Manuals / Candle-lite / Computer Equipment / Network Card

Candle-lite DB2 manual System Status Components and Related Exceptions, Cics exceptions

Models: DB2

1 132

Download 132 pages 16.76 Kb

Page 69

System Status Components and Related Exceptions

System Status Components and Related Exceptions

OMEGAMON II monitors your DB2 subsystem by comparing the performance of your subsystem against a set of performance standards. These standards are called thresholds. When the performance of a workload or a resource exceeds a threshold, an exception condition occurs.

The status indicators on the System Status panel summarize the status of the thresholds that you set in OMEGAMON. When OMEGAMON detects that a threshold has been exceeded, the status indicators for all panels that report on that threshold are affected, including the System Status panel.

The following tables are a quick reference to the exceptions that affect the status indicators for components on the System Status panel.

CICS exceptions

The following exceptions apply to threads related to CICS connections.

Description	Code	Explanation

Available pool thread %	POLU	The percentage of active CICS POOL threads to THRDA
		exceeds the specified threshold. The THRDA value is
		specified in the CICS resource control table (RCT).

CICS threadmax %	CICT	The percentage of active CICS threads to THRDMAX
		exceeds the specified threshold. The THRDMAX value is
		specified in the CICS RCT.

CICS transaction	ENTW	The number of CICS transactions waiting for a thread
waiting		exceeds the specified threshold. This exception detects
		transactions that are waiting, because all threads defined for
		use in the RCT ENTRY definition are already in use. This
		exception limits its analysis to ENTRY definitions that
		specify TWAIT=YES.

ENTRY thread %	ENTU	The percentage of active threads that originate from a CICS
		ENTRY definition to THRDA exceeds the specified
		threshold. The THRDA value is specified in the resource
		RCT.

Pool overflow threads	ENTO	The number of POOL threads in use due to ENTRY thread
		overflow activity exceeds the specified threshold. This
		exception limits its analysis to ENTRY definitions that
		specify TWAIT=POOL and THRDA>0.

Pool thread waits	POLW	The number of CICS transactions waiting for a POOL
		thread that originates from a CICS connection exceeds the
		specified threshold.

Using OMEGAMON II

69

Image 69

Candle-lite DB2 manual System Status Components and Related Exceptions, Cics exceptions, Description Code Explanation

Contents

User’s Guide CUA Interface Omegamon II for DB2 User’s Guide CUA Interface, Version Contents Index 129 List of Figures Omegamon II for DB2 User’s Guide CUA Interface, Version Preface About This Book Where to look for informationWho should read this book Documentation set informationPrinting problems? Adobe Portable Document FormatIntroduction Documentation Conventions REPORT=SUMMARY Histogram Candle Customer Service and Satisfaction Candle Customer Service and Satisfaction contactsBackground Page Omegamon II for DB2 User’s Guide CUA Interface, Version New IFCID-based reports Historical Reporter redesignLong name support Bit addressing supportUnicode support Enclave supportDistributed Thread display improvements New Dsnzparm fieldsOmegamon II for DB2 User’s Guide CUA Interface, Version Introduction Chapter ContentsSigning On Where applid is the application nameLogging on to the application Sign On panelSign On panel fields Accessing Omegamon from OmegaviewFields of the Sign On Panel are defined in the table below Field DescriptionLogon Options panel fields Setting Logon OptionsLogical rows Number of logical rows Returning to Omegaview from Omegamon Signing OffPanel Features Panel featuresPart Feature Description Part Feature Description Description Data PanelsHighlighted data fields ScrollingPushbuttons Action Bar Selecting from the action barFast pathing from the action bar Actions pull-down View pull-down GoTo pull-downOptions pull-down Tools pull-downHelp pull-down Action Codes Using an action codeAvailable action codes You can use these action codes in OmegamonFunction Keys Default function key assignments are listed belowFunction key assignments Function Name Assignment KeyPA1 CUA/TSOOmegaview PA2 OmegaviewHelp from a panel Getting HelpHelp from the action bar Help menu provides the following selectionsUsing the Glossary Searching the glossaryIf you are Help function keys Customizing Omegamon Introduction Using the Preferences window Accessing the Preferences windowTo access the Preferences pop-up window Specifying Panel PreferencesAction to occur Accessing the Terminal Options window Using the Terminal Options windowSpecifying Terminal Options Manual Values for SQL Description Process LevelAuto SaveSaving Terminal Options Saving for current sessionSaving to a profile Accessing the Thresholds window Setting ThresholdsUsing the thresholds windows Follow these steps to change threshold valuesSaving threshold values Assigning User Authorities Accessing user authoritiesAdding a user Deleting a userMaintaining Profiles Accessing profile maintenanceProfile types Omegamon II uses three different profilesCopying a profile D61A$DEFAULTExporting a Profile Importing a ProfileDeleting a profile Modifying a profile descriptionUsing the Dynamic Profile Update Facility Switching profilesExample command for importing a profile Example command for exporting a profileMVS Modify command for exporting a profile is as follows MVS Modify command for importing a profile is as followsAccessing the Filter Options window Setting Filtering Options for Near-Term Thread HistoryUsing the Filter Options window To access the Filter Options pop-up windowTime Accessing the Save SQL Text Parameters window Using the Save SQL Text Parameters windowSpecifying Save Options for SQL Text Set up the CUA options Set up the !DB/EXPLAIN options Using the Callable InterfaceSetting Up the CUA Options Setting Up !DB/EXPLAINSQLID.PLANTABLE Step Action Log onto CUAUse the following procedure to set up the D2/EXPLAIN options Setting Up the D2/EXPLAIN OptionsText and invokes the Explain function Use the following procedure to Explain SQL EXPLAINing SQL CodeAppend CPU % Press the Process SQL key Page This chapter describes how to use Omegamon Using OmegamonMonitoring from the System Status Panel DB2 subsystem componentsMonitored objects Alert notification Status indicatorsInvestigating an alert Color StatusPerforming actions from the System Status panel System Status Components and Related Exceptions Cics exceptionsDescription Code Explanation TSO exceptions IMS exceptionsBackground exceptions Utility exceptionsFollowing exceptions apply to active threads Active thread exceptionsInactive thread exceptions Buffer pool exceptionsFollowing exceptions apply to buffer pool resources Lock statistics exceptions EDM pool exceptionsLog manager exceptions DDF statistics exceptionsLock exceptions DB2 activity exceptionsFollowing exceptions apply to DB2 activity alerts Following exceptions apply to lock alertsVolume activity exceptions Stored procedures exceptionsActive trace exceptions User-defined functions exceptions Triggers exceptionsFollowing exceptions apply to alerts relating to triggers Following exceptions apply to user-defined functionsActive threads alert Investigating an Active Threads AlertException recommendations Investigating the exception conditionEvaluating and Modifying Thresholds Displaying all exceptionsModifying thresholds Adding or modifying rules Accessing near-term history data Reviewing Near-Term History DataThread activity for a reporting period Thread activity for a report interval Specifying background application trace options Initiating a background application traceIdentifying the dataset to which trace data is written Size Size of the dataset in megabytes VolumeViewing the list of background traces Name of the dataset you want to createActivities you can perform in a background trace request Using the Ifcid Trace Facility OverviewStarting an Ifcid Trace Displaying Ifcid Trace Data Stopping an Ifcid Trace Page Using Omegamon II for DB2 Functions provided by !DB/EXPLAIN for DB2 Background about !DB/EXPLAIN for DB2Using Omegamon II and !DB/EXPLAIN Complementary Functions When to use the complementary functionsAssumptions Using Omegamon II and !DB/EXPLAIN Complementary Functions Using the Omegamon II for DB2 Callable Interface Testc Current Sqlid is determined by the DB2 security exit Fields for Terminal Description Options SQL Text ATF. You can access the SQL Text panel through Required fields for the SAVE/EXPLAIN option SAVE/EXPLAINPDS Using the D2/EXPLAIN Options PanelFrom the other !DB/EXPLAIN report sections that follow Press the Process SQL key Moving Interactively between !DB/EXPLAIN and Omegamon What functions can you use?Modes of operation Prerequisites for real time access Procedure to use the full function of !DB/EXPLAINWhat happens when you cancel the Omegamon II session? Using the Copy-and-Paste Facility in Omegamon Prerequisites to using the copy-and-paste facilityCapturing SQL from a running thread Capturing SQL using the ATF Direction of access Accessing Omegamon II Trace Information from !DB/EXPLAINPrerequisites for using the Omegamon II trace information Procedure to obtain current trace informationTask You Want to Perform Source of Information Sources of informationPage Appendix Contents Panel Navigation FlowchartsFlowchart Conventions System Status panelElement Description DB2 System StatusWorkloads Panels Cics IMSTSO Cics IMS TSO Workloads Panels Near-term historyResources Panels Resources Panels Realtime Resources Panels Near-Term History Alerts Panels Alerts Panels Installation Parameters Panels Installation Parameters Panels Application Trace Facility Panels Application Trace Facility Panels Object Analysis Panels Object Analysis Panels Thread Detail GoTo Panels Thread Detail GoTo Panels Realtime Thread History Detail GoTo Panels Near-Term History Index Omegamon II for DB2 User’s Guide CUA Interface, Version 131 Omegamon II for DB2 User’s Guide CUA Interface, Version