JECL syntax conventions


The syntax of a BMC ThruPut Manager JECL statement follows JES2 conventions.

Note the following:

  • Uppercase letters and words are coded on the control statement exactly as they appear in the format model, as are the following characters:
    – comma     ,
    – parentheses         )
  • Lowercase letters, words, and symbols appearing in the format model represent variables for which specific information is substituted when the parameter is coded. For example: 

    /*JBS BIND agent-name

   is the format description for the JBS BIND control statement. When you code the command, substitute the Agent name for the symbol agent-name.

  • The bar | is a special notation and is never coded on a control statement. The bar is used to separate elements in a list of choices from which only one can be selected. For example:

    GLOBAL | LOCAL

    indicates that you should choose one of the two types of activation attribute for an Agent that is being activated by a /*JBS ACTIVATE statement.
  • Braces { } are a special notation and are never coded on a control statement. Braces are used to indicate a set of items from which one must be chosen. For example:

    {JOB | nn}

    illustrates a keyword choice for the /*DCS NAG statement. The braces indicate that you must specify one of JOB or nn.
    Note that braces are used only when needed to clarify the syntax. If there is little chance for confusion, choices are separated by bars (|) only, as described previously. The intention is to simplify syntax descriptions as much as possible.
  • An underlined choice indicates the value that is used as the default if no choice is specified. For example:

    GLOBAL | LOCAL

    If no keyword is specified, the default is LOCAL.
  • Brackets [ ] are a special notation and are never coded on a control statement. Brackets indicate that the enclosed item is optional and you can omit it entirely. For example:

    [FROM=stepname]

    is part of the format of the /*JBS ACTIVATE control statement. When coding the /*JBS ACTIVATE statement you can specify the FROM keyword or omit it entirely.
  • Keywords on BMC ThruPut Manager JECL statements can be separated by either blanks or commas; however we recommend the use of commas except where spaces provide superior clarity.


 

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