Example: start commands and variables

The variable is resolved when the CSM subsystem application processes the command and the variable is read from the SHARED variable pool. If the variable is not present in the SHARED pool, it resolves as the variable name (as in REXX language coding).

Using a compound variable is the same as a simple variable. For example, if an object has a start command defined as

the variable AO.CSMDAY is treated in the same manner as a REXX compound symbol: AO is the stem and CSMDAY is the tail.

On Monday, the variable resolves into shared variable AO.MON. It contains the value STUFF. The resulting command is as follows:

You can set the variable with a Rule, an EXEC, or an entry in the BBIVAR xx member. The variable must already be defined when CSM executes the defined command.

This allows you to specify Start and Stop commands that can change periodically. It also provides flexibility for object definitions in the shared repository whose Started Task name is the same across multiple partners but use significantly different parameters from system to system.

All commands entered in any of the command fields: Start , Stop , Post Start , Post Stop , Cancel, and Recovery must be prefixed by one of the following control characters:

• Period ( . )
• Pound sign (#)
• Forward slash (/)
• Question mark (?)
• Percent sign (%)

Single quotation marks can be used in commands. The quotation marks must be doubled, so that they are properly processed; for example:

CSM running in the BBI-PAS strips out the extra quotation marks and sends the command to the system for execution. If an object used the this command, CSM translates to the following command:

You can also use values defined in the static system symbol list. These values must be prefixed with two ampersand signs (&&); for example:

The resolved command that is passed to MVS is:

When MVS processes this command, &SUBAREA is substituted with a value defined in the static system symbol list.

If the command is not prefixed with a control character, MainView AutoOPERATOR tries to process the command as an EXEC using EXEC parameters.

You can use the Command Specifications panel to also specify the following values:

• Start and Stop Command Time Out values (in minutes)
• Start Command Limit value
• Whether to reset the Start Command count where a Y or N specification determines whether the object command count shared variable is reset each midnight to zero
• Conditional Start or Conditional Stop setting where a Y setting in either field will cause the Conditional Commands Specification panel to appear

Press Enter to display the Conditional Command Specification panel.