A fix is available
APAR status
Closed as program error.
Error description
SLIP SET on MSGID=CSQX772E showed that the root cause of this problem is due to a timeout when the chinit inquire channels while building the certificate label cache at startup. The supervisor task puts an inquire channel command message to the command queue, and waits for up to 10s for the response. This dump shows that this command had not yet been processed, because the command server was busy clearing a shared queue - as part this a request had been queued to the DB2 BLOB tasks, but it had not completed because all of the BLOB tasks were busy in DB2 - this appeared to be due to BACKUP CFSTRUCT(*) had initiated 16 structure backups just prior to the clear queue command, as they were also making DB2 updates. It is unusual that a command would take more than 10s to be processed, it is not expected that it would leave the chinit without a valid channel certificate cache.
Local fix
REFRESH SECURITY TYPE(SSL) was able to resolve the issue
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM MQ for z/OS Version 9 * * Release 0 Modification 0 and Release 1 * * Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: CSQX772E is issued at chinit startup, * * reporting MQCMD_INQUIRE_CHANNEL failed * * with MQRC 0 (MQRC_NONE). * * When SSL/TLS channels are subsequently * * started, the value of CERTLABL on the * * channel definition is ignored. * **************************************************************** During channel initiator startup, the chinit gets a list of channels and caches the value of CERTLABL for each. However if the response to the inquire channel command is delayed (for example, because the command processor is busy), this processing fails, causing any incoming channel to use the default certificate label instead of the value specified by CERTLABL.
Problem conclusion
The time waited for the inquire channel command response is increased, to allow for other work being processed by the command processor. If the cache is not successfully created, incoming channels will fail with GSK_ERR_UNRECOGNIZED_NAME (448).
Temporary fix
Comments
APAR Information
APAR number
PI86956
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-06
Closed date
2019-10-04
Last modified date
2019-11-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI65708 UI65709
Modules/Macros
CMQXRSSM CSQXGSNI
Fix information
Fixed component name
MQ Z/OS V9
Fixed component ID
5655MQ900
Applicable component levels
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:
01 November 2019