NetView and SA are More Integrated Than Ever
JeffWeiner 0600016PPM Comment (1) Visits (10512)
SA for z/OS is built on top of many base services provided by NetView for z/OS. But did you know that the two products also have a long history of collaboration and integration? Or that several integration points are new to the last couple releases? Let's explore these areas.
First, "data REXX" support gave NetView the opportunity to conditionally include SA initialization members without asking customers to manually include these members, as they previously had to do, saving time and eliminating potential errors. This has been done in several areas.
NetView and SA commands are defined in member CNMCMD. One of NetView's included files includes a member called INGCMD if SA is present, which integrates SA's command definitions with NetView's.
The same idea applies to definition of operator IDs (when not defined in a SAF product like RACF). NetView's DSIOPF member conditionally includes AOFOPF0.
The respective lists of clists allowed to bypass authorization are similarly integrated. NetView's DSIAUTB member conditionally includes AOFAUTB.
NetView has an INDEX function that lists its commands and other Help topics. When SA is present, it includes an entry for SA's high-level AOCHELP function.
NetView's "attended" logon profiles drive code, conditional on SA's presence, to obtain console IDs SA needs (via command AOCGETCN).
NetView's MAINMENU function (typically driven automatically through logon), conditionally includes a launch into SA operations when SA is present.
NetView's main configuration member is CNMSTYLE. Here "towers" are defined, among many other things. The SA tower is shipped commented out, and uncommenting it is the only configuration item we leave to the customer that's related to functions described here. Once this is done, SA's AOFSTYLE entries are included by CNMSTYLE, and SA initialization code is invoked during NetView initialization for the purpose of obtaining SA storage, control blocks, etc. This arrangement is new, although it's been PTF'd back to several NetView releases.
There is a new NVINFO command (recently PTF'd back to NetView v6.1) that gathers and logs a wide range of NetView information that's useful in diagnosis. This command has been updated to include SA information, again conditionally based on whether SA is present. See the online help or Command Reference for more on NVINFO - http
Finally, until recently SA installation was dependent on the customer correctly appending its REXX function packages to NetView's. This process is now automated through CNMSTYLE (see "REXX.FUNCPKGLIST" entries, also recently PTF'd back to NetView v6.1), again saving our customers time and errors.
In summary, the NetView and SA development teams continue to work together to integrate their respective installations, and make both products easier to use together.