28.11.2012 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PIPE CORRWAIT<br />

PIPE CORRWAIT<br />

Syntax<br />

Synonyms<br />

CORRWAIT:<br />

CORRWAIT<br />

MOE<br />

1<br />

interval<br />

*<br />

interval<br />

seqWait<br />

Stage Name Synonym<br />

CORRWAIT CORR, WAIT<br />

seqWait<br />

aftMlwait<br />

Command Description<br />

The CORRWAIT stage allows time to pass while asynchronous messages generated<br />

by the previous stage are returning to the pipeline. For every message processed<br />

by CORRWAIT, the timeout value is reset to allow up to n seconds between<br />

messages where n is determined by the interval parameters.<br />

Streams<br />

54 <strong>Programming</strong>: <strong>Pipes</strong><br />

Asynchronous or delayed messages are those which return to the <strong>NetView</strong><br />

program from commands running in another task (SWITCH, <strong>for</strong> example), or at<br />

another <strong>NetView</strong> system. When asynchronous responses are expected from any<br />

command issued in a pipe NETVIEW or VTAM stage, the next stage must be<br />

CORRWAIT. Otherwise, the stages in between do not see the asynchronous<br />

messages, and results are unpredictable.<br />

The CORRWAIT stage can be used as a first stage (to provide a definite waiting<br />

period) or following a stage generating asynchronous messages.<br />

Stream Type Number Supported<br />

Input 1<br />

Output 2<br />

Termination Conditions<br />

CORRWAIT normally terminates when the preceding stage completes. For<br />

example, if you enter:<br />

PIPE NETV RMTCMD LU=CNM02,LIST XXX|CORRWAIT 60|STEM RMTDATA.<br />

RMTCMD completes its local processing in less than a second, but processing of<br />

the stage continues, first at a DST, next in the network, then at a remote <strong>NetView</strong>.<br />

LIST produces one or more messages, which CORRWAIT captures and writes to its<br />

primary output, STEM RMTDATA., and then CORRWAIT resets its timeout value.<br />

When the LIST stage completes, CORRWAIT is notified and the wait ends<br />

immediately. Functionally, it is as if the preceding stage did not complete

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!