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

Return Codes
The following return codes are reported when the MOE operand is used.
Examples
Return Code
Meaning
8 A timeout occurred (message interval exceeded).
12 A GO command was entered.
16 A task executing a thread terminated.
32 An ABEND occurred on a task executing a thread.
Example: Causing a Wait with CORRWAIT
To display We will now wait 9 seconds. and wait for nine seconds, enter:
PIPE CORRWAIT 9
| LITERAL /We will now wait 9 seconds./
| CONSOLE
Example: Using CORRWAIT to Wait for Messages
To issue the NetView LIST STATUS=OPS command for a logical unit (LU) named
A157C9 in a remote domain, allow 60 seconds for each resulting asynchronous
message to return to the pipeline and display the results, enter:
PIPE NETVIEW RMTCMD LU=A157C9,LIST STATUS=OPS
| CORRWAIT 60
| CONSOLE
Example: Terminating a CORRWAIT
An important consideration in using CORRWAIT with non-NetView commands,
such as VTAM and MVS commands, is proper termination of the wait. Allowing a
timeout to occur can result in lost messages. Instead, explicitly end the CORRWAIT
with a following TOSTRING, TAKE FIRST, or GO command.
When the last expected message can be detected by a simple comparison or count,
use TOSTRING or TAKE FIRST after the CORRWAIT stage. When more
complicated conditions apply, use the GO command.
In this example, we expect two VTAM ACTIVE messages. We terminate
immediately on receipt of IST061I VARY ACT...FAILED message, but if good
responses are received, we must count them.
Note: Certain VTAM message IDs are release dependent.
PIPE VTAM V NET,ACT,SCOPE=ALL,ID=NTFELN7E
| CORRWAIT 100
| TOSTRING 1.7 /IST061I/
| SAFE VTAMRESP
| LOCATE 1.7 /IST093I/
| DROP 1
| PIPEND 0
PIPE CORRWAIT
The desired termination condition is stop as soon as you receive IST061 (failure
message) or when you receive the second IST093. Notice that the first VTAM
ACTIVE message is dropped after being stored in a name SAFE for later
examination. The second VTAM ACTIVE message that is received drives PIPEEND
0, which causes the pipeline to end with a0return code.
Still more complex termination decisions can require you to drive a command
procedure from a NETVIEW stage following your CORRWAIT. This procedure can
Chapter 2. Pipeline Stages and Syntax 57