Tivoli OMEGAMON XE on z/OS provides two sets of predefined workspaces: sysplex-level and system-level. These workspaces provide data in tabular and graphic form and enable you to effectively monitor the availability, resource consumption, and performance of your sysplexes and their component z/OS systems.
The sysplex-level workspaces provide data on coupling facilities, global enqueue, GRS ring systems, report classes, service classes, resource groups, shared DASD groups, and cross-system coupling facilities (XCFs) used by each sysplex. The system-level workspaces report data on address space CPU utilization, storage usage and bottlenecks, channel activity, common storage usage, single image DASD device usage, Workload Manager service class resource usage, and LPAR cluster activity for the z/OS images that participate in the sysplex, as well as the status and configuration of any installed IBM cryptographic coprocessors.
Tivoli OMEGAMON XE on z/OS provides a Sysplex Enterprise Overview workspace, which allows you to monitor the status and performance of your sysplexes and shared resources at a glance.
Organization of Tivoli OMEGAMON XE on z/OS workspaces
Accessing Tivoli OMEGAMON XE on z/OS workspaces
See also: System Workspaces, Sysplex Workspaces
The physical view of the CandleNet Portal Navigator shows an enterprise as a mapping of platforms, systems, agents, and monitored resources. In a sysplex environment, monitored sysplexes appear between the platform and system levels of the Navigator tree, listed by their managed system names.
ENTERPRISE enterprise level
z/OS Systems
SYSPLEX1:MVS:SYSPLEX sysplex
SYSPLEX2:MVS:SYSPLEX sysplex
Below each sysplex name are entries that represent a
set of common objects shared by the sysplex that are monitored by Tivoli
OMEGAMON XE on z/OS, and
entries that represent z/OS systems
or LPARs being monitoring by Tivoli OMEGAMON XE on z/OS.
SYSPLEX1:MVS:SYSPLEX sysplex
Coupling Facility Policy
Data for Sysplex
Coupling Facility Structures
Data for Sysplex
...
System1
System2
Each entry is associated with one or more workspaces which
provide information on those monitored objects. For example, the Shared
DASD Groups Data for Sysplex entry is associated with the Shared DASD
for Groups workspace, which provides information about sysplex-wide activity
of shared DASD devices. From the Shared DASD for Groups workspace you
can link to the Shared DASD Devices workspace, which displays information
about the activity of the shared devices for a selected group, averaged
over all systems in the sysplex.
Under each system name is an entry for each type of resource
monitored by a Tivoli OMEGAMON XE monitoring agent on that LPAR. For example,
if you have installed both Tivoli OMEGAMON XE on z/OS and Tivoli OMEGAMON
XE for IMS, you will see two entries at this level:
System1
MVS Operating System
SYSPLEX:SYSTEM1:MVSSYS
IMS
Under each agent entry is an entry for the managed system.
Sysplex managed system names take the form
plexname:MVS:SYSPLEX
where plexname is normally the true name of the sysplex but could be configured to be an alias name for the sysplex.
LPAR managed system names take the form
plexname:smfid:MVSSYS
where plexname is normally the true name of the sysplex but could be configured to be an alias name for the sysplex. (This part of the LPAR managed system name typically matches the plexname component of its parent sysplex in the navigation tree.) The smfid component is the true SMF ID for the LPAR being monitored.
To see a description of a particular workspace, or to find instructions for accessing it, select its name in the Contents tab. Workspaces are listed alphabetically by type (sysplex-level or system-level).
All of the system-level workspaces except the Enqueue and Reserve Summary and Address Space Bottlenecks workspaces can record and report historical data. All of the sysplex-level workspaces, with the exception of the Users Data for CF Structure, GRS Ring Systems Data for Sysplex, and the Members Data for XCF Group workspaces can record and report historical data.
Workspace views that have history recording enabled have the history icon in the upper left corner.
In order for historical data to be reported, historical data collection must be configured and enabled on all Candle Management Servers in a sysplex. (Since the identity of sysplex proxy Candle Management Server can vary, the CandleNet Portal cannot know which address space is currently serving as the proxy.)
For information on configuring Tivoli OMEGAMON XE on z/OS data storage, see Configuring OMEGAMON XE on z/OS.
For information on configuring and reporting of historical data collection with the CandleNet Portal, see Historical Reporting Overview, Historical Reporting, Configure History Data Collection, and Using OMEGAMON XE on z/OS.
You can modify the predefined workspaces to better meet site-specific monitoring requirements, or create your own workspaces for specific monitoring purposes. (If you modify the predefined workspaces, you must save them with a new name.)
For help creating custom workspaces, see Edit a Workspace, Create a Workspace, Workspace Customization Options.
To access Tivoli OMEGAMON XE on z/OS workspaces from the Navigator:
Expand the Navigator tree by double-clicking the
Enterprise item,
if necessary.
Select (click) z/OS Systems.
Under OS/390 you will see entries for all the sysplexes you are monitoring
with IBM Tivoli OMEGAMON XE on z/OS. When you expand the beside the sysplex managed system name, you will see the
Navigator items associated with the sysplex-level workspaces. You will
also see entries for every system (LPAR) in the sysplex.
|
Enterprise level |
|
Operating platform level |
|
Sysplex level (managed system name) |
|
Sysplex workspaces |
|
. |
... |
. |
|
System |
|
System |
|
|
|
|
|
|
When you expand a system entry, you see a Navigator item for the Tivoli OMEGAMON XE on z/OS agent (MVS Operating System), as well as an item for every Tivoli OMEGAMON XE agent that you have installed on that system (for example, Storage Subsystem for Tivoli OMEGAMON XE for Storage).
When you select the managed system name of a sysplex or an LPAR ( for example, LPAR320M:SYSG:MVSSYS), a list of available workspaces for the sysplex or LPAR is displayed below the name.