*------------------------
*T
*E
*x
*T
*------------------------
shows an example of unrestricted authorization for the FEEDBACK command. A
message sent with the FEEDBACK command is passed to module DMSPOR, which supports most of the programmable operator commands. The TOFB param­
eter invokes the proper action routine contained in module DMSPOR that writes
the message to the FEEDBACK file. (See "The Feedback File" later in this sec­
tion or the VM jSP Operator's Guide for more information on the FEEDBACK
command.)
Note: In the following examples, the TYPE (lUCY message class) field is left
blank to allow the FEEDBACK (or FB) command to be issued with any class of lUCY message. The ECOL fields are 9 and 3 because the character string being
looked for is FEEDBACK or FB followed by a blank, for example, "FEEDBACK " or "FB " would match.
S
C
o
L
E
C
o
L
T
Y
P
E
-------- U S
E
R
--------
-------- -------- --------
N A P 0 C A
D T R
E N M
-------- -------- -------- * PLACE A FEEDBACK MESSAGE IN THE PROP FEEDBACK FILE
*------------------------
/FEEDBACK /
/FB /
9 DMSPOR TOFB 3 DMSPOR TOFB Figure 55. Example of Uncontrolled Authorization
*------------------------
*T
*E
*x
*T
*------------------------
Authorization can be restricted to users at a particular network node by specifying
only the nodeid. In Figure 56, only users at NODEl are authorized to issue the
FEEDBACK command.
S
C
o
L
E
C
o
L
T
Y
P
E
-------- U S
E
R
--------
--------
N 0 D
E
--------
-------- --------
A P
C A
T R
N M
-------- --------
* PLACE A FEEDBACK MESSAGE IN THE PROP FEEDBACK FILE
*------------------------
/FEEDBACK /
/FB /
9 NODE1 DMSPOR TOFB 3 NODE1 DMSPOR TOFB Figure 56. Example of Restricting Authorization by Nodeid
When a userid and nodeid are specified, only that user at the specified node is
authorized to match that entry. In Figure 57, only JOHNDOE at NODEl and JANEDOE at NODE2 are authorized to place messages in the feedback file.
The Programmable Operator Facility 437

*------------------------ -------- -------- -------- --------
*T S E T U N A P *E C C
y S 0 C A
*x 0 0 P E D T R
*T L L E R E N M
*------------------------ -------- -------- -------- -------- "." PLACE A FEEDBACK IvlESSAGE IN THE PROP FEEDBACK FILE
*------------------------ -------- -------- -------- --------
/FEEDBACK / 9 JOHNDOE NODE1 DMSPOR TOFB /FEEDBACK / 9 JANEDOE NODE2 DMSPOR TOFB /FB / 3 JOHNDOE NODE1 DMSPOR TOFB /FB / 3 JANEDOE NODE2 DMSPOR TOFB *------------------------
* SEND REMAINING REQUESTS AND COMMANDS TO THE LOGICAL OPERATOR *------------------------ --- -- -------- -------- -------- DMSPOS LGLOPR Figure 57. Example of Restricting Authorization by Userid and Nodeid
Action Routines
Since the user must explicitly issue the FEEDBACK or FB command to have a
message placed in the feedback file, action routine DMSPOR TOFB must be speci­
fied in the routing table to carry out the required action. Any user attempting to
issue the FEEDBACK command that is not authorized by the routing table in
Figure 57 will have their command sent to the logical operator as a message via
action routine DMSPOS LGLOPR, as specified by the last record of the routing
table.
Additional userids and nodeids may be added to the table to grant authorization to
issue these commands. Conversely, userids and nodeids may be removed to revoke
authorization.
Action routines, programs that receive control in response to the match of a mes­
sage and a routing table entry, handle a particular type of message or command
intercepted by the programmable operator facility. A set of action routines is pro­
vided with the programmable operator facility. These need no tailoring to provide
the installation with the control and function needed to operate the programmable
operator facility. Other action routines may be written by the installation as
desired to perform specific functions. Thus, the programmable operator facility
may be extended simply by the addition of a new action routine.
If an action routine abends, abend error messages are sent to the logical operator
and the requester (if any). Control is returned to the point in the programmable
operator facility immediately following the action routine call.
Note: Programs written in Basic Assembler Language can access the parameter list
built by the programmable operator facility. The programmable operator parame­
ters are available in a different fashion for EXEC action routines
9
• For information
on the action routine interface, see "The Action Routine Interface" later in this
section.
Description of Supplied Action Routines
The action routines supplied with the programmable operator facility are DMSPOR, D?v!SPOS, and Dr-.1SPOL. A parameter must be supplied for module
9 EXECs may be written using the System Product Interpreter, EXEC 2, or CMS EXEC languages.
438 VM/SP System Programmer's Guide