SNA subarea and SNA APPN topology and status are dynamically discovered by the NetView program through the use of a VTAM V4R3 or higher agent. The topology and status information is stored in RODM and is dynamically updated as changes occur. The SNA subarea and SNA APPN networks are represented on NGMF workstation graphical views that change dynamically as the topology and status change. Storing the topology and status of SNA resources in RODM enables object-oriented automation and correlation.
NetView security capabilities were enhanced by providing a better ability to secure the product, reducing the number of NetView recycles needed for maintenance, and allowing security information to be stored in a security product such as IBM's RACF instead of in NetView-specific definition statements.
NetView command authorization can be located in a system authorization facility (SAF) product such as RACF, or in a NetView command authorization table. Both methods have advantages over the current "scope of commands" method of NetView command security including:
The ability to use wildcard characters when specifying the command, keyword, and/or value that is being protected and permitted.
The ability to audit command identifiers to be able to spot attempts to issue unauthorized command.
The ability to change and implement command security definitions without recycling the product.
NetView operator logon information can be stored in RACF (or other complying security product). This allows a customer using RACF for MVS and TSO user authorization to also use RACF for all NetView operator logon information(currently stored in the DSIOPF member and DSIPRF DD members).
Operator span of control definitions can be stored in RACF (or other complying security product).
Commands that are issued on one task but actually execute on a different task (for example, using the EXCMD command) can be security checked against the source issuer instead of the target issuer.
An exit is provided (including a shipped sample) that allows RUNCMD requests to a service point to be security checked.
The security options can be changed while NetView is active by using the REFRESH command. The current security option settings can be displayed using the LIST SECOPTS command.
A conversion tool (SECMIGR) is provided which converts current definitions to the new formats.
A central command (READSEC) is used to define authority for all member display commands (such as browse member and PIPE). This reduces the amount of definition work required to protect sensitive information stored in members.
New NGMF graphical views, called exception views, are introduced. Exception views are a graphical list of objects that are in an exception state (for example, only broken resources are shown). This is the default way to monitor SNA resources. Resources are automatically added to and deleted from views when the status of the resource changes. The same graphical operations can be done on exception views (for example, command support and more detail views). Different characteristics can be used when determining what resources should appear in an exception view. For example, an Automation-in-Progress operator status is provided which, when set, can be used to prevent operators from being notified of failures if automation is attempting a recovery.
Two of the RODM Toolkit PRPQ tools are incorporated into the NetView product: RODMView and RODMUNLD.
The ability to automatically cycle through views is added to NGMF.
NGMF workstation code has been converted to 32-bit, and fully tested with OS/2 Warp.
Alerts can be forwarded using LU 6.2. This allows alerts to be forwarded through intermediate focal points without conversion to messages, and allows non-NetView focal points to receive alerts from the NetView program. Using LU 6.2, you can also look at hardware monitor alert data across domains.
Session monitor supports the VTAM dependent LU server (DLUS) and dependent LU requestor (DLUR), border nodes, and virtual route transmission groups.
Customizable PF-keys are available from NetView host components (such as command facility, hardware monitor, session monitor, status monitor, log browse, member browse, and View applications). This allows you to use consistent PF-keys between NetView components, including, for example, setting PF12 to be a RETRIEVE key throughout the NetView program.
NGMF has 32 additional system statuses, and the NGMF color palette is externalized and expanded to 32 entries.
NetView's PIPE facility has been enhanced with eight new stages (QSAM, CHANGE, CHOP, NOT, CASEI, $VAR, $STEM, ENVDATA), and several additional commands which have been enhanced to produce correlated output.
There are several RODM enhancements:
A new RACF resource class called RODMMGR is supported for security (DATAMGR is still supported).
You can initialize RODM without using the active security product.
One API call can change multiple fields.
A new data type of INDEXLIST is supported, allowing an easier search of fields.
The NetView Browse function no longer requires the main status monitor facility task to be active.
The NetView main task has been reorganized into a main task and separate subtasks. This allows more selective recovery of the NetView program for certain types of failures.
NetView log and member browse and VIEW applications can use the full-screen dimensions instead of being limited to 24x80.
Automated logon to the NetView program is possible.
You can determine if a data set member exists or not before writing to it or reading from it using the NetView FNDMBR REXX function.