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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Debugging <strong>NetView</strong> Pipelines<br />

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

Displaying Data Stream In<strong>for</strong>mation (DEBUG)<br />

The DEBUG option generates in<strong>for</strong>mation about the input and output data streams<br />

in a pipeline. DEBUG can be used either as a pipeline option, affecting the entire<br />

pipeline, or on individual stages.<br />

Attention:<br />

v DEBUG output is provided <strong>for</strong> pipeline problem determination only and is not<br />

intended as a programming interface. The <strong>for</strong>mat, type, and amount of<br />

in<strong>for</strong>mation provided by DEBUG is subject to future change.<br />

v DEBUG in<strong>for</strong>mation is available in English only.<br />

DEBUG Stage Option<br />

DEBUG on a stage generates in<strong>for</strong>mation about input and output streams<br />

connected to the stage and the messages flowing over those streams.<br />

Consider the following pipeline.<br />

/* REXX Example - Formats output from LIST STATUS=TASKS */<br />

address NETVASIS,<br />

’PIPE (NAME TASKLIST END -)’,<br />

’| NETV LIST STATUS=TASKS’, /* generate the data */<br />

’| DROP LAST 1’, /* no need of "END OF DATA" */<br />

’| COLOR GREEN’, /* standardize buffers */<br />

’| EDIT WORD 2 1’, /* re<strong>for</strong>mat data from the lines */<br />

’19.8 8’,<br />

’38.8 19’,<br />

’55.* 35’,<br />

’| LABS: COLLECT’, /* data and labels, labels read first */<br />

’| CONSOLE ONLY’, /* display results */<br />

, /* --- END of simple pipeline, begin new pipeline... */<br />

’- FAN: (DEBUG) FANIN’, /* feed data to "LABS", in order */<br />

’| LABS:’,<br />

, /* --- END of simple pipeline, begin new pipeline... */<br />

’- LIT !-------- Status of <strong>NetView</strong> Tasks ---------!’,<br />

’| COLOR YEL’, /* Control line becomes yellow */<br />

’| FAN:’, /* give line to "FAN" (primary input) */<br />

" LIT !Task Task’s Taskname or Current!",<br />

’| COLOR PINK’, /* First label line becomes pink */<br />

’| FAN:’, /* give line to "FAN" (2nd input) */<br />

"- LIT !type ID Resource Status!",<br />

’| COLOR PINK’, /* Second label line becomes pink. */<br />

’| FAN:’ /* give line to "FAN" (3rd input) */<br />

Note: For more in<strong>for</strong>mation, see “Example: Formatting LIST STATUS=TASKS<br />

Output” on page 42.<br />

DEBUG on the stage labeled FAN: generates in<strong>for</strong>mation about the data streams<br />

connected to FANIN and the messages flowing on those data streams. The<br />

following is an example of the type of problem determination in<strong>for</strong>mation<br />

produced.<br />

Connecting output number 1 of stage 7, "FANIN "<br />

to input number 2 of stage 5, "COLLECT ".<br />

Connecting output number 1 of stage 9, "COLOR YEL "<br />

to input number 1 of stage 7, "FANIN ".<br />

Connecting output number 1 of stage 11, "COLOR PINK "<br />

to input number 2 of stage 7, "FANIN ".<br />

Connecting output number 1 of stage 13, "COLOR PINK "<br />

to input number 3 of stage 7, "FANIN ".<br />

Stage 7 reads input from stream 1, "Status of NetVi".<br />

Stage 7 writes output to stream 1, "Status of NetVi".<br />

Stage 7 reads input from stream 2, "Task Task’s ".

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

Saved successfully!

Ooh no, something went wrong!