Syntax rules for NSMSYSIN control statements

You can specify one or more control statements in the NSMSYSIN DD JCL statement. This section provides a summary of the syntax rules for the NSMSYSIN control statements

Control statement content

The following rules apply to control statement content:

  • Statement text is contained within the first 72 positions of an 80-byte record, and the last 8 bytes are ignored.
  • A statement consists of the following fields:
    • Label (optional)
    • Command code (required)
    • One or more keywords (optional)

    • Comment (optional)
      The following statement shows example fields:

      LABELCOMMANDOPERAND=TEST/* COMMENT */
  • A complete statement might spread across several 80-byte records.
  • The control statement data set can contain any number of control statements.

Special characters

The following characters are special characters within a control statement:

  • Blank
  • Comma
  • Equal sign
  • Parenthesis
  • Single quotation mark
  • Decimal point

Continuation characters

Continuing entries in a list:

  • Must use a "+" continuation indicator rather than a "-",
  • The + continuation indicator must immediately follow the "," character behind the list entry,
  • The continued statement must begin in position 1.
    Examples:
XCHECK -
TYPE=ACB, -
 MBRLIST=(DBD1,+
DBD2), -
 INDD=ACBLIB2

Literals

The following rules apply to literals:

  • A literal consists of one or more characters enclosed within single quotation marks.
  • If a literal contains a single quotation marks, it must be represented by two consecutive quotation marks, as in the following example:
    'ISN' 'T'
  • You cannot continue literals from one record to the next.

Labels

The following rules apply to labels:

  • A control statement can optionally have a label field.
  • The label must start in the first position of the control statement.
  • The label must consist of a period (.) and 1 to 7 alphanumeric characters, as in the following example:
    LABEL3
  • The label must be followed by one or more blanks.

Command codes

The following rules apply to command codes:

  • The command code consists of predefined words.
  • The command code must follow the label (if one is present) and must precede the keywords (if any are present).
  • The command code must be followed by one or more blanks.

Keyword operands

The following rules apply to keyword operands:

  • Keyword operands consist of a keyword, an equal sign, and one or more optional values.
  • Keyword operands must be separated by a comma.
  • You can enclose keyword operand values with parentheses or quotation marks, as in the following examples:
    REPORTS=(PSBLIST=YES)
  • You must enclose the keyword operand value with parentheses if it consists of more than one value. Each value must be separated by a comma, as in the following example:
    REPORTS=(PSBLIST=YES,SYSINLST=NO)
    or
    REPORTS=(2,5,6)
  • You can use blanks in the operand value only within a literal.

  • You must enclose the keyword operand value with quotation marks if it contains a blank or comma, as in the following example:

    HEADING='THIS IS A TEST' or HEADING=(REPORT1,'THIS IS A TEST')

Comments

The following rules apply to comments:

  • You must enclose a comment within the following symbols:
    /* */
    as in the following example:
    /* THIS IS A COMMENT */
  • Comments can only appear at the end of the control statement.

Related topic

Commands-control-statements



 

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