Automatic Invocation
If you wish, you can set up the programmable operator facility to start running
when the system isIPLed and to restart automatically in the event of CP system
restart. This can be done as follows:Place an "IPL CMS PARM AUTOCR" entry for programmable operator's vir
tual machine in theCP directory. This can be done even if the programmable
operator virtual machine is theCP system operator. Place the following entry in the PROFILE EXEC of the programmable opera
tor's virtual machine:
EXEC PROPST rtable-name [DISConn]
You can precede or follow the invocation of thePROPST EXEC by the invo
cation of any virtual machine commands that you wish to have executed before
or after the programmable operator facility is invoked. Virtual machine com
mands'that are placed after the invocation of thePROPST EXEC are not exe
cuted until the programmable operator facility is stopped.
If you want the programmable operator to run in other than the operator's vir
tual machine, place anAUTOLOG entry for the programmable operator's vir
tual machine in thePROFILE EXEC of the system operator or the AUTOLOG user.
Once this is complete, if the logical operator is not already logged on, he/she
should do so on the appropriate system.
The following example shows how to place entries in theCP Directory and the PROFILE EXEC of operator's virtual machine. These entries automatically
invoke the programmable operator facility in the operator's virtual machine when
the system isIPLed. The userid of the programmable operator virtual machine is "OPERATOR". The default, "PROP RTABLE", is the name of the routing table
being used.CP directory entries: USER OPERATOR password 512K 1024K ABCDEFG
IPL CMS PARMAUTOCR Entries in the PROFILE EXEC of the Operator's virtual machine:
EXEC PROPST DISCONN
Once these changes (or similar ones) have been made,IPLing the system causes
the programmable operator to be automatically invoked in the disconnected system
operator virtual machine. After the DISCONNECTED message has been written
to the console, indicating that the system operator virtual machine is disconnected,
the operator can log on to whatever virtual machine he/she is normally supposed to
use, for example, the logical operator virtual machine specified in the routing table.
The Programmable Operator Facility 447
If you wish, you can set up the programmable operator facility to start running
when the system is
restart. This can be done as follows:
tual machine in the
operator virtual machine is the
tor's virtual machine:
EXEC PROPST rtable-name [DISConn]
You can precede or follow the invocation of the
cation of any virtual machine commands that you wish to have executed before
or after the programmable operator facility is invoked. Virtual machine com
mands'that are placed after the invocation of the
cuted until the programmable operator facility is stopped.
If you want the programmable operator to run in other than the operator's vir
tual machine, place an
tual machine in the
Once this is complete, if the logical operator is not already logged on, he/she
should do so on the appropriate system.
The following example shows how to place entries in the
invoke the programmable operator facility in the operator's virtual machine when
the system is
being used.
IPL CMS PARM
EXEC PROPST DISCONN
Once these changes (or similar ones) have been made,
the programmable operator to be automatically invoked in the disconnected system
operator virtual machine. After the DISCONNECTED message has been written
to the console, indicating that the system operator virtual machine is disconnected,
the operator can log on to whatever virtual machine he/she is normally supposed to
use, for example, the logical operator virtual machine specified in the routing table.
The Programmable Operator Facility 447