Notational conventions

IBM® uses a uniform notation to describe the syntax of access method services commands. This notation is not part of the language; it is a way of describing the syntax of the commands, and uses these conventions:
[ ]
Brackets enclose an optional entry. You can, but need not, include the entry. Examples are:
  • [length]
  • [MF=E]
|
An OR sign separates alternative entries. You must include one, and only one, of the entries unless you allow an indicated default. Examples are:
  • [REREAD|LEAVE]
  • [length|'S']
{ }
Braces enclose alternative entries. You must use one, and only one, of the entries. Examples are:
  • BFTEK={S|A}
  • {K|D}
  • {address|S|O}

Sometimes alternative entries are shown in a vertical stack of braces. An example is:

MACRF={{(R[C|P])}
       {(W[C|P|L])}
        {(R[C],W[C])}}

In the example above, you must choose only one entry from the vertical stack.

...
An ellipsis indicates that the entry immediately preceding the ellipsis can be repeated. For example:
  • (dcbaddr,[(options)],. . .)
‘  ’
A blank indicates that a blank must be present before the next parameter.
UPPERCASE BOLDFACE
Uppercase-boldface type indicates entries that you must code exactly as shown. These entries have keywords and the following punctuation symbols: commas, parentheses, and equal signs. Examples are:
  • CLOSE , , , ,TYPE=T
  • MACRF=(PL,PTC)
UNDERSCORED UPPERCASE BOLDFACE
Underscored uppercase boldface type indicates the default used if you do not specify any of the alternatives. Examples are:
  • [EROPT={ACC|SKP|ABE}]
  • [BFALN={F|D}]
lowercase italic
Lowercase italic type indicates a value that you supply according to specifications and limitations described for each parameter. Examples are:
  • number
  • image-id
  • count