A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

Closed as program error.

Error description

A Queue Manager fails with ABEND5C6-00F30095 at startup
if the same SSID has been defined on several LPARs.
The return code indicates ATR_RM_ACTIVE_ON_ANOTHER_SYSTEM,
because it is already active on another LPAR.
This ABEND was also issued in WMQ V6 or V701, but it did not
terminate the queue manager instance.
After installation of apar PM61006 (UK80194),
an ABEND0C4 in CSQ3RRSF +912 is generated which follows
ABEND5C6-00F30095 and results in queue manager termination
with CSQV086E REASON=00E80100 .
The 0C4 is issued because REG2 contains all zeroes - it was
loaded from: SDWA => XPAD => SDWAXEME (64bit info)
CSQ3RRSF does not check if reg2 is valid before using it.
.
ADDITIONAL SYMPTOMS:
The ABENDS0C4 S0C4 in CSQ3RRSF+x'912' appears in logrec as
an S00C4 in CSQ3REPL. The failing instruction is 5090 2030.
.
The ABEND0C4 can occur in other situations besides the
ABEND5C6-00F30095. For example, after a STOP QMGR MODE(FORCE),
AB/S06C6 PRCS/00E50070 appears in logrec followed by the S00C4.
The error in the joblog is:
CSQV086E QUEUE MANAGER ABNORMAL TERMINATION REASON=00E80140
.
00E80140 00E50070 0C4 S0C4 FORCE ABEND5C6 ABEND6C6

Local fix

Define the same SSID in one system / LPAR only to avoid the
ABEND5C6-00F30095.