module that is invoked to perform an action.
a parameter, which, in this case, is a userid or nickname.
invoked with a parameter, which is a routing table name.
Note that new action routines are not required to be in this format. The program
mable operator facility supports any desired number of action routines. Each one
is loaded separately when the programmable operator facility is initialized, or when
a LOADTBL command is issued.
The following sections describe the action routines that are supplied with the pro
grammable operator facility. These action routines (or subroutines in the case of
VM /
GET -
This routine sends programmable operator files, such as the log and feedback
files, to the user who requested the file via the
QUERY -Return a response to a user query
This routine returns the fileid of the currently active routing table or returns
the status of programmable operator node-checking or logging to the user who
issued the command.
This routine stops or resumes the periodic checking of the distributed systems
or the host system, or the logging of messages in the log file.
This routine stops the programmable operator operation after processing cur
rently queued messages. The programmable operator virtual machine returns
control to
This routine attaches the date and time received to the head of the incoming
message and writes
more information.
This routine is invoked when the programmable operator CMD command is
issued. The text following
be executed in the programmable operator machine, according to the
mand is returned to the authorized user who invoked the CMD command.
Authorized users of the CMD command should be aware of the following:
The Programmable Operator Facility 439