Manuals / Candle-lite / Computer Equipment / Network Card

Candle-lite DB2 manual Setting Up !DB/EXPLAIN, Setting Up the CUA Options, Sqlid.Plantable

Models: DB2

1 132

Download 132 pages 16.76 Kb

Page 58

Using the Callable Interface

Step

Action

6Use option 1, Realtime monitor interface members, to submit the job.

This job creates a started task in RKD2PAR. The name of this started task is D2TE or the value entered on this panel for the parameter TESTC. Copy this started task to the JES2 procedure library for started tasks. This task dynamically allocates the !DB/EXPLAIN profile dataset. Configuration options for !DB/EXPLAIN will be obtained from this dataset.

Note: Do not start this task. OMEGAMON II for DB2 starts this task whenever a !DB/EXPLAIN function is performed and stops it when the function has completed.

Setting Up !DB/EXPLAIN

Use the following procedure to set up !DB/EXPLAIN on the OMEGAMON II for DB2 Commands screen.

Step		Action

1	Ensure that !DB/EXPLAIN V300 PSP 9602 (or greater) is installed on every DB2
	subsystem where you want to EXPLAIN statements. For information on installing
	!DB/EXPLAIN, see the !DB/Tools for DB2 Installation and Customization Guide.

2	Define Destination Plan_Tables. The Destination PLAN_TABLE will be the current
	SQLID.PLAN_TABLE.
	■	If the current SQLID.PLAN_TABLE does not exist, !DB/EXPLAIN attempts to
		create the tablespace PLANTBLS in the !DB/TOOLS default database.
	■	If the PLAN_TABLE cannot be created there, !DB/EXPLAIN attempts to create the
		PLAN_TABLE in the database DSNDB04.
	■	If it cannot create the table, !DB/EXPLAIN issues an error message indicating that
	■
		the EXPLAIN could not be performed.
	The current SQLID is determined by:
	■	whether EXP_POWERX is defined in the !DB/Tools profile dataset concatenation as
	■
		a non-blank value (for example, EXP_POWERX=SAMHILL), if so, the current
		SQLID is the value specified for EXP_POWERX,
	■	or the current SQLID is determined by the DB2 security exit.

Setting Up the CUA Options

Use the following procedure to set up CUA options and to use the new !DB/EXPLAIN feature.

Step	Action

1	Log onto CUA.

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

Image 58

Candle-lite DB2 manual Setting Up !DB/EXPLAIN, Setting Up the CUA Options, Sqlid.Plantable, Step Action Log onto CUA

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 informationAdobe 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 reportsUnicode support Bit addressing supportLong name support Enclave supportNew Dsnzparm fields Distributed Thread display improvementsOmegamon II for DB2 User’s Guide CUA Interface, Version Chapter Contents IntroductionLogging on to the application Where applid is the application nameSigning On Sign On panelFields of the Sign On Panel are defined in the table below Accessing Omegamon from OmegaviewSign On panel fields Field DescriptionSetting Logon Options Logon Options panel fieldsLogical rows Number of logical rows Signing Off Returning to Omegaview from OmegamonPanel features Panel FeaturesPart Feature Description Part Feature Description Highlighted data fields Data PanelsDescription ScrollingPushbuttons Selecting from the action bar Action BarFast pathing from the action bar Actions pull-down GoTo pull-down View pull-downTools pull-down Options pull-downHelp pull-down Available action codes Using an action codeAction Codes You can use these action codes in OmegamonFunction key assignments Default function key assignments are listed belowFunction Keys Function Name Assignment KeyOmegaview CUA/TSOPA1 PA2 OmegaviewHelp from the action bar Getting HelpHelp from a panel Help menu provides the following selectionsSearching 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 PreferencesAction to occur Using the Terminal Options window Accessing the Terminal Options windowSpecifying Terminal Options Auto Values for SQL Description Process LevelManual SaveSaving for current session Saving Terminal OptionsSaving to a profile Using the thresholds windows Setting ThresholdsAccessing the Thresholds window Follow these steps to change threshold valuesSaving threshold values Adding a user Accessing user authoritiesAssigning User Authorities Deleting a userProfile types Accessing profile maintenanceMaintaining Profiles Omegamon II uses three different profilesD61A$DEFAULT Copying a profileDeleting a profile Importing a ProfileExporting a Profile Modifying a profile descriptionSwitching profiles Using the Dynamic Profile Update FacilityMVS 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 followsUsing the Filter Options window Setting Filtering Options for Near-Term Thread HistoryAccessing the Filter Options window To access the Filter Options pop-up windowTime 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 optionsSQLID.PLANTABLE Setting Up !DB/EXPLAINSetting Up the CUA Options Step Action Log onto CUASetting Up the D2/EXPLAIN Options Use the following procedure to set up the D2/EXPLAIN optionsText 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 OmegamonDB2 subsystem components Monitoring from the System Status PanelMonitored objects Investigating an alert Status indicatorsAlert notification Color StatusPerforming actions from the System Status panel Cics exceptions System Status Components and Related ExceptionsDescription Code Explanation Background exceptions IMS exceptionsTSO exceptions Utility exceptionsActive thread exceptions Following exceptions apply to active threadsBuffer pool exceptions Inactive thread exceptionsFollowing exceptions apply to buffer pool resources Log manager exceptions EDM pool exceptionsLock statistics exceptions DDF statistics exceptionsFollowing exceptions apply to DB2 activity alerts DB2 activity exceptionsLock exceptions Following exceptions apply to lock alertsStored 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 functionsException recommendations Investigating an Active Threads AlertActive threads alert Investigating the exception conditionDisplaying 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 optionsViewing 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 createActivities 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 DB2When 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 optionUsing the D2/EXPLAIN Options Panel PDSFrom 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 informationSources of information Task You Want to Perform Source of InformationPage Panel Navigation Flowcharts Appendix ContentsSystem Status panel Flowchart ConventionsElement Description System Status DB2Workloads Panels IMS CicsTSO Workloads Panels Near-term history Cics IMS TSOResources 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