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.

PIPE VET<br />

Note: For any field of data that has an intensity attribute of DARK (ID), the<br />

entire returned field in<strong>for</strong>mation has presentation attribute of DARK. As<br />

a result, the data cannot be displayed. One way to see the data is to use<br />

a COLOR NORMAL stage subsequent to the VET stage.<br />

NAME<br />

Specifies the name of the V<strong>OS</strong>T. NAME must correspond to the NAME on the<br />

ATTACH command that created the V<strong>OS</strong>T or attach name. VET NAME<br />

indicates that the VET stage is to interact with the named V<strong>OS</strong>T.<br />

If a V<strong>OS</strong>T was created by the ATTACH command without a NAME, the V<strong>OS</strong>T<br />

is dependent on the invoking procedure. In the case of a dependent ATTACH,<br />

if you code VET without specifying a NAME, VET interacts with only one<br />

V<strong>OS</strong>T: the V<strong>OS</strong>T created by the ATTACH command within the same procedure<br />

as the VET stage. NAME must be specified if VET is to interact with an<br />

independent V<strong>OS</strong>T, that is, a V<strong>OS</strong>T created outside of the procedure family.<br />

NAME must be specified if VET is to interact with an independent V<strong>OS</strong>T, that<br />

is, a V<strong>OS</strong>T created outside of the procedure family.<br />

NEXT<br />

Specifies that the next update to the virtual screen is to be returned to the<br />

stage. This update can either be currently pending or can be received at a<br />

future point in time when the application next updates the virtual screen.<br />

Specify CORRWAIT as the next stage after VET NEXT. CORRWAIT<br />

automatically ends when:<br />

v The application running on the V<strong>OS</strong>T is ready <strong>for</strong> input.<br />

v The application terminates.<br />

For additional in<strong>for</strong>mation on CORRWAIT, see “PIPE CORRWAIT ” on page<br />

54.<br />

In general, VET NEXT does not return a complete screen image. Only the parts<br />

of the virtual screen sent by the application as the screen updates are returned.<br />

Depending on the application, all or part of the virtual screen can be updated.<br />

ROWS<br />

Specifies that the data displayed on the virtual screen is to be returned to the<br />

stage as a series of 24 lines of 80 characters each following the BNH150I<br />

message header. Positions on the virtual screen occupied by start field orders<br />

are blank (X'40'). When using VET NEXT ROWS, those screen positions not<br />

updated by the application running on the V<strong>OS</strong>T contain X'FF' characters.<br />

Note: For any row of data that contains any field with an attribute of DARK,<br />

the returned row has a presentation attribute of DARK. As a result, the<br />

data is not displayed. One way to see the data is to use a COLOR<br />

NORMAL stage subsequent to the VET stage.<br />

For additional in<strong>for</strong>mation about start field orders, refer to the 3270<br />

In<strong>for</strong>mation Display System library.<br />

ROW.COL<br />

Specifies the starting row and column on the virtual screen where the data<br />

specified by the input stream or /string/ is to be written. If ROW is specified<br />

without COL, the default value of 1 is used <strong>for</strong> COL.<br />

If ROW.COL is not specified, VET writes the data specified in the input stream<br />

/string/ beginning at the current cursor position on the V<strong>OS</strong>T virtual screen. If<br />

the current cursor position is in a protected field, VET simulates a tab to the<br />

next unprotected field and writes the data beginning in that unprotected field.<br />

Chapter 2. Pipeline Stages and Syntax 263

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

Saved successfully!

Ooh no, something went wrong!