Find the CICS Transaction which caused CICS Storage Violation

Products

• SymDump for CICS
• SymDump Batch

Issue/Introduction

 Where is the CICS transaction that caused a storage violation?  Is the transaction always shown?

Resolution

The transaction ID causing the storage violation in the Task Storage Summary (StgV).
Normally the CICS Summary Report lists all the active transactions.  However, in some cases the transaction is not listed in the CICS Summary Report. This is because the transaction ended and the storage violation was not found until after the termination of the transaction (e.g. during storage cleanup).
 When this happens, the CICS trace entries are needed to find the transaction.

There is a parameter for the CADVTGEN macro used to generate the options table, which specifies how many blocks to allocate for the CICS trace table - TRACLIM=. The default is 200.
It is possible that the TRACLIM is not large enough to show the transaction causing the storage violation.
To increase the TRACLIM, change it in the CADVTABL member located in the PPOPTIONS library and apply the USERMOD as outlined in Appendix A of the Getting Started Guide. You must then restart SymDump using program DV70INIT for the new value to take affect. 

TRACLIM:
Is the maximum CICS Formatted Trace Block Limit and specifies the maximum number of blocks from the CICS trace SymDump will format when viewing a CICS dump. The entire trace is captured but Traclim controls how many records will be formatted during dump view.