Direction of access, Procedure | Candle-lite DB2 instruction

Accessing OMEGAMON II Trace Information from !DB/EXPLAIN

Accessing OMEGAMON II Trace Information from !DB/EXPLAIN

This unit describes how you can obtain OMEGAMON II Application Trace and Accounting Report information when you are working in !DB/EXPLAIN.

Direction of access

The direction of access when obtaining OMEGAMON II Application Trace and Accounting Report information is always one-way: from !DB/EXPLAIN to OMEGAMON II, with OMEGAMON II operating under ISPF.

Prerequisites for using the OMEGAMON II trace information

Ensure the Application Trace Facility has previously been used to trace your applications and that you have current application and accounting trace information available to you in datasets whose names are known to you. You must know the name of the dataset containing the history information for the facility you want to use. You can use the OMEGAMON II OPTIONS menu to specify the input datasets or DB2 table names to use for reporting or to change their names, and to specify the report filtering selection criteria.

Procedure to obtain current trace information

If the trace information you have is not current or does not contain information about the plan or plans you want to study, follow the steps below.

Step

Action

1Toggle to OMEGAMON II using the appropriate function key.

2Start the Application Trace Facility writing to a VSAM dataset.

3Access !DB/EXPLAIN and select the plan or plans you want to study.

For information about using the OMEGAMON II for DB2 Application Trace Facility, see OMEGAMON II for DB2 Reference.

Procedure

To perform the tasks, take the actions described in the table.

Task You Want to Perform	Action to Take

Access the OMEGAMON II	On the !DB/EXPLAIN Plans panel, in the SEL (selects)
Application Trace Facility from	column, type A in the SEL field of the plan for which you
!DB/EXPLAIN	want to display application trace information.
	Result: OMEGAMON II displays the Application Trace
	Facility Menu panel.

106 OMEGAMON II for DB2 User’s Guide: CUA Interface, Version 540

Image 106

Candle-lite DB2 manual Accessing Omegamon II Trace Information from !DB/EXPLAIN, Direction of access, Procedure

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 Who should read this book Where to look for informationAbout This Book Documentation set information Adobe Portable Document Format Printing problems?Introduction Documentation Conventions REPORT=SUMMARY Histogram Candle Customer Service and Satisfaction contacts Candle Customer Service and SatisfactionBackground Page Omegamon II for DB2 User’s Guide CUA Interface, Version Historical Reporter redesign New IFCID-based reports Unicode support Bit addressing supportLong name support Enclave support New Dsnzparm fields Distributed Thread display improvements Omegamon II for DB2 User’s Guide CUA Interface, Version Chapter Contents Introduction Logging on to the application Where applid is the application nameSigning On Sign On panel Fields of the Sign On Panel are defined in the table below Accessing Omegamon from OmegaviewSign On panel fields Field Description Setting Logon Options Logon Options panel fields Logical rows Number of logical rows Signing Off Returning to Omegaview from Omegamon Panel features Panel FeaturesPart Feature Description Part Feature Description Highlighted data fields Data PanelsDescription Scrolling Pushbuttons Selecting from the action bar Action BarFast pathing from the action bar Actions pull-down GoTo pull-down View pull-down Tools pull-down Options pull-downHelp pull-down Available action codes Using an action codeAction Codes You can use these action codes in Omegamon Function key assignments Default function key assignments are listed belowFunction Keys Function Name Assignment Key Omegaview CUA/TSOPA1 PA2 Omegaview Help from the action bar Getting HelpHelp from a panel Help menu provides the following selections Searching the glossary Using the GlossaryIf you are Help function keys Customizing Omegamon Introduction To access the Preferences pop-up window Accessing the Preferences windowUsing the Preferences window Specifying Panel Preferences Action to occur Using the Terminal Options window Accessing the Terminal Options windowSpecifying Terminal Options Auto Values for SQL Description Process LevelManual Save Saving for current session Saving Terminal OptionsSaving to a profile Using the thresholds windows Setting ThresholdsAccessing the Thresholds window Follow these steps to change threshold values Saving threshold values Adding a user Accessing user authoritiesAssigning User Authorities Deleting a user Profile types Accessing profile maintenanceMaintaining Profiles Omegamon II uses three different profiles D61A$DEFAULT Copying a profile Deleting a profile Importing a ProfileExporting a Profile Modifying a profile description Switching profiles Using the Dynamic Profile Update Facility MVS Modify command for exporting a profile is as follows Example command for exporting a profileExample command for importing a profile MVS Modify command for importing a profile is as follows Using the Filter Options window Setting Filtering Options for Near-Term Thread HistoryAccessing the Filter Options window To access the Filter Options pop-up window Time Using the Save SQL Text Parameters window Accessing the Save SQL Text Parameters windowSpecifying Save Options for SQL Text Using the Callable Interface Set up the CUA options Set up the !DB/EXPLAIN options SQLID.PLANTABLE Setting Up !DB/EXPLAINSetting Up the CUA Options Step Action Log onto CUA Setting Up the D2/EXPLAIN Options Use the following procedure to set up the D2/EXPLAIN options Text and invokes the Explain function EXPLAINing SQL Code Use the following procedure to Explain SQLAppend CPU % Press the Process SQL key Page Using Omegamon This chapter describes how to use Omegamon DB2 subsystem components Monitoring from the System Status PanelMonitored objects Investigating an alert Status indicatorsAlert notification Color Status Performing actions from the System Status panel Cics exceptions System Status Components and Related ExceptionsDescription Code Explanation Background exceptions IMS exceptionsTSO exceptions Utility exceptions Active thread exceptions Following exceptions apply to active threads Buffer pool exceptions Inactive thread exceptionsFollowing exceptions apply to buffer pool resources Log manager exceptions EDM pool exceptionsLock statistics exceptions DDF statistics exceptions Following exceptions apply to DB2 activity alerts DB2 activity exceptionsLock exceptions Following exceptions apply to lock alerts Stored procedures exceptions Volume activity exceptionsActive trace exceptions Following exceptions apply to alerts relating to triggers Triggers exceptionsUser-defined functions exceptions Following exceptions apply to user-defined functions Exception recommendations Investigating an Active Threads AlertActive threads alert Investigating the exception condition Displaying all exceptions Evaluating and Modifying ThresholdsModifying thresholds Adding or modifying rules Reviewing Near-Term History Data Accessing near-term history dataThread activity for a reporting period Thread activity for a report interval Initiating a background application trace Specifying background application trace options Viewing the list of background traces Size Size of the dataset in megabytes VolumeIdentifying the dataset to which trace data is written Name of the dataset you want to create Activities you can perform in a background trace request Overview Using the Ifcid Trace FacilityStarting an Ifcid Trace Displaying Ifcid Trace Data Stopping an Ifcid Trace Page Using Omegamon II for DB2 Background about !DB/EXPLAIN for DB2 Functions provided by !DB/EXPLAIN for DB2 When to use the complementary functions Using Omegamon II and !DB/EXPLAIN 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 SAVE/EXPLAIN Required fields for the SAVE/EXPLAIN option Using the D2/EXPLAIN Options Panel PDS From the other !DB/EXPLAIN report sections that follow Press the Process SQL key What functions can you use? Moving Interactively between !DB/EXPLAIN and OmegamonModes of operation Procedure to use the full function of !DB/EXPLAIN Prerequisites for real time accessWhat happens when you cancel the Omegamon II session? Prerequisites to using the copy-and-paste facility Using the Copy-and-Paste Facility in OmegamonCapturing SQL from a running thread Capturing SQL using the ATF Prerequisites for using the Omegamon II trace information Accessing Omegamon II Trace Information from !DB/EXPLAINDirection of access Procedure to obtain current trace information Sources of information Task You Want to Perform Source of InformationPage Panel Navigation Flowcharts Appendix Contents System Status panel Flowchart ConventionsElement Description System Status DB2 Workloads Panels IMS CicsTSO Workloads Panels Near-term history Cics IMS TSO Resources 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