Look at the list of notation conventions to see how syntax is represented in this manual. The example following the list shows how the conventions are used.
Syntax Notation and Parameter Syntax Rules:
|
Example |
Function |
|---|---|
|
PROCESS |
Keywords appear in UPPERCASE. The minimum required portion of each keyword is UNDERSCORED. If a portion of or an entire keyword is not underscored, you can omit that portion of the keyword. |
|
AREA=area-name |
Variables appear in lowercase italics. You must substitute an appropriate value for each variable. |
|
[,TARGETROOT] |
Brackets indicate optional clauses. |
|
◄─ |
Points to the default in a list of choices. |
|
[,DSPLYINT={ |
Braces enclose two or more options. You must select one of the options. |
|
[,PRIORITY=( |
An ellipsis indicates that one or more options can be selected and entered in any order. |
|
Order of Parameter Statements |
The PROCESS statement must be entered first. The other three parameter statements can be entered in any order |
|
Continuing a Parameter Statement |
To continue a parameter statement onto the next record, key in a trailing comma. Do not split a keyword phrase between two records. |
|
Entering Blanks In Parameter Statements |
You can enter blanks (character spaces) to separate keywords and improve readability in a parameter statement without affecting processing. However, do not embed blanks within a keyword or value field. |
|
Entering Parameter Statements |
On an 80-character input record, you must enter all parameter syntax between positions 1 and 72, inclusive. |
|
Comments |
Enter an asterisk (*) in column 1 to indicate a comment. |
|
Series of Variables |
Parenthesis are required around a series of variables. Variables must be separated by commas. |

|
Copyright © 2014 CA.
All rights reserved.
|
|