SET statements



You code the various specifications that control BMC AMI Storage in SET statements in the library members.

A SET statement is composed of the keyword SET and one or more parameter specifications. A SET statement begins with the SET keyword and continues until the next SET keyword is found or the end of the member is reached.

The following rules apply:

  • All text must be uppercase.
  • The SET keyword must precede all parameters. There are no column restrictions. In the following example, all of the statements are valid.

Example

column 1
|
SET POOL=TEST
    SET POOL=TEST
SET POOL = TEST
  • Parameters are composed of keywords and associated values. There are two types of parameters: action and selection. Action parameters indicate how the BMC AMI Storage function operates. Selection parameters indicate which resources (volumes, jobs, data sets, and so on) are affected by the BMC AMI Storage function.
  • Action parameters must be placed immediately after the SET operation keyword. For members SMPOOLxx, SMFLSTxx, and SMRLSTxx, all action parameters must be on the same line or a continued line. For other members (SMMSYS xx, SMCALSxx, SMVARSxx, and SMFUNCxx), action parameters can be listed on separate lines.

    In all members the first line must be preceded with SET. In SMMSYS and SMEVNT, lines that are not preceded by SET, INC, or EXC use the default value SET (except continuations). In all other members, lines that are not preceded by SET, INC, or EXC use the default value INC (except continuations).

  • Selection parameters must follow the action parameters and start on a new line. Selection parameters can be preceded by the keyword INC or EXC to indicate inclusion or exclusion (the default is INC).
  • The parameter value is separated from the parameter keyword by an equal sign (=) and in some cases, a greater-than (>) or less-than (<) sign; spaces are optional.
  • Most parameters have a single value specification: a keyword, a name, or a name mask, or a number.

    Example

    MODE=ACT
    EXC PGM=GL0125A
    EXTENT>5
  • All selection parameters and some action parameters can have a list of values, in which case the individual values are enclosed in parentheses and separated by commas or blanks.

    Example

    POOL=(TEST,WORK,PROD)
  • Parameter specifications within a single line are separated by commas or spaces.

    Example

    SET  POOL=WORK,USEVOL=ALL
    SET  POOL=WORK USEVOL=ALL
  • Variables are concatenated by placing them together, without the use of any special connective characters. Blanks or commas cannot be placed between concatenated variables.

    Example

    DSN=&TESTHLQ&DIVCODE&TESTLLQ
  • Blank lines are allowed.
  • In SMPOOLxx or a filter or rule list, a SET statement action parameter or selection parameter can be continued onto the next line by placing any character in column 72.
  • A comment line is indicated by an asterisk in column 1.
  • Comments can be embedded in a line by starting the comment with /* and ending it with */. The following restrictions regarding /* */ comments apply:
    • They can only be used outside of a keyword and its associated value.
    • They cannot be used within a parenthesized list of values.

Example

The following examples show valid /* */ comments:

INC  JOBNAME=TSTJOB1  DSN=TEST.DSN  /* Comment is outside of any keyword and associated value */
INC  JOBNAME=TSTJOB1   /* Comment is outside of any keyword and associated value */  DSN=TEST.DSN

The following example shows an invalid /* */ comment:

INC   DSN= /* Comment within keyword and associated value not allowed */TEST.DSN

A /* */ comment appearing within a parenthesized list of values is also invalid, as the following example shows:

INC VOLSER = (DSN1.TESTA,          /* No comment allowed here within a list of values */      X
              DSN1.TESTB,          /* No comment allowed here within a list of values */      X
              DSN1.TESTC)

BMC AMI Storage would not flag either of the invalid examples as errors. Instead, BMC AMI Storage will view the leading / in the /* as a pattern matching character, causing it to always match any value, which is not how the /* */ comment was intended to be used.

 

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