not-symbol when it immediately follows a separator is the character indi­
cating that the text should not be found in the message. If
the text following the not-symbol is found in the message,
then the message does not match that routing table entry.
The default character is "...,". See "Filtering Messages" for the use of TEXTSYM characters in routing table
entries:
3. The optional PROPCHK statement identifies the distributed nodes that the
host system is to check on. The RSCS nodeids of these distributed systems
must be specified in this statement. A programmable operator must be running
in the system operator virtual machine on the distributed systems being
checked. As many nodes may be specified on one statement as fit in an
80-column record. The programmable operator facility only reads the first 80 columns. Any number of PROPCHK statements may be entered to specify
different checking or response wait intervals for different RSCS nodes. The
PROPCHK statement must be after the LGLOPR statement.
Note: Nodes to be checked with PROPCHK must be systems running VM/SP Release 3, with a programmable operator in the system operator virtual
machine. I PROPCHK where:
ccc
ww
nodeid
Notes:
ccc ww nodeid [nodeid ... ]
is the checking interval. This interval, in minutes, indicates how
often acknowledgment requests are sent out to the specified nodes.
is the response wait interval. This interval is the number of min­
utes permitted to pass before a response must be received from the
specified node(s).
is a valid id of a system in the network.
a. The checking interval specified must be greater than the response wait
interval.
b. The nodeid of the logical operator must not be specified as a nodeid on this
statement.
4. The optional HOSTCHK statement specifies the time interval for checking
communication with the RSCS virtual machine at the logical operator node and
the wait time for a response. The HOSTCHK statement must be after the LGLOPR statement. I HOSTCHK ccc ww
where:
The Programmable Operator Facility 427

ccc is the checking interval. This interval, in minutes, indicates how
often acknowledgment requests are sent out to the specified nodes.
ww is the response wait interval. This interval is the number of min­
utes permitted to pass before a response must be received from the
specified node(s).
Note: The checking interval specified must be greater than the response wait
interval.
5. The optional LOGGING statement specifies whether messages or messages
and command responses are to be logged or not logged. If the LOGGING statement is not in the routing table, messages are logged and LOGGING is ON. If the LOGGING statement is in the routing table, one of the three oper­
ands must also be specified, because there is no default operand. I LOGGING 1 t OFF where: ON indicates that messages are to be logged while this RTABLE is
active, unless it is explicitly turned off using the SET LOGGING command.
ALL indicates that messages and programmable operator command
responses are to be logged while this R TABLE is active, unless it
is explicitly turned off using the SET LOGGING command. OFF indicates that messages are not to be logged while this RTABLE is
active, unless it is explicitly turned on using the SET LOGGING command.
6. The ROUTE statement indicates the end of the configuration statements and
the start of the routing entries. ROUTE This statement must follow the other statements specified in this section.
The LGLOPR and ROUTE statements are required in every routing table. An
example of these statements in a routing table is as follows: LGLOPR OPERATNS HOSTNODE TEXTSYM / $ --, PROPCHK S 1 NODE1 NODE2 NODE3 PROPCHK 3 1 NODE4 NODES HOSTCHK 2 1
LOGGING ALL ROUTE These special statements may be specified for each routing table in any order (as
long as LGLOPR is first and ROUTE is last) and with at least one blank separating
each parameter. The statements depend on the installation and, therefore, must be 428 VM/SP System Programmer's Guide