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

NetView Pipelines Device Drivers
292 Programming: Pipes
NCCF NETVIEW CNM19 OPER6 03/20/10 11:12:25
| CNM19 READY FOR LUNCH ?
Processing steps:
1. The LITERAL stage writes the message READY FOR LUNCH? to the pipeline.
2. The NETVIEW stage has an operand, the MSGROUTE command. The pipe
contains one message, the READY FOR LUNCH message. The NETVIEW stage
invokes the MSGROUTE command one time to act on the message in the
pipeline, routing it to OPER6.
If there are multiple messages in the pipeline, the NETVIEW stage invokes
MSGROUTE once for each message. No copy of the routed message is written
to the pipeline output stream. If the stage has an error, the MOE option causes
a DWO369I message, with nonzero return code, to be placed in the pipe.
Example 4: Acting on a Pipeline Message
This example shows how to use the NETVIEW stage, without a command
parameter, as a non-first stage to process messages in the pipeline.
PIPE LITERAL ? LIST STATUS=TASKS ? | NETVIEW MOE | LOCATE /NOT ACTIVE/
| CONSOLE
Output from the pipeline follows:
NCCF NETVIEW CNM29 OPER3 02/01/10 09:07:40
* CNM29 PIPE LITERAL ? LIST STATUS=TASKS ? | NETVIEW MOE | LOCATE /NOT
ACTIVE/| CONSOLE
- CNM29 TYPE: OPT TASKID: TASKNAME: SQLOGTSK STATUS: NOT ACTIVE
- CNM29 TYPE: OPT TASKID: TASKNAME: ALIASAPL STATUS: NOT ACTIVE
- CNM29 TYPE: OPT TASKID: TASKNAME: DSISVRT STATUS: NOT ACTIVE
- CNM29 TYPE: OPT TASKID: TASKNAME: DSIROVS STATUS: NOT ACTIVE
- CNM29 TYPE: OPT TASKID: TASKNAME: CNM29VMT STATUS: NOT ACTIVE
- CNM29 TYPE: OPT TASKID: TASKNAME: CNM29BRW STATUS: NOT ACTIVE
- CNM29 TYPE: OPT TASKID: TASKNAME: DSIKREM STATUS: NOT ACTIVE
- CNM29 TYPE: OPT TASKID: TASKNAME: VPDTASK STATUS: NOT ACTIVE
- CNM29 TYPE: OPT TASKID: TASKNAME: DSIQTSK STATUS: NOT ACTIVE
- CNM29 TYPE: OPT TASKID: TASKNAME: DSIRQJOB STATUS: NOT ACTIVE
- CNM29 TYPE: OST TASKID: RESOURCE: A01A441 STATUS: NOT ACTIVE
- CNM29 TYPE: OST TASKID: RESOURCE: A01A442 STATUS: NOT ACTIVE
- CNM29 TYPE: OST TASKID: RESOURCE: A01A443 STATUS: NOT ACTIVE
- CNM29 TYPE: OST TASKID: RESOURCE: A01A444 STATUS: NOT ACTIVE
- CNM29 TYPE: OST TASKID: RESOURCE: A01A445 STATUS: NOT ACTIVE
- CNM29 TYPE: OST TASKID: RESOURCE: A01A446 STATUS: NOT ACTIVE
- CNM29 TYPE: OST TASKID: RESOURCE: STATUS: NOT ACTIVE
- CNM29 TYPE: OST TASKID: RESOURCE: STATUS: NOT ACTIVE
- CNM29 TYPE: OST TASKID: RESOURCE: STATUS: NOT ACTIVE
- CNM29 TYPE: NNT TASKID: RESOURCE: STATUS: NOT ACTIVE
- CNM29 TYPE: NNT TASKID: RESOURCE: STATUS: NOT ACTIVE
- CNM29 TYPE: NNT TASKID: RESOURCE: STATUS: NOT ACTIVE
- CNM29 TYPE: NNT TASKID: RESOURCE: STATUS: NOT ACTIVE
- CNM29 TYPE: NNT TASKID: RESOURCE: STATUS: NOT ACTIVE
Processing steps:
1. The LITERAL stage writes the LIST STATUS=TASKS command to the pipe.
2. The NETVIEW stage reads the message in the pipe (the LIST command) and
separates the words into the command and its arguments. The command is
then invoked. MOE writes the DWO369I message to the pipeline if the stage
generates a nonzero return code. In this example, DWO369I was not generated.
If there are multiple messages in the pipeline, the NETVIEW stage runs one
time for each message.