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.

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

Displaying Return Codes<br />

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

PIPE (NAME SAMP)<br />

| (DEBUG) < MYFILE<br />

| (DEBUG) STRIP TRAILING / /<br />

| (DEBUG) JOINCONT TRAILING /$/<br />

| (DEBUG) CONSOLE<br />

For details on the output produced by DEBUG 1, see “DEBUG Stage Option” on<br />

page 348.<br />

Clogged Pipeline Details: When you receive message BNH155E indicating that a<br />

complex pipeline is clogged, it might be difficult to determine the cause of the<br />

clog. The DEBUG 2 pipeline option generates additional debugging in<strong>for</strong>mation<br />

when BNH155E is issued.<br />

For example, the following pipeline will clog:<br />

/* REXX Example */<br />

’PIPE (NAME CLOGGER END \ DEBUG 2)’,<br />

’|

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

Saved successfully!

Ooh no, something went wrong!