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.

Using Storage Protection

Related Topics

Assembler User Guide

Code Debug for CICS C User Guide

COBOL User Guide

Code Debug for PL I User Guide

Customizing-after-installation

Quick-Reference

Code Debug CICS allows you to select the degree of storage protection for your debugging session.

  • In the XPED/XPRT level, the Storage-Protection-1-8 screen permits you to set storage protection for any transaction or program originating from your terminal. Global parameter STORAGE_PROTECTION_UNPROTECT_TERM_FIELD can be used to remove the restriction on setting storage protection only for your own terminal. BMC recommends caution if setting STORAGE_PROTECTION_UNPROTECT_TERM_FIELD to YES because doing so enables XPED and XPRT users to activate storage protection for any terminal, transaction, or program originating in the CICS region.
  • In the XPSP level, the Storage-Protection-9-8 screen permits you to set storage protection for any terminal, task, or program in the CICS region.

Storage protection can be automatically set with the PROTECT option on the Session-Profile-Menu-0 screen. The default for a new user profile can be set by tailoring the PROFILE_DEFAULT_STORAGE_PROTECTION parameter of the Code Debug CICS global parameter table.

Additional storage protection can be set by using the Storage-Protection-9-8 screen or Code Debug’s DBPA transactions. See the Code Debug CICS Advanced Configuration space for more information.

When storage protection is enabled, Code Debug CICS analyzes each application instruction to verify that the instruction will not cause a storage violation. It also provides options for checking program reentrancy, protecting shared storage, and executing CICS commands.

Code Debug CICS not only detects and prevents storage violations, it identifies the program, transaction code, and instruction and gives the definition of the violation it is preventing. After the potential storage violation is detected and prevented, you can interactively debug the violating task through Code Debug's interactive debugging functions. Additional diagnostic reports can be created through Abend-AID for CICS by requesting a dump of the trapped storage violation.

With Code Debug CICS, processing may be continued around the instruction that attempted to violate storage. This allows you to continue a test session that might otherwise have ended in an abend or region crash. If you prefer, you can use the ALLOW command to let the trapped storage violation take place, provided that the global parameter CAN_USE_ALLOW_COMMAND is set to ON for the transaction that was used to start Code Debug.

Code Debug CICS detects and prevents storage violations even when you are not in an active debugging session. Code Debug CICS intercepts the violation before it can occur and produces a transaction abend dump. The region remains active, and programs and storage areas are protected.


 

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