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

+ NTV7E DSI#0003 BNJ924I CANNOT SEND TO SPECIFIED DOMAIN
’ NTV7E TOM
BNH150I ROWS/NEXT OUTPUT FOR ’NPDA’ RECEIVED FROM NPDA.
NETVIEW SESSION DOMAIN: NTV7E DSI#0003 11/16/10 18:33:16
NPDA-01A * MENU * HOST DOMAIN: NTV7E
SEL# PRODUCES:
( 1) ALERTS-DYNAMIC DISPLAY
( 2) TOTAL EVENTS DISPLAY
( 3) TOTAL STATISTICAL DATA DISPLAY
( 4) HELP MENU DISPLAY
REQUEST DATA FROM NETWORK RESOURCES:
( 5) SNA CONTROLLERS (CTRL)
DATA TYPES INITIALIZED/PURGED
AL.. (11/16/10) EV.. (11/16/10) ST.. (11/16/10) GMFALERT.. Not Present
ENTER SEL#
BNJ926I SD/SDOMAIN COMMAND FAILED. SESSION DOMAIN IS UNCHANGED
???
CMD==>
Figure 21. Message and Full-Screen Returned to VET
Partial Screens
Full-screen automation programs can require considerable knowledge of the
screen-handling techniques used by the applications running on the VOST. This is
especially true if the applications write partial screens of data to the virtual screen.
To a human operator these partial screens might not be detectable, but an
application handling data at computing speeds must be tolerant of partial screen
updates.
There are also special considerations for applications running on a VOST running
the Terminal Access Facility (TAF). TAF sessions are started using BGNSESS
FLSCN.
Sample CNMS1098 demonstrates techniques you can use to avoid problems with
applications running in the TAF environment and those providing partial screen
updates. This sample uses TAF to log on to a TSO ID, collect data from the Spool
Display and Search Facility (SDSF) active display, and log off.
Debugging Full-Screen Automation Programs
Full-Screen Automation
You can use the DUMP keyword to create a display of all data sent to and from
the VOST. This data might be useful in problem determination.
Figure 22 on page 330 shows a partial dump from ATTACH DUMP NPDA:
Chapter 5. Full-Screen Automation 329