Issuing commands through the OM API
You can enter type-1 commands from an IMS terminal, such as the MTO terminal or an end-user terminal. You can enter many type-1 commands and all type-2 commands through the SPOC and OM API. When you enter a command through the OM API, OM can route the command to all IMS systems that can process the command. OM consolidates the command responses from the IMS systems into one buffer as they are received.
If the command has local scope only and is entered from the IMS Master Terminal, IMS end user terminal, or the IMS automated operator program (AOP), then the command is processed only by the local IMS where the command was entered. However, if a resource structure is part of the IMSplex, some commands, such as /STOP USER and /STOP NODE, have a global status in RM. If you enter those commands from a SPOC, they might be routed to all of the IMS systems in the IMSplex and have a global effect. The TSO SPOC allows you to route commands to individual IMS systems.
CSL provides the type-2 command format. The benefits of this format are listed below:
- Elimination of resource name and command keyword conflicts
- Better command syntax checking using the BPE parser
- Simplified set of command verbs
- Parallel command processing
- Filters and wild cards for resource name selection
- Filtering and displaying of only selected output fields for QUERY command output
- Only one IMS with access to global information
Commands entered using this command format can only be entered through a SPOC. As a result, the command format cannot be entered through the system console, master terminal, end user terminal, DL/I call, APPC client, or through the OTMA interface. The format is based on simplified BPE parse rules. These commands work with the single-system image that an IMSplex provides of IMS systems sharing databases and queues in the IMSplex.
The type-2 command format is as follows. The keywords and parameters are optional:
ActionVerb ResourceType Keyword(parameter) Keyword(parameter) . . .