|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Messages altered when taken from mainframe queue |
« View previous topic :: View next topic » |
Author |
Message
|
rraam75 |
Posted: Mon Jan 08, 2007 6:46 am Post subject: Messages altered when taken from mainframe queue |
|
|
Novice
Joined: 18 Mar 2006 Posts: 14
|
hello,
Iam sending mq message from windows2000 to mainframe. When the IMS pgm takes the message and give it to my transaction program Iam seeing the messages get altered. I notice some junk values in the messages.
So, to investigate further, I stopped my transaction program. Now the messages get routed to DLQ. When I browse the message content at DLQ, I don't find any junk values in the message.
So, could anyone tell me what is happening in mainframe mq?? Is the IMS bridge application changing the message content?? |
|
Back to top |
|
 |
zpat |
Posted: Mon Jan 08, 2007 7:00 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Does the receiving application issue MQGET with MQGMO_CONVERT? |
|
Back to top |
|
 |
cicsprog |
Posted: Mon Jan 08, 2007 3:23 pm Post subject: |
|
|
Partisan
Joined: 27 Jan 2002 Posts: 347
|
|
Back to top |
|
 |
David.Partridge |
Posted: Tue Feb 27, 2007 6:10 am Post subject: |
|
|
 Master
Joined: 28 Jun 2001 Posts: 249
|
If this is IMS bridge, then you can't use conversion in the application.
For the IMS bridge, the actual message get is done using smoke and mirrors from inside the MSTR address space and done without conversion.
The CHIN is "supposed" to handle conversion of MQIIH format messages.
Quote from the programming reference (bold added by myself for emphasis):
"Character set and encoding: Special conditions apply to the character set and encoding used for the MQIIH structure and application message data:
Applications that connect to the queue manager that owns the IMS bridge queue must provide an MQIIH structure that is in the character set and encoding of the queue manager. This is because data conversion of the MQIIH structure is not performed in this case.
Applications that connect to other queue managers can provide an MQIIH structure that is in any of the supported character sets and encodings; conversion of the MQIIH is performed by the receiving message channel agent connected to the queue manager that owns the IMS bridge queue.
Note:
There is one exception to this. If the queue manager that owns the IMS bridge queue is using CICS for distributed queuing, the MQIIH must be in the character set and encoding of the queue manager that owns the IMS bridge queue.
The application message data following the MQIIH structure must be in the same character set and encoding as the MQIIH structure. The CodedCharSetId and Encoding fields in the MQIIH structure cannot be used to specify the character set and encoding of the application message data.
A data-conversion exit must be provided by the user to convert the application message data if the data is not one of the built-in formats supported by the queue manager." |
|
Back to top |
|
 |
zpat |
Posted: Wed Feb 28, 2007 10:41 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Set data convert on the channel from Windows to z/OS - or rather create a new sender channel with CONVERT(YES) and use that for these messages. |
|
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
|
|
|
|