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

Usage Notes<br />

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

A null string (//) is handled as a tab to the next unprotected field. By using<br />

null strings you can tab through the unprotected fields on the virtual screen,<br />

filling in data as you proceed. If you specify more tabs than unprotected fields<br />

on the virtual screen, you can return to the first unprotected field on the screen<br />

and continue with your data input.<br />

All pending application I/O requests are applied to the virtual screen be<strong>for</strong>e<br />

writing the /string/ to the virtual screen.<br />

/string/<br />

Specifies the data to be written to the virtual screen.<br />

/string/ is only valid when VET is used as a command.<br />

Data that is too long <strong>for</strong> the unprotected field is truncated. When the data is<br />

truncated, no error condition or warning is returned to the stage.<br />

Data that is shorter than the unprotected field is padded on the right with<br />

blanks.<br />

The first nonblank character encountered after the stage name or row.col is the<br />

delimiter, which establishes the boundary of the text string used by the stage.<br />

The delimited string ends when the same character is encountered a second<br />

time.<br />

Multiple unprotected fields on the virtual screen can be filled by including null<br />

values <strong>for</strong> /string/. A null value is indicated by coding two delimiters<br />

consecutively, <strong>for</strong> example:<br />

//<br />

A null string causes nothing to be written to the unprotected field, but the<br />

cursor tabs to the next field on the virtual screen. In this way you can input<br />

data to some fields and skip other fields. If you specify more tabs than<br />

unprotected fields on the virtual screen, the cursor tabs back to the first<br />

unprotected field on the screen and continues with your data input.<br />

v While the application is still locked from accepting input, VET enables you to<br />

queue input <strong>for</strong> the application. Queued input assumes that the application<br />

accepts your input without any intervening errors. You can queue as much input<br />

as necessary, but the chance <strong>for</strong> error increases dramatically with each queued<br />

input request. If the application ends be<strong>for</strong>e all queued input has been passed to<br />

the application, the remaining queued input is discarded without generating an<br />

error or warning.<br />

v If PIPE VET NEXT is issued while queued inputs are pending, the results of<br />

PIPE VET NEXT are not returned to the stage until all pending queued inputs<br />

have been passed to the application and inputs have been processed by the<br />

application and the results displayed on the V<strong>OS</strong>T virtual screen.<br />

v A null string (//) does not need to be specified on VET. If you want to send a<br />

PF3 action key to the application running on the V<strong>OS</strong>T without altering any<br />

fields on the virtual screen, you can specify the following statement:<br />

VET PF3<br />

v If VET has both an input stream and a /string/ specified, the /string/ is written to<br />

the panel first, followed by data from the input stream.<br />

v PF and PA keys cannot be specified <strong>for</strong> action key if the application running on<br />

the V<strong>OS</strong>T allows user-defined PF keys. The BNH150I application field contains<br />

the application name if the application enables the user to define PF keys. If<br />

BNH150I contains a value in the application field, the <strong>NetView</strong> program rejects

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

Saved successfully!

Ooh no, something went wrong!