Additional steps when migrating from V2.1
If you intend to migrate from V2.1 to V5.3.1, we need to consider the following when you customize your new version, in addition to the tasks in the previous sections (you do not need to install and customize the intervening versions):
- System parameter module
This might affect Task 16 in Customizing your queue managers.
There were several system parameters introduced in V5.2 (QSGDATA, RESAUDIT, DEALLCT, and UNIT2) and the MAXRTU parameter superseded the MAXALLC parameter, which is no longer used. There were also several changed parameters. Consider whether we need to use these parameters and change your system parameter module accordingly.
If you do not need to use these parameters, you do not need to relinkedit your system parameter module.
- Channel initiator parameter module
This might affect Task 17 in Customizing your queue managers.
There were several channel initiator parameters introduced in V5.2 (ADOPTCHK, ADOPTMCA, DNSGROUP, DNSWLM, LUGROUP, OPORTMAX, and OPORTMIN). Consider whether we need to use these parameters and change your channel initiator parameter module accordingly.
If you do not need to use these parameters, you do not need to relinkedit your channel initiator parameter module.
- Initialization data sets
This might affect Task 12 in Customizing your queue managers.
A sample input initialization data set for queue sharing groups called thlqual.SCSQPROC(CSQ4INSS) is supplied with WebSphere MQ. If you are planning to use queue-sharing groups, customize and include this data set. (Queue sharing groups are described in the WebSphere MQ for z/OS Concepts and Planning Guide.)
Review sample data set thlqual.SCSQPROC(CSQ4INYG) to see if you want to use the default buffer pool, storage class, and page set definitions.
- Logs
- Review sample data set thlqual.SCSQPROC(CSQ4BSDS) to see if you want to use the default settings for log placement and size.
If you are using very large messages, the amount of storage required for your log and archive data sets might increase. This is described in the WebSphere MQ for z/OS Concepts and Planning Guide.
- Installation verification program
- The name of the samples for the IVP in thlqual.SCSQPROC have been changed to CSQ4IVPQ and CSQ4IVPR. New samples called CSQ4IVPG and CSQ4IVPS have been added for the queue-sharing group IVP. These are described in Testing your queue manager.
- Migrating queues and queue definitions to shared queues
- WebSphere MQ for z/OS System Administration Guide describes how to migrate your existing queues and queue definitions to be used as shared queues. You do not have to do this, but you should consider it if you are going to use shared queues.
- Change log inventory utility (CSQJU003)
- The STARTRBA and ENDRBA keyword value of NEWLOG must end in 000 and FFF respectively.
- Return codes
- MQRC_PAGESET_FULL and new return code MQRC_STORAGE_MEDIUM_FULL have the same value.
- Data conversion exits
- Data conversion exits written for MQSeries for OS/390 V2.1 will continue to function correctly with V5.3.1. However, they cannot convert messages containing text using the Unicode UCS-2 coded character sets (1200, 13488, 17584) and need to be updated to do so, if you require such conversions.
Exits generated using the CSQUCVX utility need to be reassembled and link-edited, ensuring that you use the thlqual.SCSQMACS library supplied with V5.3.1. See the WebSphere MQ Application Programming Guide and the CSQ4BAX9 and CSQ4CAX9 samples for information about using CSQUCVX.
Other exits place calls to MQXCNVC to perform data conversion. If these exits need to deal with UCS-2, the Options parameter of this call must be updated to specify the byte order of the UCS-2 text. See the WebSphere MQ Application Programming Reference manual for information about MQXCNVC and sample exit CSQ4BAX8, which demonstrates how to calculate this parameter.
If these exits are not updated, applications cannot convert to or from Unicode UCS-2 CCSIDs. Typically, this is seen in the response from MQGET, which returns the message unconverted with reason code MQRC_SOURCE_INTEGER_ENC_ERROR or MQRC_TARGET_INTEGER_ENC_ERROR (this depends on the behavior of the exit).