Possible configurations using runtime environments

Edit online

The following five examples show different types of runtime environment configurations. The way you choose to set up your runtime environments depends on your site requirements and maintenance procedures.

Tip: The data set name (DSN) is composed of the high-level qualifier (&hilev), followed by the mid-level qualifier (&rte), followed by the low-level qualifier. The field settings and library names shown are for illustrative purposes only.
Example 1. Full (self-contained) runtime environment: The full runtime environment contains all libraries required by a particular IBM product and is the easiest runtime environment to create. This type of runtime environment can be defined in any situation but is most suitable if at least one of the following statements is true:
  • Your installation comprises only a single z/OS image.
  • You want each z/OS image to be independent.
  • You are creating a runtime environment for a specific combination of monitoring agents that do not exist in any other runtime environment.
The following example represents a full runtime environment called RTE1 that is completely self-contained. All base libraries and LPAR-specific libraries are allocated within RTE1. The base libraries in a full runtime environment are a copy of the SMP/E installation libraries. 
RTE Name: RTE1
Type: FULL Hilev: IBM.OMXE
Midlev: RTE1
Shares with: (none)
LPAR-specific library DD DSNAME resolution: 
//RKANPARU DD DSN=IBM.OMXE.RTE1.RKANPAR
           DD DSN=IBM.OMXE.RTE1.RKANPARU
Base library DD DSNAME resolution: 
//RKANMODL DD DSN=IBM.OMXE.RTE1.RKANMODL
This type of runtime environment is illustrated in Figure 2.

Figure 2. Full runtime environment on a single system

The following figure shows the way a full runtime environment can be expanded to more than one z/OS image. Each runtime environment is self-contained; the three runtime environments X, Y, and Z on systems A, B, and C do not share any libraries.

Figure 3. Full runtime environments on several systems

Example 2. Base runtime environment: The base runtime environment allocates shareable base libraries only. A base runtime environment must be used in conjunction with a sharing-with-base runtime environment (see “Example 3. Sharing-with-base runtime environment”) to provide the complete set of libraries required to run the installed monitoring agents. The base runtime environment and the sharing-with-base runtime environment must be defined for the same combination of monitoring agents.

A base runtime environment is typically used when storage devices are shared or when monitoring agent product maintenance synchronization across systems is desired. Sharing base libraries avoids unnecessary duplication, saves disk space, and simplifies the application of monitoring agent maintenance to a common point.

The following example represents a base runtime environment called RTE2. 
RTE Name: RTE2
Type: BASE Hilev: IBM.OMXE
Midlev: (none) Shares with: (none)
Shares with: (none)
LPAR-specific library DD DSNAME resolution:

*There are no LPAR-specific libraries in a BASE RTE.

Base library DD DSNAME resolution: 
//RKANMODL DD DSN=IBM.OMXE.RKANMODL

This type of runtime environment is illustrated in the following figure.

Figure 4. Base runtime environment

Example 3. Sharing-with-base runtime environment: The sharing-with-base configuration is a good choice for environments where storage devices are shared. Using the base runtime environment for common data sets, the sharing-with-base runtime environment contains only LPAR-specific libraries. The base runtime environment cannot contain the LPAR-specific libraries required to run the installed monitoring agents. The base runtime environment and the sharing-with-base runtime environment must be defined for the same combination of monitoring agents.

The Configuration Tool resolves product configuration elements to point at the LPAR-specific libraries and the base runtime environment libraries as necessary.

The following example represents a sharing-with-base runtime environment called RTE3, which obtains its base library information from the base runtime environment (RTE2). 
RTE Name: RTE3
Type: SHARING
Hilev: IBM.OMXE
Midlev: RTE3
Shares with: BASE RTE2
LPAR-specific library DD DSNAME resolution: 
//RKANPARU DD DSN=IBM.OMXE.RTE1.RKANPAR 
           DD DSN=IBM.OMXE.RTE1.RKANPARU
Base library DD DSNAME resolution: 
//RKANMODL DD DSN=IBM.OMXE.RKANMODL

This type of runtime environment is illustrated in the following figure.

Figure 5. Sharing-with-base runtime environment

Example 4. Sharing-with-full runtime environment: The sharing-with-full runtime environment allocates LPAR-specific libraries only, and in this example, obtains its base library information from a full runtime environment that contains the same combination of monitoring agents.

This configuration can also be used for environments where storage devices are shared, although the base/sharing pair is the preferred approach.

The following example represents a sharing-with-full runtime environment called RTE4, which obtains its base library information from the full runtime environment (RTE1). 
RTE Name: RTE4
Type: SHARING
Hilev: IBM.OMXE
Midlev: RTE4
Shares with: FULL RTE1
LPAR-specific library DD DSNAME resolution: 
//RKANPARU DD DSN=IBM.OMXE.RTE1.RKANPAR
           DD DSN=IBM.OMXE.RTE1.RKANPARU
Base library DD DSNAME resolution: 
//RKANMODL DD DSN=IBM.OMXE.RTE1.RKANMODL
This type of runtime environment is illustrated in the following figure.

Figure 6. Sharing-with-full runtime environment

Example 5. Sharing-with-SMP/E runtime environment: The sharing-with-SMP/E runtime environment allocates LPAR-specific libraries only and obtains its base library information from target libraries managed by SMP/E. Note that the target SMP/E libraries must be copies (cloned) rather than the system libraries. See the appendix on making a copy of your system software (cloning) in z/OS and z/OS.e Planning for Installation.
Use the sharing-with-SMP/E configuration if at least one of the following statements is true:
  • Space is limited on storage devices. This configuration method does not allocate base libraries in the runtime environment, thereby reducing storage requirements.
  • You want to activate SMP/E applied monitoring agent product maintenance immediately.
The following example represents a sharing-with-SMP/E runtime environment called RTE5, which obtains its base library information from SMP/E target libraries. 
RTE Name: RTE5
Type: SHARING Hilev: IBM.OMXE
Midlev: RTE5
Shares with: SMP/E Target Libraries
Hilev (SMP): INSTALL.SMPE
LPAR-specific library DD DSNAME resolution: 
//RKANPARU DD DSN=IBM.OMXE.RTE1.RKANPAR 
           DD DSN=IBM.OMXE.RTE1.RKANPARU
Base library DD DSNAME resolution: 
//RKANMODL DD DSN=IBM.OMXE.SMPE.TKANMODL
The sharing-with-SMP/E type of runtime environment is illustrated in the following figure.

Figure 7. Sharing-with-SMP/E runtime environment