| Author |
Message
|
| ALCSALCS |
 Posted: Tue Oct 21, 2003 3:37 am Post subject: CCSID to be used to connect a OS/390 and Windows MQ |
 |
|
Acolyte
Joined: 14 Apr 2002
Posts: 61
|
I am running an MQ V5.2 in OS/390 with CCSID 500.
An MQ running in Windows need to be connected to MQ running in OS/390.
The default value for the MQ CCSID running in Windows was 1381 but it is not supported for conversion by CCSID(500) in OS/390.
In MQ running in Windows through command ALTER QMGR CCSID the value was changed to 1115 but the following error message appears on MQ running on Windows
AMQ4052
meaning
AMQ4052 Coded character-set ID error. Cannot convert a command message to the CCSID of the target queue manager.
After a new value of CCSID(437) was used with the same error message
AMQ4052
Question:
Without changing the CCSID(500) in MQ running in OS/390, which possible CCSID can be selected in the MQ running in Windows to be able to communicate both MQ ?
For Z/OS this info is available in the Application Programmng Reference manual, where I can find the same type of info for MQ running on Windows ?
Many Thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Oct 21, 2003 4:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You do not need to change the CCSIDs of queue managers on different platforms to the same values to get them to be able to communicate with each other.
You do need to perform data conversion between different CCSIDs, however.
There are basically three ways to perform data conversion:
- Manually inside your applications
- Inside your applications, using the MQGMO_CONVERT option in your GetMesssageOptions structures
- By enabling 'Sender Conversion' on sender channels between the queue managers.
Using the Convert option is the best choice. However, if you're working with applications that you don't have the source code for, then setting up some channels with sender conversion may be appropriate.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ALCSALCS |
| Posted: Mon Oct 27, 2003 4:09 am Post subject: |
|
|
Acolyte
Joined: 14 Apr 2002
Posts: 61
|
Many Thanks for the information.
The problem was happening when the channel was started/stopped and before starting the process of testing the application. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Oct 27, 2003 5:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| ALCSALCS wrote: |
Many Thanks for the information.
The problem was happening when the channel was started/stopped and before starting the process of testing the application. |
Are you still having this problem?
Which machine is reporting it? What channel is being started/stopped when the problem occurs? How are you starting/stopping the channel?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ALCSALCS |
| Posted: Tue Oct 28, 2003 12:32 am Post subject: |
|
|
Acolyte
Joined: 14 Apr 2002
Posts: 61
|
The sequence of events was :
1) MQ V5.2 in OS/390 with CCSID 500
2) MQ in Windows CCSID(1381)
3) Try to connect both MQ
4) Channel Sender from MQ Windows to MQ OS/390 (started) and went to 'Retry status'
5) Error message on MQ OS/390
CSQX541E Invalid CCSIDs for data conversion, 1381 and 500
6) MQ in Windows issue command : ALTER QMGR CCSID(437)
7) MQ Windows try to stop Sender channel to MQ OS/390 and error message
AMQ4052 Coded character-set ID error. Cannot convert a command message to the CCSID of the target queue manager
Final solution:
 Stop the MQ in windows after issuing ALTER QMGR CCSID(437)
9) Start MQ in windows again
10) Channel Sender from MQ Windows to MQ OS/390 (started) and went to 'Run status'
Many Thanks |
|
| Back to top |
|
|
|
|
