Are there any reports that I can run to determine which program or transaction is causing CICS to go short on storage

Document ID : KB000027240
Last Modified Date : 14/02/2018
Show Technical Document Details

Summary:

Sample reports that can help detect the cause of SOS in CICS

 

Instructions:

 

This will display all the transaction ids, transaction number, and, the maximum amount of DSA storage. Please select the transactions during the half-hour (or less) interval before and after the SOS occurred.

Select by CICS jobname.

// EXEC EXPRPT,SIZE=EXPRPT
* may use expcfbk or tape as input
INPUT(DISKIN)
SELECT TRANID('5F'TCP,'5F'EXPC)
FROM mm/dd/yy hh:mm:ss
TO mm/dd/yy hh:mm:ss
FLASHBACK LIST DATETIME JOBNAME TRANID TRANNUM AND,
TRAN WORKSET AND TRAN LIFE
END
RUN

The variable TRAN WORKSET is the maximum amount of DSA allocated to the transaction at any point during its life. Please look for transactions that have an unusually large TRAN WORKSET value and run a detailed report on these transactions using the report below.

// EXEC EXPRPT,SIZE=EXPRPT
INPUT(DISKIN)
SELECT JOBNAME(CICSPROD)
FROM mm/dd/yy hh:mm:ss
TO mm/dd/yy hh:mm:ss SELECT TRANID(tranid1,tranid2,...)
FLASHBACK DETAIL
END
RUN