CTGRRMS fails to start when XA support is active
If XA support has been activated, the Gateway daemon and CTGRRMS might not start.
The CICS® Transaction Gateway fails to start, and a log message indicates that CTGRRMS services could not be started.
The CTGINIT module is missing from the LNKLST.
Follow the steps in Enabling CTGRRMS services to add the module to the LNKLST.
CSV003I REQUESTED MODULE CTGINIT NOT FOUND CSV028I ABEND806-04 JOBNAME=MSTJCL00 STEPNAME=LLA IEA989I SLIP TRAP ID=X806 MATCHED. JOBNAME=CTGRRMS , ASID=018B. IEE824I CTGRRMS FAILED, TERMINATED IEA995I SYMPTOM DUMP OUTPUT 495 SYSTEM COMPLETION CODE=806 REASON CODE=00000004 TIME=12.33.27 SEQ=62869 CPU=0000 ASID=018B PSW AT TIME OF ERROR 070C1000 8142E1EE ILC 2 INTC 0D NO ACTIVE MODULE FOUND NAME=UNKNOWN DATA AT PSW 0142E1E8 - 9024181E 0A0D18FB 180C181D GR 0: 00001E00 1: 84806000 2: 00FCB218 3: 00000000 4: 00000000 5: 008FD5C0 6: 000000FF 7: 00000000 8: 008FA250 9: 0142E6B4 A: 00000000 B: 00000004 C: 00000000 D: 008FA250 E: 84806000 F: 00000004 END OF SYMPTOM DUMP
If a network failure occurs, the transaction is rolled back if the Java™ Transaction API (JTA) specification allows this. If the state of the transaction does not allow the transaction to be rolled back, the transaction manager repeatedly attempts to open new connections and reissue requests. The transaction manager rolls back the transaction or completes the transaction, depending on the state when the error occurs. In this situation, the transaction manager is responsible for rolling back or completing the transaction.