Syntax Model Command Language › Elements of a Command Model › OPERAND Clause

OPERAND Clause

CP commands use many different types of operands. The syntax model command language provides a number of ways to define the attributes of a command operand. It is very important that you define operands correctly in the command models. Therefore, knowing the attributes of the operand is essential.

We explain eight formats of the OPERAND clause in this section. You can use each format to describe a different type of operand.

Constants (format 1)

Describes an operand that always has a constant value. For example, all keyword operands are constants.

Variables (format 2)

Describes an operand where you enter a value. For example, all device address operands are variables.

Groups (format 3)

Describes a group of related operands by calling a GROUP clause. Each GROUP clause contains one or more OPERAND clauses.

Spool Related (format 4)

Describes operands that are related to spool files or unit record device names.

Another Operand's Default (format 5)

Signals that the value specified for an operand is also the default value for another operand. At present, only the supplied ATTACH model uses this format.

Effector Operands (format 6)

Describes operands that affect the way CP processes other operands. For example, many supplied models use this format to describe operands that accept a device address range (DETACH 0180-0188).

Mutually Exclusive (format 7)

Describes two or more mutually exclusive operands.

Interpretation Control (format 8)

Overrides the normal flow of a command as it goes through the CA ACF2 for z/ VM model interpreter. This is very useful for describing a command that has many similar formats.

We describe each of these formats individually with examples of how to use them in the CA ACF2 for z/ VM-supplied models.