Gen 8.6 CICS transaction fails with TIRM888E and the transaction is purged

Products

• Gen
• Gen - Run Time Distributed

Issue/Introduction

Gen CICS transaction displays error message TIRM888E during execution and the CICS transaction is purged by SYSVIEW. 

TIRM030E:   APPLICATION FAILED - UPDATES HAVE BEEN BACKED OUT
TIRM888E:  ERROR MEMORY MANAGEMENT ALLOCATION
TIRM046E:   *** TRANSACTION PROCESSING TERMINATED  <tranid>
TIRM044E:   *** PRESS PA2 TO CONTINUE ***

Environment

SYSVIEW
Gen Block Mode and Server application

Resolution

CICS logs showed:

1. SYSVIEW Performance Management Message GSVC157I is the reason for the transaction failure.
2. The monitoring service (CICS_TRAN_CICS_LifeTime) tracks the running tasks. This service terminates and purges CICS transactions that exceed a defined time limit (CanLimit 00:30:00).
3. The service did not perform a full cleanup of outstanding resources initiated by the given task/transaction. As a result, TSQ resources remain in memory.
4. CICS generates a unique task number for every task. Once a limit of 99,999 is reached, the numbering typically wraps back to 1.
5. Depending on the volume of processed transactions in the client's environment it could take hours up to days before the same task number is re-used. When this happens the outdated TSQ resource causes a memory issue.

The Solution:

1. Discuss and review with Systems Administrators the rules of policies identified around when the GSVC157I occurs.
2. Review the Gen model to understand why it's execution takes longer than what is allowed by the identified policy and CanLimit.
3. Make a determination on whether to create another policy or to amend CanLimit value within that policy or modify the model to abide to the policy CanLimit.