You must observe the following rules when coding initialization
statements:
- Code the statement name and parameters in columns 1-71. Column
72 must be blank if the statement is complete; column 72 may be blank
or non-blank if the statement is continued. JES3 ignores columns 73-80.
- Use commas to separate the statement name from the first parameter
and to separate one parameter from another.
- If you code a keyword parameter more than once, JES3 typically
uses the last value coded. In some cases, however, JES3 treats a duplicate
keyword as a continuation of a previously coded keyword of the same
name. In other cases, when JES3 encounters a duplicate keyword, it
issues a diagnostic message.
- If you want to continue an initialization statement (individual
statement descriptions specify whether a statement can be continued):
- The last item you code in columns 1-71 must be a complete parameter
(a parameter and all of its subparameters) followed by a comma or
a subparameter followed by a comma.
- If one or more blanks follows a comma, that statement is considered
continued, and any data beyond the blank(s) is treated as a comment.
If a comma appears in column 71 following a statement parameter, that
statement is considered continued.
- Column 72 optionally may contain any non-blank character if the
statement is being continued. Use of a non-blank character in a statement
that is not to be continued results in an
error and message IAT3253 is issued.
- On the continuation statement you may start coding in any column.
The statement can complete on this line or be continued.
- You can place any number of comment statements (indicated by an
asterisk in column 1) anywhere in the initialization stream. Comment
statements cannot be continued; however, multiple comment statements
can be included consecutively.
- Initialization statements can contain embedded comments provided
that at least one blank separates the last parameter and the comment.
For initialization statements that are continued, at least one blank
must follow the continuation comma (with the exception of a comma
in column 71).
- JES3 does not evaluate symbols in initialization
statements. Symbol names, including ampersands and periods, are handled
literally. In limited cases (such as the DSN= parameter on the DYNALLOC
statement) where the use of symbols in the parameter does not cause
the parameter to exceed its maximum length, symbols will be passed
to another system component to perform the evaluation, provided that
system component supports a symbol for the parameter in question,
but in general the use of symbols is not supported by JES3. Error
messages may or may not be issued, depending on whether the statement
in question can tolerate the use of ampersands or periods within its
parameters. In cases where errors are not issued and the value is
defined literally, the resulting definition may not be usable by JES3.
- You should not rely on parameter default values to be sufficient
for your environment. Test each default value used, and be alert to
performance problems that may arise as your environment changes.
Examples: The following are examples of
valid initialization statement continuation:
CLASS,NAME=ABC,DEF=YES,
MDEPTH=(SY1,10)
CLASS,NAME=ABC,GROUP=TESTGP,SYSTEM=(SY1,SY2)
CLASS,NAME=ABC,GROUP=TESTGP,SYSTEM=(SY1,SY2),
DEF=YES
CLASS,NAME=ABC,DEF=YES, This is a comment
MDEPTH=(SY1,10)
CLASS,NAME=ABC,DEF=YES, This is a comment
*This is a comment line
MDEPTH=(SY1, This is a comment
*This is a comment line
10)