Configuration Tool (ICAT) method
Step 1. Add a runtime environment
5. On the Runtime Environments (RTEs) panel, type A (Add RTE) in the Action field beside the first empty row, and type a name for the runtime environment in the Name field
The runtime environment name is a unique identifier of up to 8 characters. It is the default mid-level qualifier of the runtime libraries.
6. Specify the type of runtime environment being created. In this example, a Full runtime environment is created for the high-availability hub.
For more detailed information about the available types of runtime environments, see "What types of runtime environments to set up" in the "Planning your deployment" chapter of the IBM Tivoli
OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.
7. Type a description for this runtime environment. The description can be any information that is useful for you and others at your site.
8. When you have specified all required values on the Runtime Environments (RTEs) panel, press Enter.
The Add Runtime Environment (1 of 3) panel is displayed, as shown in Figure 7 on page 35.
KCIPRTE --- RUNTIME ENVIRONMENTS (RTEs) ---COMMAND ===>
*** Current product entry selected: ***
product_name Vn.n.n
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 R README Table of Contents
Action Name Type Sharing Description
A HAHUB FULL Runtime environment for high-availability hub
---Enter=Next F1=Help F3=Back F7=Up F8=Down Figure 6. Runtime Environments (RTEs) panel
The values on the Add Runtime Environment panels are used to allocate runtime libraries and provide configuration defaults.
9. Use the following information to complete the first Add Runtime Environment panel.
High-level qualifier
Specify the high-level qualifiers to be used for allocating the runtime libraries. These entries are required.
SMS considerations
If you plan to allocate SMS-managed data sets for the runtime environment, ensure that the following are all true:
v SMS is active on the z/OS image.
v The high-level qualifier that you specify is eligible for SMS-managed volumes.
v You specify a combination of VOLSER, UNIT, STORCLAS, and MGMTCLAS parameters that is valid at your site. Because SMS can be implemented in several different ways, the Configuration Tool does not attempt to validate these parameters.
The data set allocation jobs use the values you enter.
Volser Specify the volume serial numbers to be used for allocating the runtime data sets. This value is required if the runtime data sets are not managed by SMS.
Unit Specify the unit name to be used for allocating the non-VSAM runtime data sets. This value is required if the runtime data sets are not managed by SMS.
Storclas
If the runtime data sets are to be managed by SMS, specify the SMS storage class to be used for the allocation. If your site does not require the SMS STORCLAS parameter, you can leave this field blank.
Mgmtclas
If the runtime data sets are to be managed by SMS, specify the SMS management class to be used for the allocation. If your site does not require the SMS MGMTCLAS parameter, you can leave this field blank.
PDSE If the non-VSAM data sets are to be managed by SMS, you can specify Y to allocate PDSE
KCIPRTEA --- ADD RUNTIME ENVIRONMENT (1 of 3) ---COMMAND ===>
RTE: HAHUB Type: FULL Desc: Runtime environment for high-availability hub Libraries High-level Qualifier Volser Unit Storclas Mgmtclas PDSE
Non-VSAM rhilev volser unit N
VSAM rvhilev volser
Mid-level qualifier ==> HAHUB
JCL suffix ==> ssss Remote RTE for transport ==> N (Y, N) STC prefix ==> HAHB Runtime members analysis ==> Y (Y, N) 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 ==> HAHUB:CMS (Case sensitive)
Copy configuration values from RTE ==> (Optional)
Enter=Next F1=Help F3=Back
Figure 7. Add Runtime Environment (1 of 3) panel
data sets instead of PDS data sets. PDSE data sets do not require compression and are not limited by a predefined number of directory entries.
The default is N. Even if you specify Y, most load module libraries are not allocated as PDSE data sets. The main exception is a load library used for the SMP/E CALLLIBS facility.
Mid-level qualifier
Specify a mid-level qualifier for runtime libraries, or accept the default (the runtime environment name).
JCL suffix
Specify a unique JCL suffix, no more than 4 characters long, to identify the batch job members created in &shilev.INSTJOBS by the Configuration Tool for this runtime
environment. Check the INSTJOBS data set to ensure that the suffix is not already in use.
STC prefix
Specify a unique prefix to be used when generating started task procedures for this runtime environment. For the high-availability hub, do not accept the default value of CANS. Specify your own unique prefix.
SYSOUT class
Specify the value of the SYSOUT class for non-diagnostic output DDNAMEs, such as RKPDLOG, in generated JCL. This replaces the previously hardcoded SYSOUT class value.
Load optimization
Specify whether you want to optimize the loading of this runtime environment, when the runtime environment load action (L) is selected after maintenance is applied or products are reconfigured.
If you specify Y, the load job has the following characteristics:
v Copies only modified modules from target to runtime libraries.
v Requires access to IBM's SuperC (ISRSUPC) utility.
v Uses less DASD space.
v Performs additional analysis, which uses more CPU processing and file I/O.
If you specify N (the default), the load job has the following characteristics:
v Copies all members from target to runtime libraries, whether or not they were modified.
v Requires more DASD space.
v Uses less CPU time.
Tip: Even if you enable load optimization, the first load operation copies all members to the runtime data sets. Load optimization takes effect on the second and subsequent load
operations.
Remote RTE for transport
Accept the default value of N in this field.
Runtime members analysis
The Configuration Tool generates configuration batch jobs for the runtime environment and can identify user-modified data set members that each batch job will affect. If runtime members analysis is enabled, a report of user-modified members is displayed. You can also generate these reports from the RTE Utility Menu (action Z, option "Analyze user modified elements").
The default is Y.
Diagnostic SYSOUT class
Specify the value of the SYSOUT class for diagnostic output DDNAMEs, such as
SYSUDUMP and SYSABEND, in generated JCL. This replaces the previously hardcoded SYSOUT class value. The default is X.
Will this RTE have a Tivoli Enterprise Monitoring Server?
Specify Y (the default) to allocate libraries for the monitoring server.
Be sure to make a note of the TEMS name value displayed here. You will have to specify it later, when you configure the other components. The TEMS name parameter is
case-sensitive on all platforms.
Copy configuration values from RTE
Leave this field blank. Configuration values for the high-availability hub cannot be copied from another runtime environment.
10. After you have specified all required values on the first Add Runtime Environment panel, press Enter.
The second Add Runtime Environment panel is displayed, as shown in Figure 8.
The "Global SAF class name" in this panel provides security for the OMEGAMON enhanced 3270 user interface.
11. Use the following information to complete the second Add Runtime Environment panel.
Use z/OS system variables?
Leave the default of N in this field. A runtime environment for a high-availability hub cannot use system variables, because the hub is not defined to run on any specific system, and it retains the same parameter values on any system in the sysplex.
Security system
Specify what, if any, security system is to be used for this runtime environment. The default is NONE. If you specify a security system, verify that it is installed and configured correctly for your site. If you specify ACF2, you must also provide the name of the ACF2 macro library.
Tip: Specifying a security system here indicates which system will 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. For more information about configuring security, see Chapter 8,
“Configuring security on a monitoring server on z/OS,” on page 143.
Global SAF class name
Specify a common System Authorization Facility (SAF) security class name for OMEGAMON enhanced 3270 user interface security controls. The value is used in the
RTE_SECURITY_CLASS parameter in the KppENV member of the RKANPARU library. If this
KCIPRTA1 --- ADD RUNTIME ENVIRONMENT (2 of 3) ---COMMAND ===>
Use z/OS system variables? ==> N (Y, N) Use VTAM model applids? ==> N (Y, N) RTE name specification ==> &SYSNAME
RTE base alias specification ==> n/a Applid prefix specification ==> K&SYSCLONE.
Security system ==> NONE (RACF, ACF2, TSS, NAM, None) ACF2 macro library ==>
Fold password to upper case ==> Y (Y, N)
Global SAF class name ==> (ACF2 max is 3 chars.) VTAM values are required under certain conditions. Press F1=Help:
Applid prefix ==> CTD Network ID ==>
Logmode table ==> KDSMTAB1 LU6.2 logmode ==> CANCTDCS
If you require TCP/IP communications for this RTE, complete these values:
Hostname ==>
Started task ==> (Recommended default = *) Port number ==>
Enter=Next F1=Help F3=Back
Figure 8. Add Runtime Environment (2 of 3) panel
field is not specified, the RTE_SECURITY_CLASS parameter is generated as a placeholder comment in the RKANPARU(KppENV) member of components exploiting the parameter.
Specify a valid SAF class name if you want to specify a value. If you are using ACF2 as your external security resource manager, specify a maximum of three characters.
Fold password to upper case
By default, TMS:Engine folds logon passwords to uppercase. However, RACF V1.7 and higher supports mixed-case passwords. If you want to implement mixed-case passwords and if all your monitoring agents support them (this requires application of maintenance for each monitoring agent), set this field to N.
If any of your monitoring agents do not support mixed-case passwords, do not activate the SETROPTS PASSWORD(MIXEDCASE) option in RACF and do not enable mixed-case passwords in your runtime environments. Leave this field with the default value Y.
For more information about the MIXEDCASE option in RACF, refer to the z/OS Security Server RACF Security Administrator's Guide. For more information about the way
TMS:Engine handles security, enter README SEC at the command line of any Configuration Tool panel.
VTAM®communication values
The high-availability hub does not use VTAM for communication. Clear all the input fields in this section.
Applid prefix
Clear this field.
Network ID
Clear this field.
Logmode table Clear this field.
LU6.2 logmode Clear this field.
TCP/IP communication values
The values you specify here become the default TCP/IP values for the monitoring server.
Hostname
For the runtime environment of the high-availability hub, specify as the host name the application-instance-specific (private) DVIPA name you have defined to DNS. In the example shown, the host name is the private DVIPA name OMEGAHUB.
The host name for the runtime environment of the high-availability hub is a virtual system name, because the hub can run on any LPAR in the sysplex.
Started task
Identifies the TCP/IP stack to be used. If the LPAR contains a single TCP/IP stack, accept the default value of an asterisk (*), which uses the first TCP/IP stack that was started.
If the LPAR contains more than one TCP/IP stack, specify the started task name of the TCP/IP stack you want to use. Alternatively, you can specify the number sign (#), which is translated to a blank and allows the TCP/IP environment to choose the stack to use, either through TCP/IP definitions or through the use of the SYSTCPD DD statement.
Tip: Whichever method is used to select a TCP/IP stack in a multi-stack
environment, the Tivoli Management Services components continue to use that stack, even if a different stack becomes the primary stack. Therefore, in a multi-stack
environment, it is best to specify the started task name of the TCP/IP stack to be used, rather than specifying a wildcard or a blank.
If IP domain name resolution is not fully configured on the z/OS system, the SYSTCPD DD statement is required (see “(If applicable) Add support for the SYSTCPD DDNAME in the monitoring server started task” on page 119).
Port number
The number of the well-known port to be used for communications with the
high-availability hub. The default is 1918. (For detailed information about port number assignments, see the IBM Tivoli OMEGAMON XE and IBM Tivoli Management Services on z/OS: Common Planning and Configuration Guide.)
12. After you have specified all required values on the second Add Runtime Environment panel, press Enter.
A third Add Runtime Environment panel is displayed, as shown in Figure 9.
13. Leave the third Add Runtime Environment panel blank. This panel does not apply to the runtime environment of the high-availability hub.
14. Press Enter to return to the Runtime Environments (RTEs) panel (Figure 6 on page 34).
Tip: Enter V (View values) to verify the runtime environment information and U (Update) to make any necessary changes.
This completes the addition of the runtime environment. You must build the runtime libraries before continuing to configure the high-availability hub. Go on to “Step 2. Build the runtime libraries.”