| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Different CCSID of application and Queue Manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| ankurlodhi |
 Posted: Wed Jan 31, 2018 10:51 am Post subject: Different CCSID of application and Queue Manager |
 |
|
Master
Joined: 19 Oct 2010
Posts: 266
|
In our environment Application 'A' is putting messages on my Queue Manager "QMA" . My Queue Manager "QMA" has CCSID : 819 and the Application has CCSID : 1208.
when the application puts the messages on remote queue and reaches the Target Queue Manage "QMB" r. The application B on target side doesn't find and putdate and puttime in Message header.
To find the issues is on which end i asked the application A to put a message directly on local Queue on QMGR "QMA" and there was no putdate or puttime in the MQMD.
is this issue due to Queue Manager CCSID difference. and can it be resolved by setting the QMGR CCSID to 1208 |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Jan 31, 2018 10:59 am Post subject: Re: Different CCSID of application and Queue Manager |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ankurlodhi wrote: |
| is this issue due to Queue Manager CCSID difference. |
No.
| ankurlodhi wrote: |
| can it be resolved by setting the QMGR CCSID to 1208 |
No.
It's either a bug in MQ or the putting application doing something very odd when it puts the message to the queue. The date and time are not character fields, and the CCSID values relate to the payload not any of the headers.
Check how the putting application is building the MQMD and/or setting MQMD attributes prior to the put. If there doesn't seem to be anything out of the ordinary, raise a PMR.
You could also try changing the CCSID of the queue manager; if that fixes the problem you should absolutely raise a PMR and post here what the outcome was! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jan 31, 2018 11:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
What MQPMO_ options were specified? MQPMO_NO_CONTEXT, for example?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 31, 2018 12:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| What MQPMO_ options were specified? MQPMO_NO_CONTEXT, for example? |
Would that eliminate the put date & time?
Things you learn...... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jan 31, 2018 3:56 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Yep.
From https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_7.5.0/com.ibm.mq.ref.dev.doc/q098730_.htm
| Quote: |
MQPMO_NO_CONTEXT
Both identity and origin context are set to indicate no context. This means that the context fields in MQMD are set to:
Blanks for character fields
Nulls for byte fields
Zeros for numeric fields |
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
