Security control statements

The security table consists of specific control statements and control keywords. You can edit these statements to update the security table for internal and external security.


The following lists the keywords and their description.

Specifies an authorized screen space (PROC) library for initialization that bypasses the security check.
Sets the internal security levels of commands, marks them for external security, and requests an audit.
Specifies whether a listing of the current security settings is to be produced on this run.
Specifies the security options for minor commands.
Specifies the name of the module that contains the user external security exit routine.
Specifies the internal passwords.
Clears current settings.
Specifies the record ID number for SMF audit requests.
Specifies whether updating is to be performed on this run.

Format rules for control statements

These format rules apply to all control statements.

  • Control statements can begin anywhere in the input record but cannot extend beyond column 72.
  • Statements can be in any order in the input stream. The update program processes the statements as it encounters them, with the exception of the LIST and UPDATE statements. These statements take effect after all other input is processed.
  • All information for a particular control statement must fit in a single line.
  • All input must be in uppercase letters.
  • Statements must be in this format:


    Note: Blanks are not allowed because the update program treats data that follows a blank as a comment. The data prints on the edit listing but is ignored for processing purposes.
  • To insert comment lines anywhere in the input stream, place an asterisk (*) in the first column of the input record.
  • If the update program identifies statements as incorrect, correct the statements and resubmit them.

    To correct the setting, specify a new one instead of deleting or replacing part of the old one, especially when changing a command from EXTERNAL=YES to EXTERNAL=NO.

  • The Classic Interface does not recognize changes of control statements until the update job completes successfully and until a new Classic Interface session is started.

    Usually, the control statement edit listing indicates successful completion of the update.