Defining complex network environments

The sample network used in the administration example has a simple configuration. Figure 1 shows a network with a more complex network configuration.

Figure 1. Example of a complex network configuration

This network consists of two domains, with the two host systems sharing a single NCP. Because of this arrangement, you must follow certain rules in defining the NCP and the attached resources. You define all other resources using the same procedures given in Modifying resource data for domain 1.

In this example, the NCP major node definition is the same in both domains. Each domain owns some of the resources attached to the NCP, and the remaining resources are shared between the two domains and therefore have no ownership defined. When you run the STATMON preprocessor for each domain using the current VTAMLST, STATMON generates an entry for each resource defined in the NCP. Because STATMON ignores any OWNER parameters defined in VTAMLST, the order that you load the STATMON data into IBM Z Performance and Capacity Analytics defines which system identifier is the owner of the resources.

Because of this, IBM Z Performance and Capacity Analytics ignores the STATMON data for the NCP resources in the second domain. IBM Z Performance and Capacity Analytics sets the resource owner to the first domain (since that data was loaded first), and the NCP major-node definitions in the second domain are the same as the definitions in the first domain. Figure 2 shows the definitions in the dialog work table after IBM Z Performance and Capacity Analytics loads the STATMON data, first for system SMF1, and then for system SMF2.

Figure 2. Definitions in work table for complex network

The ownership of resource Z is set to SMF1 instead of the SMF2 ownership defined in VTAMLST. Although this information does not match the actual network configuration, it does not create a problem in the . IBM Z Performance and Capacity Analytics uses only the resource name during collect and reporting, and uses the system identifier only during administration.

When you load STATMON data for networks that share an NCP, load the data first for the host system to be defined as the owner of resources attached to the NCP. If your installation uses NPM to record data, first load the STATMON data for the host system where NPM is located. Figure 3 shows an example of this configuration.

Figure 3. Example of a complex network using NPM

In this example, the resources are defined with the system identifier SMF1, which matches the system identifier that NPM uses to log the data to SMF.