If you installed the Tivoli Tape Optimizer Monitoring Agent software onto a z/OS image that contains 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 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 4. Build the runtime libraries and continue from there.
To define the runtime environment for the Tivoli Tape Optimizer monitoring agent, complete the following procedure:
Procedure
On the Configure Products menu of the Configuration Tool, 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.1
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 TOCSHAR1 SHARING TOBASE1 Sharing RTE for TO environment
-------------------------------------------------------------------------------
TOCBASE1 BASE Base RTE for the TO 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. This setup makes it easy to associate the jobs in INSTJOBS with the runtime environment.
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 environment.
(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. This panel shows 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, to make the output of your Configuration Tool batch jobs easier to find in the SDSF queue.
You can change the started task (STC) prefix to avoid confusion with others at your site.
Type N for Will this RTE have a Tivoli Enterprise Monitoring Server (because Tivoli Enterprise Monitoring Server is installed on a different system).
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 CMS
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 ==> N (Y, N)
If Y, TEMS name ==> (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
Leave NONE as the value of the Security system field. Because this runtime environment does not include a Tivoli Enterprise Monitoring Server, security validation for users signing on to the Tivoli Enterprise Portal is handled by the hub monitoring server on Windows.
If you intend to use the SNA communication protocol, supply the name of your network ID in the VTAM section.
Important: If you do not intend to use SNA, clear the system defaults displayed in the VTAM section. Otherwise, you will be required to define SNA as one of your communication protocols during Step 5. Configure the monitoring agent.
For TCP/IP communications between the monitoring agent and the Tivoli Enterprise Monitoring Server, 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 on 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 (Figure 14 on page 62).
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 Tape Optimizer. Go on to Step 4. Build the runtime libraries.