ThiS can be accomplished by passing the name of the saved system to the CMS Batch Facility via the optional "sysname" operand in the CMSBATCH command
line.
The batch facility saves the name of the saved system until the end of the first job,
at which time it stores the name in the IPL command line both as the "device address" and as the P ARM character string. The latter entry informs the CMS initialization routine (DMSINS) that a saved system has been loaded and that the
name is to be saved for subsequent IPL procedures.
Note: When using the CMS SET command, the BLIP operand is ignored when
issued from the CMS batch machine.
The eMS Batch Facility 421

The Programmable Operator Facility
Overview I Use in a Single System I Use in Distributed Systems
The Programmable Operator Facility is designed to increase the efficiency of sys­
tem operation and to allow remote operation of systems in a distributed data proc­
essing environment. It does this by intercepting all messages/requests directed to
its virtual machine and by handling them according to pre programmed actions. It
determines whether a message is to be simply recorded for future reference, wheth­
er the message is to be acted upon, or whether the message is to be sent on to the
operator to handle.
When the programmable operator facility is operational in a single-system envi­
ronment, it can:
Ease message traffic to the system operator, by:
Filtering (logging) non-essential, information-only messages
Routing messages (for example, I/O intervention requests) to someone else
for specialized action.
Increase productivity, by freeing the system operator from certain routine
responses or tasks. Such responses (whether they consist of one or a series of
commands, whether VM/SP or guest operating system) may be prepro­
grammed to execute automatically upon receipt of a given message.
Thus, only essential, non-routine messages (that is, those requiring the skill and
experience of a system operator to handle) are sent on to the operator for
response or action.
The capabilities of the programmable operator, outlined above, also allow for the
remote operation of systems in a distributed environment. When the programma­
ble operator facility is operational in a distributed system, it can:
Issue responses and perform tasks that do not require an on-site operator
Filter (log) non-essential, information-only messages
Route messages requiring on-site (that is, manual) intervention to someone,
not necessarily an operator, at the distributed site for action
Route messages that require the skill and experience of a system operator to
handle to the operator at the host system. The operator at the host site can
also send commands to the programmable operator facility to control its opera­
tion, as well as commands to execute on the distributed system to control the
system itself.
By running the programmable operator facility on VM/SP systems distributed at
several different locations (network nodes), one operator at a host site can control
a network of systems.
422 VM/SP System Programmer's Guide