omegamon ims 530 introduction
TRANSCRIPT
QPlan and QCert Template
Omegamon IMS 530 Introduction
Greg Krause March 2016
Overview
Monitor IMS systemsPerformance ( transactions, databases, IO )
Resources ( storage, cpu, applications, pools )
Problems
Historical Metrics
Application and transaction tracingReal-time response times, CPU , DB and System call details
User Threshholds, generating alerts
Multiple User InterfacesClassic, e3270, TEP
IMSplex level monitoring
Classic.mainMenu
monitor.IMS status
monitor.Potential problems
monitor.plot IMS
workload.DMBs (DI21PART)
A
Psbc - # of PSBs currently active and using this DMB
Admb address of DMB
Accs the highest access intent
Casp - # CA (control area) splits
Cisp - # CI ( control interval) splits
Dres residency ( in memory , or not )
Dsiz size of DMB
Id#, ir#, it# - non-zero if I/O error has occurred. RBA of error,and error type
VDDN VSAM info
Sched -
Stat -
workload.Regions.BMPs
Pools.Communication.I/O pool
CIOP. Communications I/O pool
Pools.Communication.Msg queue
fs QBUF, msg queue buffer pool
Size: # blocks currently allocated for ( short msgs, long msgs, queue blks )
Pools.Database.VSAM buffer pool
QBUF, msg queue buffer pool
Size: # blocks currently allocated for ( short msgs, long msgs, queue blks )
Pools.Program.PSB work pool
QBUF, msg queue buffer pool
Size: # blocks currently allocated for ( short msgs, long msgs, queue blks )
Fastpath.summary
QBUF, msg queue buffer pool
Size: # blocks currently allocated for ( short msgs, long msgs, queue blks )
Exceptions
This screen appears when you do mainMenu.P
Exceptions.Operating system
This screen appears when you do mainMenu.P
Exceptions.OperatingSystem.CPU
This screen appears when you do mainMenu.P
monitor.Potential problems (exceptions)
I repeated this slide here, to show where the 'tripped exceptions' appear, and that the previous screen shows the exception descriptions
Classic.Response Time (RTA) menu
Select 'D' Intervals
Classic Response Time (RTA) Intervals
Group 11 and 15 are different transactions ( IRSP11 , IRSP15 )_
Classic Bottlenecks
3 variables add to 100%. 'using CPU' , 'database I/O', 'IMS activity'
Classic-ATF aka 'application history'
3 variables add to 100%. 'using CPU' , 'database I/O', 'IMS activity'
Classic-ATF manage traces
3 variables add to 100%. 'using CPU' , 'database I/O', 'IMS activity'
Classic-ATF define trace
3 variables add to 100%. 'using CPU' , 'database I/O', 'IMS activity'
Classic-ATF trace summary
3 variables add to 100%. 'using CPU' , 'database I/O', 'IMS activity'
Classic-ATF transaction instance summary
3 variables add to 100%. 'using CPU' , 'database I/O', 'IMS activity'
E3270ui -IMSplex Summary
E3270ui -IMS Lock Conflicts (Threshholds)
User Threshholds exceeded, results in colored fields in table view
E3270ui -IMS system information
E3270ui ATF group summary
E3270ui ATF transaction instance summary
E3270ui - IMS Health (historical)
'historical' view available to all workspaces
end of 530 presentation
TEP Monitor many IMS, IMSplex
TEP IMS Health
TEP IMS Health History
Can do History view on any workspace, here we do it for 'Health'
TEP IMS Address Spaces
TEP Bottlenecks
TEP Pools
TEP RTA Group Summary
TEP VSAM Subpool statistics
TEP IMSplex, Global Lock Conflicts
TEP Situation Defined
'Situation' ( AKA Classic.exception, e3270ui.Threshhold
TEP Situation Triggered
ibm_light_gray_logo_300dpi
IBM Software Group
ibm_white_logo_300dpi
IBM Software Group
2012 IBM Corporation
IBM Confidential
Tivoli SoftwareIBM Confidential 2009 IBM Corporation
IBM Software Group | Tivoli software
IBM Confidential