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.

Storage Protection (1.8)

Related topics

Using-Code-Debug-CICS-with-Assembler-program

Code Debug for CICS C User Guide

Using-Code-Debug-CICS-with-COBOL-program

Code Debug for CICS PL I User Guide

Quick-Reference

The Storage Protection screen (1.8) sets storage protection by terminal, transaction, or program and displays all current storage protection entries. You are only allowed to modify storage protection selections created at this terminal. These entries show the type of storage protection in effect for this CICS region. You can type over data to change it or use line commands to insert, delete, move, and copy.

The request is effective immediately within the current CICS task for this LINK/enclave level and any enclave levels created from this point on. Programs within the current CICS task at a higher (existing) LINK/enclave level are not included in this request.

Access this screen by typing the number 8 on the Session Control Menu, or as described in Transferring Between Screens.

Storage Protection Screen (1.8)

 ----------------------------- STORAGE PROTECTION (1.8) -------------------C024
 COMMAND ===>                                                  SCROLL ===>  CSR
 MODULE:          CSECT:
                                                                   ENTRY 000001
 LINE COMMANDS:  A (After) B (Before) C (Copy) D (Delete) I (Insert) M (Move)


 CMD    TYPE   TERM    TRAN    PROGRAM   STORE  FETCH   SHR    PGM   CMD Store
-----------------------------------------------------------------------------
  _     USER   S123    ****    ********   NO     NO     NO     NO     YES
  _     USER   ****    XCB2    ********   NO     NO     NO     NO     YES
  _     USER   ****    ****    ********   NO     NO     NO     NO     YES
  _     ____   ____    ____    ________   ___    ___    ___    ___    ___
  _     ____   ____    ____    ________   ___    ___    ___    ___    ___
  _     ____   ____    ____    ________   ___    ___    ___    ___    ___

Features of this screen are:

  • TYPE and TERM fields are protected and cannot be changed.
  • Entries made on this screen are always assigned a TYPE of USER. User entries (USER) for this terminal can be moved or copied.
  • Entries marked with the user’s terminal ID can be inserted, changed, or deleted.
  • System entries (SYST) can be modified only by an XPSP user via the Storage Protection screen (9.8). SYST entries are displayed on the 1.8 screen to provide an accurate status of storage protection for the terminal.

Code Debug CICS performs the following procedure on every LINK and XCTL:

    1. Matches the program to be invoked, the current terminal ID, and the transaction code with the storage protection table entries.
    2. Searches the storage protection table sequentially top to bottom.
    3. When it finds the first match, the corresponding protection options are applied.
    4. If no table entry matches the TERM, TRAN, and PROGRAM fields, no storage protection takes place.

Protection of program storage applies to all resource-defined programs. If a program executes the following command:

EXEC CICS LOAD PROGRAM(NAME)

and then branches to that program, Code Debug CICS searches the protection tables to see if the new program qualifies for a different protection table entry. If no new entry is found, the current entry’s protection parameters are used.

Input Fields

CMD

Line command entry field. Valid entries are:

  • A (After): Line after which a moved (M) or copied (C) entry is to be inserted.
  • B (Before): Line before which a moved (M) or copied (C) entry is to be inserted.
  • C (Copy): Line that is to be copied. (Must be used with the A or B line command.)
  • D (Delete): Line that is to be deleted.
  • I (Insert): Line after which a blank line is to be inserted.
  • M (Move): Line that is to be moved. (Must be used with the A or B line command.)

TRAN and PROGRAM

Valid entries in these fields set terminal storage protection. Anything keyed into the TRAN or PROGRAM fields is accepted. CICS tables are not validated. The TERM, TRAN, and PROGRAM fields are treated as masks. Asterisks in these fields represent a wildcard character and will match any character.

PROTECTION OPTIONS

The remaining input fields are used to specify YES or NO for various storage protection options.

STORE

Defines whether Code Debug CICS monitors instructions that update storage. Valid entries are:

  • NO: Bypasses storage protection for transactions that match the values specified in the TERM, TRAN, and PROGRAM fields. The default is NO.
  • YES: Performs storage protection for transactions that match the values specified in the TERM, TRAN, and PROGRAM fields.

FETCH

Defines whether Code Debug CICS monitors instructions that access storage. Valid entries are:

  • NO: Bypasses fetch protection for transactions that match the values specified in the TERM, TRAN, and PROGRAM fields. The default is NO.
  • YES: Performs fetch protection for transactions that match the values specified in the TERM, TRAN, and PROGRAM fields.

SHR

Defines whether Code Debug CICS monitors instructions that update shared storage. Valid entries are:

  • NO: Code Debug CICS allows storing into shared storage for transactions that match the values specified in the TERM, TRAN, and PROGRAM fields. The default is NO.
  • YES: Code Debug CICS does not allow storing into shared storage for transactions that match the values specified in the TERM, TRAN, and PROGRAM fields.

PGM

Defines whether Code Debug CICS monitors instructions that update program storage. This option allows you to determine whether the program is reentrant. Valid entries are:

  • NO: Code Debug CICS allows storing into program storage for those transactions that match the values specified in the TERM, TRAN, and PROGRAM fields. The default is NO.
  • YES: Code Debug CICS does not allow storing into program storage for those transactions that match the values specified in the TERM, TRAN, and PROGRAM fields. This setting should be used for testing reentrant code.

CMD Store

Defines whether Code Debug CICS monitors CICS command level commands that update storage. Valid entries are:

  • NO: Code Debug CICS will not validate the storage associated with the INTO parameter of CICS commands that match the values specified in the TERM, TRAN, and PROGRAM fields to determine whether it can be updated. The default is NO.
  • YES: Code Debug CICS will validate the storage associated with the INTO parameter of CICS commands for those transactions that match the values specified in the TERM, TRAN, and PROGRAM fields to determine whether it can be updated.

Output Fields

ENTRY

Relative entry number represented by the first entry on the screen.

TYPE

Type of interaction a storage protection entry has with other entries. Three labels are used:

  • SYST: Value was entered on the Storage Protection screen (9.8) and cannot be altered by the Storage Protection screen (1.8). SYST entries are automatically grouped at the beginning of the table of storage protection entries.
  • USER: Value was entered on either the 9.8 or 1.8 screen. It can be changed on the 1.8 screen only if it is for this terminal. USER entries for other terminal IDs have the CMD field unprotected, but accept only the I (Insert), B (Before), or A (After) line commands.
  • AUTO: Value is placed at the end of the table. AUTO entries are automatically created for the user when the XPED, XPRT, or XPSP transaction is entered and PROTECT ON is specified in the user’s profile. See Session-Profile-Menu-0.

Important

All entries made by the Storage Protection screen (1.8) are automatically labeled USER. When the session is ended, Code Debug CICS deletes all USER and AUTO entries created during this session.

TERM

User’s terminal ID.

 

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