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 TSO<br />

tso_command<br />

A TSO line mode command to be invoked at the TSO server. Tso_command is<br />

required when TSO has no input stream and is otherwise optional.<br />

If tso_command is specified, the command is invoked once if the TSO stage has<br />

an input stream. Otherwise, the command is invoked when an input message<br />

is passed to the TSO stage.<br />

If tso_command is not specified, the commands to be invoked are read from the<br />

input stream.<br />

Usage Notes<br />

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

Note: Long running commands, such as IPTRACE, and commands requiring a<br />

dialog, such as ACCOUNT, are not supported.<br />

v Command responses are delayed until command completion. For example, a<br />

TSO command that issued a message every 2 seconds and runs <strong>for</strong> 10 seconds<br />

delays 10 seconds be<strong>for</strong>e issuing 5 messages together.<br />

v Command execution is single threaded <strong>for</strong> each server.<br />

v Commands requiring a dialog are not supported. However, data <strong>for</strong> a dialog can<br />

be assembled into a multiline message. This multiline message can be used to<br />

drive a TSO REXX procedure managing the dialog within TSO.<br />

v Command authority is checked prior to and after submitting the command.<br />

Prior to submission authority is checked <strong>for</strong> the pipe stage and <strong>for</strong> the verb of<br />

the TSO command. The verb of the TSO command is the first blank delimited<br />

token. To permit only B<strong>OS</strong>S to use the TSO stage, code the following statements:<br />

PROTECT *.*.DSIPITSO<br />

PERMIT B<strong>OS</strong>S *.*.DSIPITSO<br />

The verb of the TSO command is treated as the value of the PROTECT keyword<br />

VERB <strong>for</strong> authority checking purposes. For example, if you want to prevent<br />

operators from issuing a PIPE TSO IPTRACE command, code the following<br />

statements:<br />

PROTECT *.*.DSIPITSO.VERB.IPTRACE<br />

The specified server is treated as the value of the PROTECT keyword TS<strong>OS</strong>ERV<br />

<strong>for</strong> authority checking purposes. For example, to prevent operators from using<br />

server USER1 in combination with the started job SERVJOB1, code the following<br />

statements:<br />

PROTECT *.*.DSIPITSO.TS<strong>OS</strong>ERV.USER1/SERVJOB1<br />

See the START command in the <strong>NetView</strong> online help <strong>for</strong> additional in<strong>for</strong>mation<br />

on started jobs.<br />

Note: The TSO stage cannot resolve TSO synonyms. All command synonyms<br />

must be protected.<br />

TSO per<strong>for</strong>ms command authority checking using the same rules that apply<br />

when the TSO user name is directly logged-on.<br />

Return Codes<br />

A secondary output stream can be connected to receive command response codes.<br />

Each code begins with a 10-digit, 0-padded, signed number. Nonzero codes<br />

indicate an error and are followed by a space and keyword indicating the source of<br />

the error such as +0000000100 PPI.<br />

The keyword can be one of the following keywords:

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

Saved successfully!

Ooh no, something went wrong!