IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

If an argument is not specified and the target is from the secondary input stream,
ROUTE ends when either the primary or secondary input stream disconnects.
Operand Descriptions
Usage Notes
Examples
label:
Specifies a valid label. A label can be supplied to the ROUTE stage as a
parameter or as input from the secondary input stream. The three-part syntax
(netid.luname/oper_id:) or two-part syntax (rmtalias/oper_id:) is defined and used
the same way as command labels used with CORRCMD stage with the
following exceptions:
v An asterisk (*) supplied for the operator name denotes the current operator
ID when the ROUTE takes place.
v A percent sign (%) can be used in place of the oper_id to indicate to send the
message to the authorized receiver at the target domain, as indicated by the
netid and luname.
v An exclamation (X'5A') can be used in place of the oper_id to indicate that
the message becomes a bulletin at the target domain, as indicated by the
netid and luname.
AUTHRCVR
Indicates the messages are sent to the authorized receiver in the local domain.
BULLETIN
Indicates a copy of the message is sent to every operator and autotask
currently logged on. A copy of the message is also issued to every operator
who subsequently logs on.
You can cancel a bulletin message by issuing a DOM command against it. For
example, from an operator station that still has a copy of the message
(ABC123E), issue the following command:
PIPE HELDMSG | LOCATE /ABC123E/ | NETV DOM CURMSG
v To send messages to a remote domain over IP, the IP address of the domain
must be defined using the RMTSYN statement in the CNMSTYLE member.
v The authorized receiver is determined by the individual message. For more
information, see the online help for the ASSIGN command (PRI and SEC
keywords).
Example: Sending a Message to OPER1
To send a message to OPER1, enter:
PIPE LITERAL /Hello/ | ROUTE /OPER1:
Example: Sending Multiple Messages
To send multiple messages to operators OPER1, OPER2, and NETOP1 from a
REXX Exec:
dest.1 = ’/OPER1:’
dest.2 = ’/OPER2:’
dest.3 = ’/NETOP1:’
dest.0 = 3
’PIPE (END &)’,
’| NETVIEW LIST TASK’, /* generate "a few" messages */
’| A: ROUTE ’, /* route to destination read from */
, /* below end of main pipeline */
PIPE ROUTE
Chapter 2. Pipeline Stages and Syntax 205