IBM Tivoli NetView for z/OS Programming: Pipes - IBM notice

Full-Screen Automation
Handling Returned Messages
324 Programming: Pipes
In this case, a stem variable is created with five values. The first four are null. A
null value passed to VET places nothing in an unprotected field, and the cursor
skips to the next field. In the previous example, VET begins in column 1 row 1,
skips the first four unprotected fields (*1*, *2*, *3*, and *4*), and places an X in the
fifth unprotected field (.....1 NCP/CA/LAN/PL). When the entire stem is written
to the panel, the Enter key is pressed.
Hint: Consider the following items when coding your full-screen automation
program:
v The /string/ coded on a VET command can be a pipeline specification.
v Before detaching a VOST, you might want to code NETVIEW VET /LOGOFF/,
or the appropriate logoff, or termination command for the application running
on the VOST.
v A VET first stage returns a blank screen if a logoff or termination command was
executed for the application on the VOST.
The processing of message BNH150I is key to full-screen automation. All
full-screen data returned by a VET first stage is formatted in this multiline
message.
The first line of the multiline message is:
BNH150I format/action OUTPUT FOR 'application' RECEIVED FROM attachname
The following message variables, which are contained in this BNH150I message
header line, indicate the options specified on the VET stage, the VOST name, and
the application name:
format Specifies whether the VET first stage requested the full-screen data to be
returned in ROW or FIELDS format.
action Specifies whether the VET first stage requested a CURRENT or NEXT view
of the virtual screen.
application
Indicates whether the application running on the VOST is enabled for
dynamic remapping of PF and PA keys using the NCCF SET command. If
it does, an application name is included in this message variable. If the
application is null (''), the application running on the VOST does not allow
remapping of PF and PA keys, so PF and PA keys can be used as action
keys on VET subsequent stages.
In most cases, application is null or the same as the command name.
However, application can be different from the ATTACH command in the
following situations:
v ATTACH commands that are CLISTs
v ATTACH commands that are synonyms for other commands
v ATTACH commands that attach non-IBM applications
attachname
Specifies the name of the VOST that has its data returned. This is either the
NAME specified on the ATTACH command when the VOST was created
or the default name when no NAME is specified on the ATTACH.
The lines following the BNH150I message header line depend on whether the
message results from VET ROWS or VET FIELDS.