Command structure

The method used by BMC ThruPut Manager to recognize commands depends on your installation:

• BMC ThruPut Manager can use the subsystem interface and a communications character string (COMCHAR) to recognize commands. This is the simplest technique and is considered the normal method of operating, therefore examples and discussions in this space assume that you are using this technique.
• TM commands can be issued using the MODIFY (F) command interface. While fully supported, this method is considered an exception, used in rare circumstances such as running out of COMCHARs. Examples and discussions therefore do not include this technique.

Using the MODIFY command interface

If your installation uses the MODIFY command interface, replace the COMCHAR in the descriptions in this space with:

where:

Is the short form of the z/OS MODIFY command.

Is the identifier used for the proc used to start TMSS. The identifier used in the sample proc shipped with BMC ThruPut Manager is TM.

Is the BMC ThruPut Manager command as described in this space.

Note that the MODIFY interface is always available, even if your installation uses COMCHAR and the subsystem interface. If, for some reason, the subsystem interface is not functioning, you can use the MODIFY interface.

Using the subsystem interface

The command character (COMCHAR) used to distinguish BMC ThruPut Manager commands can be modified by your installation. All examples in this spacel use the default command character " / ".

BMC ThruPut Manager command structure

BMC ThruPut Manager commands have the following structure:

is the default character that identifies the command as a BMC ThruPut Manager command to the subsystem interface. Your installation might have modified this character. If so, it could have been replaced by a character string, as described in the Installation Guide. Alternatively, your installation might use the MODIFY command interface, as described above.

is the function, normally a three-character acronym. For example, "JVL" indicates that the command is to be handled by the JVL function.

is the actual command to be performed by the particular function.

Routing command output to SPS

In addition to supporting the standard z/OS keyword L= to redirect command output, all BMC ThruPut Manager commands that issue multi-line responses can be directed to use SYSOUT Printing Services instead of a console for their output. This is done by specifying the SYSOUT keyword on the command:

is the keyword indicating that you want to direct the output to SPS instead of a console. This keyword is mutually exclusive with the L= keyword.

is the name associated with a set of SYSOUT characteristics by SPS. This name is optional; if not specified, SPS uses its default characteristics for the output.

The SYSOUT keyword is only effective for successful commands. If an error is detected in the command input or in processing the command, the output is routed back to the issuing console. If the command is successful, a confirmation message is sent to the issuing console. If the output is held, this message contains a DD name that can be used to examine or release the output.

Authorizing the use of operator commands

BMC ThruPut Manager depends on your installation's security facility (such as RACF, ACF2, or Top Secret) to restrict user authority to issue specific operator commands. BMC ThruPut Manager simply makes a System Authorization Facility (SAF) call to determine whether a user is authorized to issue a specific operating command.

The restrictions can be set at the function or command level. This means that all commands will be protected under the OPERCMDS class by a resource of

where:

BMC ThruPut Manager function (e.g. JAL, JBS, JLS)

ThruPut Manger command (e.g. DISPLAY, REFRESH)

Usually display commands only require READ authority whereas commands that alter (e.g. JAL REFRESH) require UPDATE authority.

SAF security for BMC ThruPut Manager operator commands custom option UM0041 is disabled by default. To define this custom option use the TMPARM initialization statement. Details of the TMPARM initialization statement can be found in the Installation Guide. To enable UM0041 use TM CUSTOM command described in the Command-Reference-guide.

For a list of functions, commands, and resources, refer to Functions-commands-and-SAF-resources.

BMC ThruPut Manager command organization

Normally there are two basic approaches to command organization:

1. The commands are organized by the type of action you are requesting. For example:

   /DISPLAY keyword1,...,keywordn

2. The commands are structured first by the component you want to talk to, and then by the action. For example:

   /JLS DISPLAY keyword1,...,keyword

Both approaches have advantages and disadvantages. For small products, with a limited number of functional components, the organization centered around "the action wanted" is normally the best approach. You only have to remember the name of the "action" you want done. In the case of DISPLAY what could be more simple?

As usual, things get a bit more complicated as products reach certain size and include a significant number of related but independent functions. The syntax of the DISPLAY command becomes too complicated because somewhere in the command you must indicate "display what by whom". We are all too familiar with products that have command syntax descriptions spanning several pages. In this case, the alternate model of "function-action" becomes more manageable. First you indicate "who" is to process your command, then what "action" is to be done. The drawback is that you must remember the function identifier, but the command syntax becomes a lot simpler and much more stable.

This section introduces you to the different functions available. The following table shows the functional identifications (IDs) of the commands, a brief explanation of the actual function, and the page in this section where the purpose and commands associated with the function are documented. The table, as well as the rest of the section, is presented in alphabetic order by function.