The Routing Table
ing table and loads it into virtual storage. For each action routine specified in the
routing table, an EXEC file or a corresponding member in a CMS simulatedOS load library named PROPLIB LOADLIB must exist. If an EXEC does not exist,
theLOADLIB member is loaded as a nucleus extension-via the NUCXLOAD command. If both exist, the EXEC takes precedence.
If upon invocation, the programmable operator facility cannot find an action rou
tine named in the routing table, an error message is issued, and the programmable
operator facility terminates operation.Otherwise, the programmable operator facil
ity is fully initialized, and writes a message to the programmable operator's console,
to the logical operator, and to theLOG file, indicating that the programmable
operator facility has started. The programmable operator facility then waits for
either an interrupt indicating an incoming message or an interrupt from the console.
Note: If the user enters a nodeid into the SYSTEM NETID file that is invalid as a
CMS file type, the programmable operator cannot start because it is not be able to
open the log file.
The routing table is a CMS file that contains the information used to control the
operation of the programmable operator facility. The routing table enables the
programmable operator facility to recognize a message as a command, to determine
the action to take when a message comes in, and to recognize the authorized users
of programmable operator functions.
Howtile Programmable Operator Facility Uses tile Routing Table
Routing Table Entry Formats
When the programmable operator facility receives anlUCY interrupt with an
incoming message, the active routing table is searched to find a matching entry.
When the routing table is searched, all fields are checked. In order for a match to
occur, each field must either match or be blank. If a matching entry is found, that
entry contains information pertaining to any action to be taken. The action routine
name tells the programmable operator facility which action routine to invoke when
a routing table entry matches the incoming message. If no matching entry is found
in the active routing table, no action is taken besides logging the message.
The order that the entries are placed in the routing table affects the way the pro
grammable operator facility performs. The routing table is searched from top to
bottom until a match is found. As the table is searched, lines that begin with an
asterisk (*) in column 1 are ignored, and therefore may be used to place comments
in the routing table. Also, lines that are completely blank are ignored in the routing
table search and can be used to separate lines of text for easier reading. All entries
must be made in upper case.
Note: The routing table format is changed from the initial version of the program
mable operator facility in VM/SP Release 2. The original format from Release 2 is
not compatible with later versions of the programmable operator facility. The rout
ing tables must be converted to reflect this change. See"Routing Table Conversion" later in this section. I Every routing table must have specific configuration information in the first records
of the routing table file (filetype RTABLE) that are not comments or blank lines.
TheProgrammable Operator Facility 425
ing table and loads it into virtual storage. For each action routine specified in the
routing table, an EXEC file or a corresponding member in a CMS simulated
the
If upon invocation, the programmable operator facility cannot find an action rou
tine named in the routing table, an error message is issued, and the programmable
operator facility terminates operation.
ity is fully initialized, and writes a message to the programmable operator's console,
to the logical operator, and to the
operator facility has started. The programmable operator facility then waits for
either an interrupt indicating an incoming message or an interrupt from the console.
Note: If the user enters a nodeid into the SYSTEM NETID file that is invalid as a
CMS file type, the programmable operator cannot start because it is not be able to
open the log file.
The routing table is a CMS file that contains the information used to control the
operation of the programmable operator facility. The routing table enables the
programmable operator facility to recognize a message as a command, to determine
the action to take when a message comes in, and to recognize the authorized users
of programmable operator functions.
How
Routing Table Entry Formats
When the programmable operator facility receives an
incoming message, the active routing table is searched to find a matching entry.
When the routing table is searched, all fields are checked. In order for a match to
occur, each field must either match or be blank. If a matching entry is found, that
entry contains information pertaining to any action to be taken. The action routine
name tells the programmable operator facility which action routine to invoke when
a routing table entry matches the incoming message. If no matching entry is found
in the active routing table, no action is taken besides logging the message.
The order that the entries are placed in the routing table affects the way the pro
grammable operator facility performs. The routing table is searched from top to
bottom until a match is found. As the table is searched, lines that begin with an
asterisk (*) in column 1 are ignored, and therefore may be used to place comments
in the routing table. Also, lines that are completely blank are ignored in the routing
table search and can be used to separate lines of text for easier reading. All entries
must be made in upper case.
Note: The routing table format is changed from the initial version of the program
mable operator facility in VM/SP Release 2. The original format from Release 2 is
not compatible with later versions of the programmable operator facility. The rout
ing tables must be converted to reflect this change. See
of the routing table file (filetype RTABLE) that are not comments or blank lines.
The
