68 IBM Tivoli OMEGAMON XE V3.1 – Deep Dive on z/OS
7. The last option from Tivoli Enterprise Monitoring Server configuration
explains the tasks to complete the configuration outside of the configuration
tool. This step requires you to perform several tasks. These are the tasks that
we performed in our setup:
a. Copy the Candle Management Server started task CANSDSST from
b. Copy persistent data store procedures to PROCLIB:
KPDPROC1: Sample PDS maintenance procedure
KPDPROC2: Batch job procedure to back up, export,
c. Create system variable members. We enabled system variable support, so
we ran the CB#VSHR1 system variable members job to create the system
variable parameter member and other components.
d. Copy VTAM definitions to VTAMLST and vary VTAM major node active.
Use this console command:
e. APF-authorize libraries are libraries from our base RTE:
f. Verify installation and configuration. Start the Candle Management Server
started task using this command:
The output from the CANSDSST task should contain these messages:
KDSMA001 Candle Management Server (CMS) data collection
server started.
KO4SRV032 Candle Management Server (CMS) startup complete.
3.3.5 Configuring OMEGAMON II for MVS
Next, set up the OMEGAMON II for MVS. The configuration of OMEGAMON II
for MVS requires several steps. You must specify configuration values, create
runtime members, and register the OMEGAMON II for MVS parameters with the
Tivoli Enterprise Monitoring Server configured in this RTE. This also upgrades
any previous version of OMEGAMON II for MVS in this RTE automatically.
Note: You can dynamically add the above data sets to your APF list by
using these commands:
Chapter 3. Installation and configuration: IBM Tivoli OMEGAMON XE 69
For a new RTE, you must also install the Candle subsystem, a z/OS subsystem
that runs in its own address space and enables OMEGAMON IIs in other address
spaces to monitor dynamic I/O information. A single Candle subsystem can
support multiple OMEGAMON II address spaces. The Candle subsystem
requires the KCNDLINT module to be in the link list.
Figure 3-27 shows the configuration of OMEGAMON II for MVS.
Figure 3-27 OMEGAMON II for MVS configuration list
Note: Be sure you have the latest version of the Candle subsystem running;
otherwise, unpredictable results may occur.
---------------- CONFIGURE OMEGAMON II FOR MVS / RTE: SHR1 -----------------
OPTION ===> 1
Last selected
Perform these configuration steps in order: Date Time
1 Specify configuration values 05/11/14 15:40
2 Allocate historical datastores 05/11/14 15:40
3 Create runtime members 05/11/02 10:34
4 Modify Classic interface command security 05/11/14 15:39
5 Register with local CMS 05/11/14 15:39
6 Install Candle Subsystem 05/11/03 10:17
7 Complete the configuration
8 Run migration utility
70 IBM Tivoli OMEGAMON XE V3.1 – Deep Dive on z/OS
1. Specifying the configuration values with option 1 from Figure 3-27 on
page 69, we get the dialog shown in Figure 3-28.
Figure 3-28 OMEGAMON II for MVS definition
------------------------- SPECIFY CONFIGURATION VALUES ---------------------
Started tasks:
Realtime collector OMEGAMON ==> CANSM2RC
CSA analyzer ==> CANSM2CS
Historical collector (EPILOG) ==> CANSM2HI
Historical data interface ==> CANSM2HD
End-to-End (ETE) ==> CANSETE
VTAM and OMEGAMON II information:
Applid prefix ==> K&SYSCLONE.M2
Virtual terminal prefix ==> K&SYSCLONE.M2
Maximum number of CUA users ==> 99 (10-256)
Maximum number of collector users (UMAX) ==> 99 (1-99)
Enable WTO messages ==> N (Y, N)
Enter=Next F1=Help F3=Back F6=Applids

Get IBM Tivoli OMEGAMON XE V3.1 Deep Dive on z/OS now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.