Storage Protection (9.8)
Related Topics
The Storage Protection screen (9.8) is used to set system-wide storage protection and terminal storage protection by terminal, transaction, or program. Overtype data to change it or use line commands to insert, delete, move, and copy table entries.
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 System-Facilities-Menu-9, or as described in Transferring Between Screens.
Storage Protection Screen (9.8)
COMMAND ===> SCROLL ===> CSR
MODULE: CSECT:
ENTRY 000001
LINE COMMANDS: A (After) B (Before) C (Copy) D (Delete) I (Insert) M (Move)
-----------PROTECTION OPTIONS-------
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
_ ____ ____ ____ ________ ___ ___ ___ ___ ___
_ ____ ____ ____ ________ ___ ___ ___ ___ ___
_ ____ ____ ____ ________ ___ ___ ___ ___ ___
On every LINK, XCTL, and UCH invocation, the following process occurs:
- The program about to be invoked, the current terminal ID, and the transaction code are used to match against the storage protection table entries.
- The storage protection table is searched sequentially top to bottom.
- When the first match is found, the corresponding protection options are applied.
- If no table entry matches the TERM/TRAN/PROGRAM fields, no storage protection takes place.
Protection of program storage applies to any resource defined programs. If the user has performed an EXEC CICS LOAD when branching to that program, the protection tables are searched 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): Destination after which an entry is moved or copied.
- B (Before): Destination before which an entry is moved or copied.
- C (Copy): Entry to be copied.
- D (Delete): Entry to be deleted.
- I (Insert): Insert a new entry following this entry.
- M (Move): Entry to be moved.
TYPE
Type of interaction that a storage protection entry has with other entries. Valid entries are:
- SYST: Prevents an entry specified on this screen from being changed with the Storage Protection screen (1.8). SYST type entries are automatically grouped at the beginning of the table.
- USER: Allows inserting between and/or before the entry and altering the entry if entered with this terminal ID using the Storage Protection screen (1.8).
- AUTO: Adds entries at the end of the table if entries are being created automatically (an installation option).
When ending the session, Code Debug CICS deletes all USER and AUTO entries created by this session. SYST entries can only be deleted manually from the Storage Protection screen (9.8).
TERM, TRAN, and PROGRAM
Set terminal storage protection exceptions. Valid entries are:
- asterisks (****): Selects all terminals, transactions, or programs. Type an asterisk in any position for generic selections.
- HERE: In the TERM field, sets storage protection exceptions at the current terminal when the current terminal ID is not known.
- NONE: In the TERM field, matches only asynchronous (non-terminal initiated) transactions.
No validation is performed against CICS-defined resources (terminal, transaction, or program).
PROTECTION OPTIONS
The remaining input fields are used to specify YES or NO for various storage protection options.
STORE
Defines whether instructions that update storage are monitored.
- NO: Storage protection is bypassed for transactions matching the values in the TERM, TRAN, and PROGRAM fields. The default is NO.
- YES: Storage protection is performed for transactions matching the values in the TERM, TRAN, and PROGRAM fields.
FETCH
Defines whether instructions that access storage are monitored.
- NO: Fetch protection is bypassed for transactions matching the values in the TERM, TRAN, and PROGRAM fields. The default is NO.
- YES: Fetch protection is performed for transactions matching the values in the TERM, TRAN, and PROGRAM fields.
SHR
Defines whether instructions that update shared storage are monitored.
- NO: TERM, TRAN, and PROGRAM combination is allowed to update allocated shared storage. The default is NO.
- YES: TERM, TRAN, and PROGRAM combination is not allowed to update allocated shared storage.
PGM
Defines whether instructions are monitored for updating program storage. This option allows you to determine whether the program is reentrant.
- NO: Code Debug CICS allows the current application program to store into itself. The default is NO.
- YES: Code Debug CICS considers it a storage violation if there is an attempt to store anything within this program’s storage. 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 that match the values specified in the TERM, TRAN, and PROGRAM fields to determine whether it can be updated.
Output Field
ENTRY
Relative entry number represented by the first entry on the screen.