In this step you define the runtime environment for configuring the Tivoli Tape Optimizer Monitoring Agent software.
About this task
If you installed the Tivoli Tape Optimizer Monitoring Agent software onto a z/OS image that contains no Tivoli Enterprise Monitoring Server and no other monitoring agents, you must add the runtime environment and then build its libraries. This procedure is described immediately below.
If you installed the Tivoli Tape Optimizer Monitoring Agent software onto a z/OS image that already contains a Tivoli Enterprise Monitoring Server or another monitoring agent, and if you want to use an existing runtime environment (rather than creating a new one) for configuring the Tivoli Tape Optimizer Monitoring Agent, you do not need to add a runtime environment. Go directly to Step 2. Build the runtime libraries and continue from there.
To define the runtime environment for the Tivoli Tape Optimizer Monitoring Agent software, complete the following procedure:
Procedure
On the Configure Products menu, enter 2 (Select product to configure).
------------------------------ CONFIGURE PRODUCTS -----------------------------
OPTION ===>
Enter the number to select an option:
1 Set up configuration environment
2 Select product to configure
I Configuration information
S Services and utilities
F1=Help F3=Back
The Product Selection Menu is displayed, listing the products available for configuration.
Figure 2. Product Selection Menu: Configuration Tool
---------------------------- PRODUCT SELECTION MENU ---------------------------
COMMAND ===>
Actions: S Select product
__ Tivoli Tape Optimizer Monitoring Agent V2.2
__ IBM Tivoli Monitoring Services on z/OS V6.2.0
F1=Help F3=Back F5=Refresh F7=Up F8=Down
Type S to the left of Tivoli Tape Optimizer Monitoring Agent V2.2 and press Enter.
The Runtime Environments (RTEs) panel is displayed. This panel lists all the runtime environments defined to the Configuration Tool, along with the actions you can perform to create and manage runtime environments.
Figure 3. Runtime Environments (RTEs) panel: Configuration Tool
------------------------- RUNTIME ENVIRONMENTS (RTEs) -------------------------
COMMAND ===>
Actions: A Add RTE, B Build libraries, C Configure,
L Load all product libraries after SMP/E,
D Delete, U Update, V View values, Z Utilities
Action Name Type Sharing Description
A SHAR1 SHARING BASE1 Sharing RTE for the Tivoli environment
-------------------------------------------------------------------------------
BASE1 BASE Base RTE for the Tivoli environment
-------------------------------------------------------------------------------
Enter=Next F1=Help F3=Back F7=Up F8=Down
On the Runtime Environments (RTEs) panel, type A (Add RTE) in the Action field beside the first (empty) row and type a Name for your new runtime environment.
The runtime environment name is a unique identifier of up to 8 characters. It is automatically used as the mid-level qualifier for full and sharing runtime environments. You can optionally specify a mid-level qualifier for base runtime environments.
Tip:
If you specify a runtime environment name no more than 4 characters long, you can specify the same name for the JCL suffix (used as the suffix of the name of the member containing the JCL in the INSTJOBS dataset). This setup makes it easy to associate the jobs in INSTJOBS with the runtime environment.
When you enter a C (Configure), B (Build), or L (Load) next to a runtime environment that has a previous version of the Tivoli Enterprise Monitoring Server installed, the Configuration Tool prompts you to confirm that you want to migrate to the newer version. A batch migration job completes the upgrade and retains all previously configured values for the Configuration Tool.
Specify the type of runtime environment being created. In this case, start by creating either a base or full type, which is essential if you intend to add sharing runtime environments later on.
Tip: A base runtime environment is not configurable. For information about the different types of runtime environments, see Understanding runtime environments.
(For sharing runtime environments only) Type the name of the base or full runtime environment from which this runtime environment obtains its base library information. If SMP/E target libraries are to be shared, type SMP.
Type a description for this runtime environment.
The description can be any information that is useful for you and others at your site.
When you have specified all required values on the Runtime Environments (RTEs) panel, press Enter.
The first of two Add Runtime Environment panels is displayed. These panels show the defaults for your system.
Specify a JCL suffix no more than 4 characters long, to be used as the suffix of the name of the member containing the JCL in the INSTJOBS dataset.
If possible, specify the runtime environment name as the JCL suffix. This setup makes it easy to associate the jobs in INSTJOBS with the runtime environment.
You can change the started task (STC) prefix to avoid confusion with others at your site.
Type Y for Will this RTE have a Tivoli Enterprise Monitoring Server.
Tip: Make a note of the TEMS name value displayed here. You will need to specify it later, when you configure the other components. A good place to record the TEMS name value is Configuration worksheet if the monitoring server is on a z/OS system. The TEMS name parameter is case-sensitive on all platforms.
For details of the parameters, press F1 (Help).
Figure 4. Add Runtime Environment (1 of 2) panel: Configuration Tool
----------------------- ADD RUNTIME ENVIRONMENT (1 of 2) ----------------------
COMMAND ===>
RTE: RTEname Type: SHARING Desc: RTE with TEMS
Libraries High-level Qualifier Volser Unit Storclas Mgmtclas PDSE
Non-VSAM hilev P2OMG1 3390 N
VSAM hilev P2OMG1
Mid-level qualifier ==> RTEname
JCL suffix ==> suffix
STC prefix ==> CANS
SYSOUT class ==> X Diagnostic SYSOUT class ==> X
Load optimization ==> N (Y, N)
Will this RTE have a Tivoli Enterprise Monitoring Server ==> Y (Y, N)
If Y, TEMS name ==> RTEname:CMS (Case sensitive)
Copy configuration values from RTE ==> (Optional)
Enter=Next F1=Help F3=Back
From the Add Runtime Environment (1 of 2) panel, press Enter. The Add Runtime Environment (2 of 2) panel is displayed.
----------------------- ADD RUNTIME ENVIRONMENT (2 of 2) ---------------------
COMMAND ===>
Use z/OS system variables? ==> N (Y, N)
RTE name specification ==> &SYSNAME
RTE base alias specification ==> n/a
Applid prefix specification ==> K&SYSCLONE
Use VTAM model applids? ==> N (Y, N)
Security system ==> NONE (RACF, ACF2, TSS, NAM, None)
ACF2 macro library ==>
If you require VTAM communications for this RTE, complete these values:
Applid prefix ==> CTD Network ID ==> Netid
Logmode table ==> KDSMTAB1 LU6.2 logmode ==> CANCTDCS
If you require TCP/IP communications for this RTE, complete these values:
*Hostname ==> * (See F1=Help for
*Address ==> HOMETEST instructions)
Started task ==> * (Recommended default = *)
Port number ==>
Enter=Next F1=Help F3=Back
You can leave NONE as the value of the Security system field or specify the security system of your choice. Specifying a security system here indicates the system to be used for security validation of users signing on to the Tivoli Enterprise Portal, but it does not enable the validation. Security validation of users is enabled in a Tivoli Enterprise Monitoring Server configuration panel (see Specifying configuration values). For more information about product security, see Chapter 7, Setting up security.
Supply the name of your network ID in the VTAM section.
For TCP/IP communications between the Tivoli Enterprise Monitoring Server and the other product components, supply the following information:
Hostname
The TCP/IP host name of the z/OS system where the runtime environment is being defined. To obtain the host name, enter TSO HOMETEST at the command line.
If the z/OS domain name resolver configuration specifies a search path that includes the target domain suffix, specify only the first qualifier of the host name. (Example: sys is the first qualifier of the fully qualified host name sys.ibm.com.) Otherwise, specify the fully qualified host name.
Address
The IP address of the z/OS system. To obtain the IP address, enter TSO HOMETEST at the command line.
Started task
The started task name of the TCP/IP server. The default value of * (asterisk) allows the IP stack to find the TCP/IP image dynamically, if it is available.
Port number
The address of the IP port. The default is 1918.
When you have finished defining your runtime environment, press Enter to return to the Runtime Environments (RTEs) panel (See figure: Runtime Environments (RTEs) panel: Configuration Tool in the second step of Step 1. Define the runtime environment).
Tip: Select View Values (V) to verify the runtime environment information and Update (U) to make the necessary changes.
Results
This completes the addition of your runtime environment. You must build the runtime libraries before continuing to configure Tivoli Tape Optimizer Monitoring Agent. Go on to Step 2. Build the runtime libraries.