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

* HALERT: Retrieve Alert History */
’ATTACH NPDA’ /* Output, including messages will be */ ▌1▐
/* saved for future VET call */
’PIPE (NAME AHIST1 END +)’, /* Start a pipe */ ▌2▐
’| VET NEXT ROWS’, /* give update when it arrives, as image*/
’| CORRWAIT MOE 60’, /* Wait 60 sec for first NPDA screen */
’| NLOCATE 1.7 /BNH150I/’, /* I KNOW what first screen looks like */ ▌3▐
’| CONSOLE’, /* show badness */
’| A: LOCATE 1.7 /DWO369I/’, /* Separate time-out message (MOE) */ ▌4▐
’| VAR timeout’, /* save time-out message */
’+ A:’, /* other message? */ ▌5▐
’| VAR npdamsg’ /* ...save first for test */
If symbol(’timeout’) = ’VAR’ THEN /* time out? */
Signal TIMEOUT /* handle unexpected error */
If symbol(’npdamsg’) = ’VAR’ THEN /* some NPDA error */
Exit 20 /* messages from NPDA already shown */
/*----------------- Down to business -----------------------*/
/* Type a ’ALH’ (Alerts History) in the command area and push enter. */
’VET /ALH/’ /* Sending the ’ALH’ and an enter key. */ ▌6▐
Do UNTIL(thispage = lastpage | RC¬=0) ▌7▐
’PIPE (NAME AHISTLP END =)’, /* start a big pipe */
’| VET NEXT ROWS’, /* give update when it arrives, as image*/
’| CORRWAIT MOE 60’, /* Wait 60 sec for rnd trip to DST... */
’| SC: LOCATE 1.7 /BNH150I/’,/* expected screen with data.. */ ▌8▐
’| SEPARATE’, /* handle lines individually... */
’| PG: DROP 4’, /* drop header area... */
’| DROP LAST 1’, /* command line */
’| MSG: DROP LAST 4’, /* message area, hopefully blank */
’| STRIP TRAILING’, /* shorten line ending in blank, so we */
’| LOCATE 1 //’, /* can toss out blank lines */
’| CONSOLE’, /* Report data out to user */
’| TAKE 1’, /* AND use ONE new data line to trigger */ ▌9▐
’| NETV VET /FORWARD/’, /* ...new data, then go to next screen */ ▌10▐
’= MSG:’, /* Immed message area from NPDA */
’| LOCATE 2.3 /BNJ/’, /* any error message in immed area */
’| CONSOLE’, /* REPORT it, too. */
’| VAR npdamsg’, /* save for test */
’= SC:’, /* message instead ?? This is bad. */
’| A: LOCATE 1.7 /DWO369/’, /* Separate time-out message (MOE) */
’| VAR timeout’, /* save time-out message */
’= A:’, /* other message ? ?? This is bad. */
’| CONSOLE’, /* show badness */
’| VAR npdamsg’, /* ...save first for test */
’= PG:’, /* get header area */
’| DROP 2’, /* drop BNH150 and NPDA head-date line */
’| VAR pagedata’ /* ...save pagedata for test */
If symbol(’timeout’) = ’VAR’ THEN /* time out? is possible? */
Signal TIMEOUT /* handle unexpected error */
Parse var pagedata . ’PAGE’ thispage . lastpage /* parse out page nos. */
End /* */
EXIT 0 /* And do automatic DETACH for NPDA’s VOST */
Figure 24. Sample Full-Screen Automation Program — Capture Alert History
Full-Screen Automation
Within this example there are a number of important things to note:
▌1▐ The ATTACH command creates a VOST and starts NPDA for automation.
Full-screen applications can be automated only if started with ATTACH.
▌2▐ The PIPE AHIST1 waits for a response from NPDA using VET NEXT and
CORRWAIT. This pipeline ends normally when NPDA is ready to receive
input.
▌3▐ If BNH150I is returned, the NPDA main menu was successfully displayed,
Chapter 5. Full-Screen Automation 331