Utilities › CA JARS File Utility Commands Coding Conventions
CA JARS File Utility Commands Coding Conventions
The File Utility accepts nine command statements. They are:
|
INPUT=
|
CHANGE=
|
EDIT
|
|
OUTPUT=
|
SPECS=
|
EXIT=
|
|
FIND=
|
DUMP=
|
HEADER=
|
Each command, except the EDIT command, has keywords and/or parameters that further qualify the capabilities of the File Utility.
Use the following conventions when coding File Utility Commands:
- With the exception of the EDIT command, all File Utility Commands must be coded with an equals sign (=) immediately following the command name.
- All commands must be of a card-image, fixed-format, 80-byte record.
- Commands cannot be continued however, INPUT, FIND and CHANGE commands can be repeated indefinitely.
- Unless otherwise stated, a comma must separate each keyword and/or parameter.
- Comments can be coded on any command, providing that at least one (1) blank separates the last keyword/parameter and the comment.
- All commands can use up to 79 bytes of a statement. Byte 80 is reserved.
- Comments can be entered on separate statements provided that the first nonblank character is an asterisk (*).
- The INPUT, FIND, CHANGE, and SPECS commands are viewed by the File Utility as having a logical relationship. An INPUT command must precede FIND, CHANGE, and SPECS commands associated with that INPUT.
- The only required command is INPUT.
