| Author |
Message
|
| Graham Cogill |
 Posted: Mon Jun 28, 2004 4:24 am Post subject: Windows 2000 MQSeries manager to a manager on the mainframe |
 |
|
Novice
Joined: 19 May 2004
Posts: 10
Location: UK
|
We are writing a message from a Windows 2000 MQSeries manager to a manager on the mainframe, with the IMS Bridge (and IMS) as the eventual destination.
We have set the MQMD encoding to MQENC_NATIVE.
We have set the MQMD CodedCharSetID to MQCCSI_Q_MGR
We have set the SENDER channel properties to Convert=Yes
The constructed message (IIH plus IMS variable string) look ok.
But we are still getting error code 2111, which suggests the CodedCharSetId is in error.
If the two queue mangers can understand the MQMD that is passed, how can they not understand the following message in the same format? |
|
| Back to top |
|
 |
| EddieA |
| Posted: Mon Jun 28, 2004 9:07 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Have you set the CCSID and Encoding correctly in the MQIIH.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Graham Cogill |
| Posted: Tue Jun 29, 2004 12:01 am Post subject: |
|
|
Novice
Joined: 19 May 2004
Posts: 10
Location: UK
|
| Quote: |
| Have you set the CCSID and Encoding correctly in the MQIIH |
we have set CCSID to 500 and format to MQIMSVS
We have an exit running on that sender channel (to reformat the message for the IMS Bridge ) which we suspect is affecting the conversion. So we are going to insert an additional channel which will allow us to do the conversion on the MGET and see if that cures the problem.
I would be interested in your opinion |
|
| Back to top |
|
|
| Remco |
| Posted: Tue Jun 29, 2004 3:01 am Post subject: |
|
|
Acolyte
Joined: 19 Mar 2002
Posts: 68
Location: Capelle aan den IJssel (Rotterdam)
|
As far as I can remember, format has to be set to STRING.
Good Luck |
|
| Back to top |
|
|
| Graham Cogill |
| Posted: Tue Jun 29, 2004 5:47 am Post subject: |
|
|
Novice
Joined: 19 May 2004
Posts: 10
Location: UK
|
Thanks for your advice
We believe we have solved the problem.
FYI
We had an exit dll (for formatting the message) running on the same sender channel as we had defined translation to EBCDIC. It seems that MQ translated the message to EBCDIC, then the dll read the message, altered it and wrote it out in ASCII format which persisted through to the mainframe.
We have put an extra channel in so we can seperate the 2 functions and it's working well. |
|
| Back to top |
|
|
|
|
