these characters are found, PROPRTCV informs you and then prompts
you for different characters. You can also exit and change the texts that
caused the conflict. PROPCHK statements are added, if desired. PROPRTCV prompts you
for this information.
A HOSTCHK statement is added, if desired. PROPRTCV prompts you
for this information.
A ROUTE statement is placed after all the above statements have been
completed.
An entry for the new SET command is added with text" ISET I", message
type 1, action routine DMSPOR, and parameter SET. PROPRTCV prompts you for any authorization desired for this entry. See "DMSPOR -
Miscellaneous supplied action routines" for more information on the SET
command.
Note: The SET entry is simply placed after the ROUTE statement. This is
probably not where you want it. Move the entry when the routing table
conversion is completed.
For each routing table entry, PROPRTCV 2. Encloses the specified text with the blank-separator, (I), for the specified
length of the text.
3. Generates a starting column value and an ending column value from the exist­
ing displacement and length values.
4. Converts an entry with action routine DMSPOR and parameter TOLGLOPR to the action routine name DMSPOS. PROPRTCV prompts you for the rout­
ing target information to be used as the parameter.
5. Converts an entry with action routine DMSPOR and parameter LOADTBL to
the action routine name DMSPOL and no parameter.
Invoking the Programmable Operator Facility
Manual Invocation
Before loading and invoking the programmable operator facility, load CMS in the
virtual machine that will be running the operator facility. Use the PROPST EXEC to manually invoke the programmable operator facility.
The PROPST EXEC drops any IBM-supplied programmable operator routines that
are currently loaded as a nucleus extension, and loads the programmable operator
as a nucleus extension. It then invokes the programmable operator facility with the
specified RTABLE. If you do not specify a routing table, the RTABLE name
defaults to "PROP". You may specify a disconnect parameter to disconnect the
programmable operator before it is invoked. The format of the invocation EXEC is as follows:
The Programmable Operator Facility 445

I ____ __ ____ [ __ D_I_S_C_o_n_n __ ] __________________ Optionally, you can take the following steps each time you invoke the programma­
ble operator facility:
1. Issue a FILEDEF command to assign a CMS filename to the PROPLIB LOADLIB file so CMS can read and load from it. This is done with the fol­
lowing command:
FILEDEF PROPLIB DISK PROPLIB LOADLIB *
2. N ext, load the programmable operator program as a CMS nucleus extension
via the NUCXLOAD command. Issue the command as follows: NUCXLOAD PROP DMSPOP PROPLIB (See the VM/SP CMS Command and Macro Reference for more details on the NUCXLOAD command.) These first two steps may be omitted for subse­
quent invocations as long JOU do not: IPL CMS or
Have a CMS abend from which the programmable operator does not
automatically recover.
Following its loading as a CMS nucleus extension, invoke the programmable opera­
tor facility as if it were a CMS command. The format of the invocation is: PROP [rtable-nameJ PROP where:
rtable-name is the filename of the routing table that is to be used for the pro­
grammable operator facility. "PROP" is the default filename of
the routing table if no other is specified at invocation.
The action routines named in the default or specified routing table are in turn
loaded as CMS nucleus extensions. If the programmable operator facility cannot
find an action routine that is named in the routing table, the user receives an error
message and is informed of all detectable routing table errors before the program­
mable operator facility terminates operation. When all of the required action rou­
tines have been loaded, a message is typed on the programmable operator's console
indicating that the programmable operator facility has started. The programmable
operator facility then waits for either an incoming message or a programmabie
operator console command (STOP and SET are the only valid commands). The
operator can disconnect at this point by having specified the DIS Conn parameter
for the PROPST EXEC or by entering CP (pressing the PAl key or equivalent)
and typing CP DIS CONN. 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 hel she is normally supposed to
use, for example, the logical operator virtual machine specified in the routing table.
446 VM/SP System Programmer's Guide