The syntax of the SDF command/statement language is explained in the “Commands” manual [1 (Related publications)]. The following short forms are used in this manual:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The keyword *DEFAULT is no longer described in the individual statements. It always means the value set with the MODIFY-DEFAULTS statement.
The following also applies to the member type:
The member type is preset to *UNDEFINED. Therefore, MODIFY-DEFAULTS must first be used to define a member type, since the specification *DEFAULT would otherwise produce an error.
Input rules
The LMSCONV statements are read via the SDF user interface and processed by the command processor SDF (System Dialog Facility). Different forms of guided or unguided dialog exist, enabling you to request help menus for the statements. See the “SDF Dialog Interface” manual [20 (Related publications)].
Continuation lines
It is also possible for statements to extend over more than one record. Splitting is governed by the BS2000 command language conventions. A hyphen (-) is used as the separator character. Statement lines may be up to 16364 characters long.
Abbreviation options
When entering LMSCONV statements it is permissible to abbreviate statement names, operand names and keywords.
The following rules then apply:
It is possible in each case to abbreviate from right to left as long as uniqueness is maintained. This applies both to the name as a whole and to subnames (beginning with a hyphen) and allows for the possibility of the subname being omitted entirely.
The guaranteed abbreviation options for all statements, operands and operand values are indicated in the syntax descriptions of the statements by boldface print. It is, however, possible to abbreviate beyond these (so long as uniqueness is maintained within a structure).
Either no abbreviations or only guaranteed abbreviations should be used in procedures.
SDF allows the optional specification of operands as keyword operands or positional operands. However, the possibility of an operand position changing in a subsequent version cannot be completely ruled out. It is therefore advisable to avoid using positional operands in procedures.