APAR status
Closed as program error.
Error description
The IBM MQ channel pooling process 'amqrmppa' is abruptly terminated. The following sequence of failure data capture (FDC) records is generated: First FDC: Probe Id :- ZS402099 Component :- zstAsyncConsume Program Name :- amqrmppa Major Errorcode :- MQRC_SYNCPOINT_NOT_AVAILABLE Arith1 :- 2072 (0x818) Arith2 :- 2072 (0x818) MQM Function Stack zstAsyncConsumeThread zstAsyncConsume xcsFFST Second FDC: The second FDC is generated when processing MQDISC and the MQM Function stack contains MQDISC. Example 1: Probe Id :- ZS013010 Component :- zsqVerifyPCD Program Name :- amqrmppa Thread :- 8013553 RemoteResponder Major Errorcode :- MQRC_HCONN_ERROR MQM Function Stack ccxResponder rrxResponder ccxReceiveThreadFn ccxReceiveThreadCleanup cciEndConv rriAsyncConvControl MQDISC zstMQDISC zifMQDISC zsqVerifyPCD xcsFFST Example 2: Probe Id :- ZC004062 Component :- zcpCreateMessage Program Name :- amqrmppa Thread :- 77410 RemoteResponder Major Errorcode :- STOP Probe Type :- HALT6109 MQM Function Stack ccxResponder rrxResponder ccxReceiveThreadFn ccxReceiveThreadCleanup cciEndConv rriAsyncConvControl MQDISC zstMQDISC ziiMQDISC ziiCreateIPCCMessage zcpCreateMessage xcsFFST The first FDC with error MQRC_SYNCPOINT_NOT_AVAILABLE indicates that the queue manager was not able to honor the sync-point request. The subsequent FDCs indicate error when processing MQDISC request followed by the amqrmppa process ending abruptly. Example FDC sequence 1: 2019/07/09 14:25:52.810623 amqrmppa 47979 9188100 ZS402099 zstAsyncConsume MQRC_SYNCPOINT_NOT_AVAILABLE 2019/07/09 14:25:52.885986 amqrmppa 47979 8980682 ZS013010 zsqVerifyPCD MQRC_HCONN_ERROR 2019/07/09 14:25:53.021597 amqrmppa 47979 8980682 ZI075088 zifMQDISC MQRC_HCONN_ERROR 2019/07/09 14:25:53.360496 runmqlsr 47471 6 RN201010 rppDeadProcessHandler zrcX_NON_CRITICAL_PROCESS_MISSING 2019/07/09 14:26:08.839783 amqzxma0 47374 11 ZX005022 zxcProcessChildren lrcW_S_FAST_PATH_APP_DEAD Example FDC sequence 2: 2019/10/21 11:04:01.447175 amqrmppa 9622 77412 ZS402099 zstAsyncConsume MQRC_SYNCPOINT_NOT_AVAILABLE 2019/10/21 11:04:01.534398 amqrmppa 9622 77410 ZC004062 zcpCreateMessage STOP 2019/10/21 11:04:07.163302 runmqlsr 5759 1 RN201010 rppDeadProcessHandler zrcX_NON_CRITICAL_PROCESS_MISSING
Local fix
Problem summary
USERS AFFECTED: Users using MQ client applications with asynchronous consume and transactions. Platforms affected: MultiPlatform PROBLEM DESCRIPTION: A defect in handling MQCTL operation when asynchronous thread ending caused a memory exception in MQ channel process.
Problem conclusion
MQ channel code has been modified to fix the defect in the MQCTL operation. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.1 8.1.0.11 The latest available maintenance can be obtained from http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'IBM MQ planned maintenance release dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
Temporary fix
Comments
APAR Information
APAR number
IT41770
Reported component name
MQ FOR HPE NS O
Reported component ID
5724A3904
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2022-08-15
Closed date
2022-08-15
Last modified date
2022-08-15
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
MQ FOR HPE NS O
Fixed component ID
5724A3904
Applicable component levels
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"810","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
15 August 2022