A fix is available
APAR status
Closed as program error.
Error description
Change Team finds after customer migration to version 9 some changes to exit loading have taken place. The default exit checking mechanism used in v9 results in a change in exit processing behavior. After recompiling an exit in the CSQXLIB DD, if a channel which uses the exit attempts to start while there is still an active channel using the old version of the exit, then MQ will fail the channel. This differs from the default behavior at previous versions of MQ, where the new channel would load and use the new version of the exit while existing channels continued to use the old version. Change Team finds that this should be investigated in order to determine whether this change should be mitigated.
Local fix
There is a tuning parameter available which alters the exit loading such that the updated exit should be used for channels starting after the change, while existing channels continue to use the already loaded copy of the old exit. The tuning parameter can be set using cpf RECOVER QMGR(TUNE CHINEXITDL ON) Note that this value is not preserved across qmgr restart. To ensure that it is set after restart, the command can be added to CSQINP2
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM MQ for z/OS Version 9 * * Release 0 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: A V9 qmgr is running with multiple * * channels using a channel exit. When * * the exit code is updated and a channel * * which uses the exit tries to start, the * * channel fails with message: * * CSQX535E +cpf CSQXRESP Channel xxx * * stopping because exit yyy is not valid. * **************************************************************** An MQ V9 qmgr is running with multiple channels using a channel exit. An update is made to the exit code, and the new version is built into the dataset pointed to by the CSQXLIB DD. When a channel which uses the exit tries to start, MQ detects that the exit has changed. However, if it also detects that an older version is still in use by other channels, and if the tuning parameter ChinExitDL is not set then the exit will not be loaded and the starting channel fails with message CSQX535E. If the tuning parameter ChinExitDL is set, then directed loading is used to allow the starting channel to use the updated exit.
Problem conclusion
The ChinExitDL flag is now set ON at qmgr startup, and the default value reported by the RECOVER QMGR is now ON.
Temporary fix
Comments
APAR Information
APAR number
PI86807
Reported component name
MQ Z/OS V9
Reported component ID
5655MQ900
Reported release
000
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-09-04
Closed date
2018-01-30
Last modified date
2018-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI53539 010PC2 010PC2 010PC2
Modules/Macros
CSQIRECP CSQMSTRT
Fix information
Fixed component name
MQ Z/OS V9
Fixed component ID
5655MQ900
Applicable component levels
R000 PSY UI53539
UP18/03/14 P F803
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
03 April 2018