Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Analyzing storage violations

This topic describes possible approaches for using Abend-AID for CICS to analyze storage violations. A CICS Transaction Server for OS/390 version 1 storage violation example is provided.

Programming errors that commonly cause storage violations include the following:

  • A failure to reassemble or recompile programs after redefining a common storage area. This mistake can result in issuing a GETMAIN for insufficient storage.
  • Runaway subscripts caused by tables with no size limitations.
  • Writing data to an area after a FREEMAIN has been issued.
  • Posting an ECB for a canceled task. With this type of error, a transaction attempts to hand-post an ECB after a task waiting on it has been canceled. As a result, data belonging to an unrelated activity becomes corrupted.

The approach described in this chapter for analyzing storage violations is based on a specific storage violation dump. To generate this dump, install and invoke the supplied CICS transaction ERWV described in the Abend-AID Advanced Configuration Guide.

After generating the dump, use the Data set Import screen to import it. However, if you installed Abend-AID for CICS to import dumps automatically, this final step is not necessary. For information about importing dumps, refer to SVC Dump Import Screen.

Note

Because of unique CICS system activity, the dump information in your Abend-AID for CICS screens will differ from the information shown in this chapter. In particular, addresses may vary.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*