Command language conventions

Commands

The PFPSYSIN or PFPOPTS DD statement must be followed by a valid Fast Path/EP command. A command set is defined as a command, the command keywords and parameters, any subcommands, and the subcommand keywords and parameters.

You can abbreviate command names within certain guidelines. You can truncate the command name to as few as three characters as long as the truncated string uniquely identifies the command. For example, the ANALYZE command can be coded as ANA since these leading characters are unique to the ANALYZE command.

Subcommands

Subcommands can be used with certain commands to modify or enhance the primary function. A subcommand set is defined as a subcommand, its keywords, and keyword parameters. Valid commands and subcommands are shown beginning with the table in PFPSYSIN commands and subcommands for PFCMAIN.

You can abbreviate subcommand names within certain guidelines. You can truncate the subcommand name to as few as three characters as long as the truncated string uniquely identifies the subcommand. For example, the REPORT subcommand can be coded as REP since these leading characters are unique to the REPORT subcommand.

Keywords

Keywords follow a command or subcommand and invoke specified or default parameters. All keywords are nonpositional and can be specified in any order. Separate the keyword and its parameter with an equal sign, e.g., keyword=parameter, or by using parentheses, e.g., keyword(parameter). If multiple parameters are specified, the list of parameters must be enclosed within parentheses, e.g., keyword=(parameter, parameter, parameter); the equals sign (=) is optional. Keywords must be separated by commas.

You can abbreviate keyword names within certain guidelines. You can truncate the keyword to as few as three characters as long as the truncated string uniquely identifies the keyword. For example, the POINTER_VALIDATION keyword can be coded as POI since these leading characters are unique to the POINTER_VALIDATION keyword.

A truncated keyword name must be unique only among valid keywords for the command or subcommand on which it is coded. The truncated name does not have to be unique across with all Fast Path/EP Series command language keywords. For example, on the ANALYZE command, the INPUT_DSN_MASK keyword can be truncated to INP, because the truncated keyword is distinguishable from all other valid ANALYZE command keywords. On the UNLOAD command, however INP would not be sufficient to distinguish it from the INPUT_THREADS keyword.

Parameters

Some keywords require only one parameter and some require more than one. Some keywords accept a list of parameters. Keywords require either numeric, character, or character string values. Lists of parameters must be contained within parentheses and separated by commas.

Some parameters are specified as predefined names. For example, the valid values for the POINTER_VALIDATION keyword are FULL, QUICK, OFF and NONE. The value names can be truncated to as few as three characters as long as the truncated string uniquely identifies a valid value for the keyword.

Comments

Comments in the PFPSYSIN or PFPOPTS command set are designated by an asterisk (*) character in column 1. If two consecutive slash characters (//) appear anywhere in a command line, the remainder of that command line is treated as a comment.

Separator characters

One or more commas can appear between keywords. Commas are used to separate parameters.

Parentheses are used to group listed parameters following a keyword. Commas are used to separate listed parameter entries inside parentheses, following the keyword construct. For example, IAREA=(a,b,c,d,...).

Continuation characters

There are no continuation characters. All commands, subcommands keywords are free in form, and can be continued from one line to the next.