Master-capable and Basic NetView Programs

Other NetView® programs in the sysplex that are members of the same DSIPLXnn group can be defined as backups for the master NetView program and are known as master-capable. If the master NetView program is unavailable, one of the master-capable NetView programs can take over the role of master, depending on the rank defined for each master-capable program.

The master and master-capable NetView programs are defined by using the XCF.RANK statement in the CNMSTUSR or CxxSTGEN member. For a high degree of control, these statements must be coordinated throughout the sysplex. Other statements in the CNMSTUSR or CxxSTGEN member can be used to define, for example, a list of procedures that is associated with the master NetView program or the time that a master-capable NetView program must wait before taking on the master role if no master program is detected at initialization. For information about changing CNMSTYLE statements, see IBM® Tivoli NetView for z/OS Installation: Getting Started. For information about the statements, see the IBM Tivoli NetView for z/OS Administration Reference.

NetView programs that are neither master nor master-capable are known as basic NetView programs. Basic NetView programs forward status to the master NetView program but cannot assume the role of master.

Figure 1 shows an example configuration consisting of a sysplex with three systems, each running a single NetView program. NVA is the master NetView program, with NVB (a master-capable NetView program) and NVC (a basic NetView program) forwarding data to NVA. The master NetView program provides data to the NetView management console and the Tivoli® Enterprise Portal and stores data in RODM. The NetView for z/OS® Enterprise Management Agent connects to a z/OS Tivoli Enterprise Management Server on the same LPAR. All three NetView programs belong to the same XCF group and use z/OS XCF support.
Figure 1. Sysplex Configuration
This figure shows a sysplex configuration.