Prerequisites for data collection and display

For an IBM® Z OMEGAMON Monitor for z/OS 5.6 monitoring agent to collect certain types of data, the Tivoli Enterprise Monitoring Server address space in which it is configured must be assigned a user ID and given the appropriate authorization. In addition, some attributes or attribute groups collect and display data only if specific conditions are met.

To monitor UNIX® System Services, the Tivoli® Enterprise Monitoring Server must be identified to your security authorization facility as a UNIX System Services user as described in Authorizing address spaces for UNIX System Services).

To monitor coupling facility, cross-system coupling facility, or lock data collected by RMF™, the Tivoli Enterprise Monitoring Server must have an RACF® ID and the ID must be authorized to generate PassTickets, as described in Enabling RMF data collection.

To collect RMF near-term history data, the Tivoli Enterprise Monitoring Server and OMEGAMON® Subsystem must have an RACF ID and the ID must be authorized to generate PassTickets, as described in Enabling RMF data collection.

Table 1 describes the additional prerequisites for collection and display of certain types of data.

Table 1. Data prerequisites
The additional prerequisites for collection and display of certain types of data.
Data is available for	Only if
4 Hour MSUs attribute in the System CPU Utilization attributes group	A defined capacity is used as a basis for pricing and the z/OS® system is not running as a guest on z/VM®.
Channel Path attributes	The IBM Resource Measurement Facility (RMF) has been started.
Common Storage attributes	The Common Storage Area Analyzer (CSA Analyzer) is started. Note: The CSA Analyzer is shipped and installed with IBM Z OMEGAMON Monitor for z/OS 5.6. It is started as a separate started task.
Coupling facility and cross-system coupling facility (XCF) data collected by the IBM Resource Measurement Facility (RMF) Distributed Data Server (DDS)	The following RMF components are activated: RMF Control Task (RMF)–one instance on each system RMF Monitor III Gatherer (RMFGAT)–one instance on each system RMF Distributed Data Server (GPMSERVE)–one instance per sysplex You have enabled RMF data collection as described in Using RMF data collection.
Cryptographic attributes	At least one IBM cryptographic coprocessor must be installed. KM5EXIT3 and KMEXIT4 exits must be installed in the Integrated Cryptographic Service Facility (ICSF). Note: The KM5EXIT3 and KM5EXIT4 exits are shipped and installed with IBM Z OMEGAMON Monitor for z/OS 5.6. See Make KM5EXIT3, KM5EXIT4, and KM5CSFSX modules available to ICSF for more information. The USERID for the IBM Z OMEGAMON Monitor for z/OS 5.6 TEMS STC (typically xxxxDS) has access to the required ICSF Callable Services. See Activate the changes to ICSF for more information.
DASD MVS™ workspace and DASD MVS Devices attributes	RMF has been started.
GRS Ring Systems attributes	The global resource serialization (GRS) complex is in ring mode. (If the complex is in star mode, only the name, status, and ring acceleration of each system are available.)
Health Check attributes	IBM Health Checker for z/OS software be installed, configured, and running.
HiperDispatch Management and HiperDispatch Logical Processors attributes	HiperDispatch Management mode is On.
Integrated Facility for Applications (IFA) on CP resource times at the address space and service class period level	Either z/Series Application Assist Processors are configured on the systems, or Java™ applications are started using a switch (-Xifa:force)
LPAR cluster attributes	The z/OS system is not running as a guest on z/VM.
Model Permanent Capacity ID and Rating and Model Temporary ID and Rating	System hardware is z10™ or later.
Near-term history data collected by the Resource Measurement Facility (RMF) Distributed Data Server.	The following components are activated: OMEGAMON Subsystem - at least one instance per sysplex (two for redundancy), up to one instance on each monitored system RMF Control Task (RMF) - one instance on each monitored system RMF Monitor III Gatherer (RMFGAT) - one instance on each monitored system RMF Distributed Data Server (GPMSERVE) - one instance per sysplex You have enabled RMF data collection as described in Using RMF data collection
Promoted Percent	The z/OS Workload Manager blocked workload capability is enabled.
Sysplex DASD attributes (Sysplex DASD Device, Sysplex DASD Group, Sysplex DASD)	A DASD filter situation is enabled.
Suspend lock and spin lock data	The following RMF components activated: RMF Control Task (RMF)–one instance on each system RMF Monitor III Gatherer (RMFGAT)–one instance on each system RMF Distributed Data Server (GPMSERVE)–one instance per sysplex You have enabled RMF data collection (see Using RMF data collection). Lock data collection is enabled on RMF.
zFS attributes	zFS is specified as the file system on the monitored system (FILESYSTEM TYPE(ZFS) is specified in SYS1.PARMLIB(BPXPRMxx)). Note: For z/OS 1.10, IBM Z OMEGAMON Monitor for z/OS 5.6 uses an address space name of ZFS, unless the parameter KM3KZFSASNM=xxxxxxxx (where xxxxxxxx is the started task (STC) name of the zFS address space) has been added to the &rhilev.&rte.RKANPARU(KDSENV).
z/OS UNIX System Services attributes	The address space where the IBM Z OMEGAMON Monitor for z/OS 5.6 product is running has SUPER USER authority. This level of authority is equivalent to root (UID=0).