OMEGAMON z/OS Management Console sans OMEGAMON?
- From: SKnutson@xxxxxxxxxxxx (Knutson, Sam)
- Date: 28 Feb 2006 07:00:15 -0800
Hi,
I loved the Health Checker prototype and have found the full Health
Checker for z/OS very useful as well if slightly more work to get going.
I have had conversations with a couple folks who have tried to convince
me to explore the OMEGAMON z/OS Management Console. I went back and
read over the documentation again.
http://www-03.ibm.com/servers/eserver/zseries/zos/hchecker/
http://www-03.ibm.com/servers/eserver/zseries/zos/zmc/
The OMEGAMON z/OS Management Console product collects and displays
availability data for your z/OS systems and Sysplex resources, but does
not include performance data. To create more complex situations and
monitor the response time of paging data sets, you must purchase and
install the IBM Tivoli OMEGAMON XE on z/OS product. See
http://www-306.ibm.com/software/tivoli/products/omegamon-xe-zos/.
I am getting great value from the Health Checker from which we have
tuned up a number of issues with our configuration. The exceptions
produce WTO's which we consolidate with OPSMVS and push to email and our
event management console.
There are a limited number of "situations" included with ZMC that are
not included with Health Checker
Predefined situations provided by the OMEGAMON z/OS Management Console:
KHL_AddressSpace_Waiting raises an alert if an address space is in a
long wait.
KHL_CF_Paths_Problem raises an alert if a coupling facility path in the
sysplex is inactive or not operational.
KHL_CF_Structures_Problem raises an alert if a coupling facility
structure in the sysplex fails.
KHL_CF_Systems_Problem raises an alert if an unexpected status is
detected for a coupling facility in the sysplex.
KHL_GTF_Active indicates whether the GTF tracing facility is active.
KHL_HealthChecker_Problems raises an alert when IBM Health Checker for
z/OS software is not active on a system.
KHL_High_Severity_Check raises an alert when the IBM Health Checker for
z/OS software detects one or more high-severity exceptions.
KHL_OLTEP_Active indicates whether the Online Test Executive Program
(OLTEP) is active.
KHL_Paging_Dataset_Utilization raises an alert when the paging data sets
exceed the threshold set for percentage of slots in use.
KHL_RMF_Problem raises an alert when the Resource Management Facility
(RMF) is not active on a system.
KHL_SMF_Problem raises an alert when the System Management Facility
(SMF) is not recording information.
KHL_Syslog_Problem raises an alert when the system log (SYSLOG) is not
recording information.
KHL_XCF_Paths_Problem raises an alert if a cross-system coupling
facility (XCF) signaling path in the sysplex is not working.
KHL_XCF_Systems_Problem raises an alert if a system shows a status other
than Active.
There are also a limited number of predefined workspaces:
Sysplex-level z/OS Management Console
Coupling Facility Systems Data for Sysplex workspace
Coupling Facility Structures Data for Sysplex workspace
Coupling Facility Structures Data for Sysplex workspace
Coupling Facility Paths Data for Sysplex workspace
XCF Systems Data for Sysplex workspace
XCF Paths Data for Sysplex workspaceSystem-level
Address Space Data for z/OS workspace
Operations Status Data for z/OS workspace
Paging Dataset Data for z/OS workspace
Health Monitor Status workspace
Health Monitor Checks workspace
Check Messages workspace
This is a fairly small list of additional checks and displays most of
which are duplicated by TMON, MXI, SHOWMVS, existing automation and our
Health Checker notification automation. To get it I have to requisition
yet another pane of glass in the ops room to provide the UDB and app
server possibly also server as the display station, SMP/E install the
host components, request the network connections (you don't just go
slinging bits up and down from the MF without talking to the network
gurus first), run new host address spaces (How much memory, CPU, TCP/IP
traffic, XCF traffic, disk storage will all these take), and have
installed software on a few client computers as well which will
doubtless have to be maintained. All this to get "pretty"?
It seems to me like the ZMC without OMEGAMON just doesn't have enough
added value to make it worthwhile to implement. Is anyone running ZMC
who does NOT have OMEGAMON and feels it is worth doing? Would you care
to share a little about why you found it useful and how much it "cost"
in computer resources and the time of carbon based units to do the
setup? I am not unwilling but I have not been sold yet.
Best Regards,
Sam Knutson, GEICO
Performance and Availability Management
mailto:sknutson@xxxxxxxxx
(office) 301.986.3574
"Think big, act bold, start simple, grow fast..."
][
====================
This email/fax message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution of this
email/fax is prohibited. If you are not the intended recipient, please
destroy all paper and electronic copies of the original message.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.
- Prev by Date: Re: Fw: Tax chooses dead language - Austalia
- Next by Date: Re: z/OS 1.8 (pre) announcement
- Previous by thread: Our D.R. situation (was:RE: Changing an IODF in batch)
- Next by thread: IEW2413I -- Just Curious
- Index(es):
Relevant Pages
|
