Creating the statements

To customize the Tivoli Workload Scheduler for z/OS functions, you must set the initialization statements of the PARMLIB library data set. Each statement consists of a statement name, keywords, and keyword values, and follows TSO command syntax rules:

Statement data must be in columns 1 through 72. Information in columns 73 through 80 is ignored.
A statement cannot exceed 455 records.
A statement can be specified only once, unless otherwise indicated. If more than one instance of a statement is specified, only the last one is taken into account. No warning message is reported in EQQMLOG.
A keyword can be specified in a statement only once, unless otherwise indicated. If more than one instance of a keyword is specified in the same statement, only the last one is taken into account. No warning message is reported in EQQMLOG.
A blank or comma serves as the delimiter between two keywords; if you supply more than one delimiter, the extra delimiters are ignored.
Values for keywords are contained within parentheses. If a keyword can have multiple values, the list of values must be separated by valid delimiters. Delimiters are not allowed between a keyword and the left parenthesis of the specified value.
Some keywords have multiple values. If you want to use the default for a value that occurs before the one you are specifying explicitly, use the delimiter shown in the keyword syntax. For example, if you specify TRACK(READYFIRST) on the JTOPTS statement, the default ALL is used for the first value.
Type /* to start a comment and */ to end a comment. A comment can span record images in the parameter member and can appear anywhere except in the middle of a keyword or a specified value.
Only comment statements can appear before the statement name on a record.
A statement continues until the next statement or until the end of records in the member. Continuation characters are not used to define a statement that spans parameter records.
You can abbreviate keywords to the smallest unambiguous length in the current statement. Statement names cannot be abbreviated.

Notes:

If an abbreviation matches more than one keyword on a statement, Tivoli Workload Scheduler for z/OS writes to the message log the TSO-parser message IKJ56704I parameter IS AMBIGUOUS. This can cause a subtask to end or Tivoli Workload Scheduler for z/OS itself to end.
The names of RODM classes, objects, and fields are case-sensitive. Ensure you preserve the case if you specify RODMOPTS statements in the parameter library. Also, if a name contains anything other than alphanumeric or national characters, you must enclose the name in double quotation marks.