Completing the configuration

Edit online

There are a number of steps you must take outside of the configuration profile to complete the configuration of OMEGAMON for z/OS. The steps you have remaining to complete depend on what steps you have already taken, what options you have chosen, and what you intend to monitor.

If you have not already done so, complete the following steps to ensure that you have the definitions that have been created in the configuration in your runtime environment.

The following tasks must be completed for every product and can be completed all at one time for all the products.

Note that if you run the WKANSAMU(KCIJcSYS) job (where c = P if SYSV is not enabled; V if SYSV is enabled), all the STCs and VTAM major nodes are copied to the system libraries specified for the GBL_DSN_SYS1_* parameter in the configuration profile. If you are using the global VTAM node (RTE_VTAM_GBL_MAJOR_NODE parameter), you can use the WKANSAMU(ccccAPF) imbed member to VARY the node and APF authorize the load libraries. To use ccccAPF, uncomment the placeholder INAPF INCLUDE statement in each started task:

//******************************************************************    
//* Uncomment out the INAPF statement if are using this composite       
//* member to APF-authorize the libraries concatenated in the           
//* STEPLIB and RKANMODL DDNAMEs.                                       
//*INAPF INCLUDE MEMBER=IBMAPF

If you are using a local node, you must VARY the node active and authorize the libraries yourself.

To complete configuration of the OMEGAMON® Subsystem:

If you intend to collect ICSF data:

If you intend to collect UNIX System Services information:

If you have configured use of coupling facility, cross-system coupling facility, or system lock data collected by Resource Measurement Facility:

Enable RMF data collection.

If you have accepted the default (enabled) or configured near-term history collection from Resource Measurement Facility:

Enable RMF data collection.

If you intend to collect historical data using IBM Tivoli Monitoring:

Configure historical data collection

If you intend to warehouse the historical data in the Tivoli Data Warehouse, but the hub monitoring server is not located on the same computer as the Tivoli Enterprise Portal Server:

Enable Warehouse agents on a z/OS hub monitoring server.

To enable monitoring of Sysplex DASD device data:

Create situations to filter DASD device collection.

If you want to use OMEGAMON for z/OS to help you plan special processor resources:

Set the PROJECTCPU control in the SYS1.PARMLIB IEAOPTxx member.

If you previously used IBM® OMEGAMON z/OS Management Console situations and you want to replace them with OMEGAMON for z/OS situations:

Recreate or replace z/OS Management Console situations

Finally, perform the following tasks to complete the configuration: