OMEGAMON XE for DB2 PE identifiers

Usage

DB2 trace records contain identifiers that OMEGAMON XE for DB2 PE uses to:

• Group data
• Order reports
• Identify trace records
• Include or exclude specific data

Identifiers

ACE (Agent control element address)

The absolute hexadecimal address of the DB2 agent control element for the thread. Each work request in DB2 is represented by an agent. When a work request identifies itself to DB2, an agent control element address (ACE) is used to track the agent. The agent can be:

• An allied agent representing a work request that originated in allied address spaces
• A system agent representing a work request internal to DB2

You can use this address to select records for a particular thread. Note that an ACE address can be reused after a thread terminates.

BPID (Buffer pool ID)

The buffer pool ID.

CLASS (DB2 trace class)

DB2 groups records of a similar nature into classes. When running a DB2 performance trace, you can limit the type of information that is traced by selecting one or more trace classes. OMEGAMON XE for DB2 PE can be used to select records by DB2 performance class.

CONNECT (Connection ID)

The connection identifier of the correlation header, which is the ID of the address space that interfaces with DB2. You can, for example, specify the CICS® or IMS™ ID.

CONNTYPE (Connection type)

The type of connection for a thread. You can, for example, specify that you want to include only records that have a connection type of TSO or CICS. Possible values for thread connection types are:

TSO

TSO foreground and background

DB2CALL

DB2 CALL attach

CICS

CICS attach

BATCH

DL/I batch

IMS-BMP

IMS nontransaction-oriented BMP

IMS-MPP

IMS attach MPP

IMS-CNTL

IMS control region

IMS-TBMP

IMS transaction-oriented BMP

DB2-PRIV

DB2 private protocol

DRDA®

DRDA protocol

UTILITY

Utility attach

RRS

Recoverable Resource Manager Services attach

Correlation identifier

A 12-character value identifying the DB2 task in conjunction with the connection ID.

OMEGAMON XE for DB2 PE uses the correlation ID to derive two identifiers: the correlation name and the correlation number:

CORRNAME (Correlation name)

An identifier assigned to a task. This field is a subset of the correlation ID. Its meaning varies with the connection type.

CORRNMBR (Correlation number)

An identifier assigned to a task. This field is a subset of the correlation ID. Its meaning varies with the connection type.

The location of the correlation name and correlation number within the 12-character value depends on the type of connection that the task executes in.

In distributed processing, when the application requester is a DB2 system, the value assigned to the correlation ID at the application server is the same as the value assigned to the application requester. If the application requester is not a DB2 system, the value assigned to the correlation ID at the application server is the name of the job, task, or process the requester is servicing.

For more information about correlation ID translation, see Monitoring Performance from ISPF.

DATABASE (Database name)

The name of the DB2 database.

Note that INCLUDE and EXCLUDE processing uses the character names of databases, while DB2 instrumentation records contain the decimal IDs used by DB2. OMEGAMON XE for DB2 PE translates the decimal ID to the character name.

DATASET (Data set name)

The 8-character name of the archive log, active log, or bootstrap data set (BSDS).

ENDUSER (End user ID)

The user ID of the workstation end user. This can be different from the AUTHID used to connect to DB2.

FIELD (Comparison with data in a record field)

This option is used in conjunction with the FIELD command. By using the FIELD command, you can define a value and comparison operator for a data field in a specific IFCID type. You can include or exclude records based on the result of the comparison. For more information, see FIELD command.

GROUP (Group name)

The name of the data-sharing group.

IFCID (Instrumentation Facility Component Identifier)

A decimal identifier that represents a significant DB2 event and appears in the trace records produced by DB2.

INSTANCE (Instance number)

This hexadecimal number is mainly for distributed activity and is part of the LUWID. It can be used to match the activity performed by DBATs, DBAT-distributed threads, and allied-distributed threads. The instance number is allocated at thread creation.

LOCATION (Location name)

The name of a DB2 system. The location name is unique among DB2 systems that can communicate with each other.

If an input data set contains data from several subsystems, at least one of the following identifiers has to be different if OMEGAMON XE for DB2 PE is to distinguish between different subsystems: group name, location name, member name, or subsystem ID.

MAINPACK (Main package)

This identifier can be used to distinguish between plans according to the packages they contain. The representative package is either the first or last package or DBRM in a plan.

This identifier is useful when the name of a plan does not provide satisfactory identification.

The MAINPACK definition is stored in the DPMPARMS member MAINPACK. You can get access to the member by using the MAINPACK Definition Editor panel of the IRF. A different MAINPACK definition can be specified for each unique combination of requester location, connection ID, and plan name.

The default value for MAINPACK is the package ID of the first executed package for any requester location, connection ID, and plan name. If there is no package data available, MAINPACK returns to the default plan name.

MEMBER (Member name)

The name of the data-sharing group member.

OBJECT (Object type)

The type of DB2 resource. Valid values are:

BUFFER

Buffer pool

COLLECT

Collection

DATABASE

Database

DISTTYPE

Distribution type

FUNCTION

Function

PACKAGE

Package

SCHEMA

Schema

APPLPLAN

Application plan

LOBTS

LOB table space

STOGROUP

Storage group

TAB/VIEW

Table or view

USERAUTH

For system privileges like SYSADM or SYSOPR

ORIGAUTH (Original authorization ID)

The original value of the primary authorization ID at the time of connection to DB2 and before it can be changed by any authorization exits.

In distributed processing and if the requester is a DB2 system, the value of the original authorization ID at the application server is the same as the value assigned to the application requester. If the application requester is not a DB2 system, the value of the original authorization ID at the application server is the user ID used during the initial connection with the application server.

PACKAGE (Package information)

This identifier is used to identify a package or DBRM. It is displayed in traces and reports in the headings of corresponding package data blocks.

PAGESET (Page set name)

The name of the page set.

Note that INCLUDE and EXCLUDE processing uses the character names of page sets, while DB2 instrumentation records contain the decimal IDs used by DB2. OMEGAMON XE for DB2 PE translates the decimal ID to the character name.

PARTNBR (Partition number)

PARTNBR identifies a partition of a table space by its number.

Table spaces can be partitioned or non-partitioned. The value for this identifier is zero if the table is not partitioned. This identifier is only valid for the ORDER command used with IOACTIVITY. You must specify PAGESET before you can specify PARTNBR.

PLANNAME (Plan name)

The plan name from the correlation header. A plan is a control structure produced during the bind process and used by DB2 to process SQL statements encountered during statement execution.

To receive better identification and granulation of bind and utility traces and reports, it is necessary to filter and order data. The plan name on a bind event (constant DSNBIND) is replaced by the program name, and the plan name on a utility event (constant DSNUTIL) is replaced by the utility name.

PRIMAUTH (Primary authorization ID) or AUTHID (Authorization ID)

The two terms are interchangeable. This is the primary authorization ID you entered at signon or identify.

REQLOC (Requester location)

For distributed processing, this is the location requesting the work. If the requester location is not a DB2 subsystem, or is not recognized by DB2, the logical unit name from the DRDA LUWID is printed instead of the requester location name. The logical unit name is enclosed in less than (<) and greater than (>) symbols.

For TCP/IP connections, the requester location can contain the dotted-decimal IP address.

RESOURCETYPE (Resource type)

The type of lock resource. You can specify one of the following values:

DATAPAGE

Data page locking

DATABASE

Locking of the DBD

PAGESET

Page set locking

DATASET

Locking of partitioned data sets

SKCT

Skeleton cursor table locking

INDEX

Index page locking

TABLE

Table locking

SKPT

Skeleton package table locking

COLLECT

Collection ID locking

DRAIN

All types of drain locking

ROW

Data row lock

OTHER

All unlisted resource types

RMID (Resource manager identifier)

The decimal identifier of a DB2 resource manager. You can use RMID to select a particular type of activity. For example, RMID 6 selects records associated with storage management.

SQLCODE

The SQL return code. This identifier is only valid with the SQLACTIVITY TRACE or SQLACTIVITY FILE commands. It can be used to include statements that completed, for example, with a specific error.

See INCLUDE and EXCLUDE subcommand options for syntax details, and SQLACTIVITY command with TRACE subcommand for examples using this filter.

SUBSYSTEMID (Subsystem ID)

The ID of the DB2 subsystem that generated the data.

THREADTYPE (Thread type)

The type of thread that you want included in a report. You can specify one or more of the following values:

ALLIED

Threads without distributed activity. An allied thread does not involve distributed activity, that is, it is not initiated by a remote location and does not request data from another location.

ALLIED_DIST

Threads that request work from remote locations. An allied-distributed thread is not initiated by a remote location, but it requests data from one or more server locations.

DBAT

Threads performed on behalf of remote locations.

TRANSACT (End user transaction name)

The transaction or application that the client is running.

TYPE (Event type)

Specifies which event types are to be included in, or excluded from, the lock detail trace. Valid event type values are:

IRLMREQ

Lock, unlock, change, query, and notify requests

CLAIMREQ

Claim acquire, claim change, and claim release

DRAINREQ

Drain request and drain release

PLOCKREQ

Page set or partition and page P-lock requests

IRLMSUSP

The beginning of lock, unlock, change, query, and notify suspensions

DRAINSUSP

The beginning of drain suspensions

LATCHSUSP

The beginning of page latch suspensions

IRLMRES

The end (resumption) of lock, unlock, change, query, and notify suspensions

DRAINRES

The end (resumption) of drain suspensions

LATCHRES

The end (resumption) of page latch suspensions

TIMEOUT

Timeouts

DEADLOCK

Deadlocks

LOCKSUMMARY

Lock summary events

LOCKAVOID

Successful lock avoidance events

The default is all event types.

Note:

TYPE can also be used with the REDUCE and FILE subcommands of LOCKING, with the following limitations:

• Valid types for REDUCE are: IRLMRES, DRAINRES, and LATCHRES.
• Valid types for FILE are: IRLMREQ, CLAIMREQ, DRAINREQ, and LOCKAVOID.

If values other than those listed are used with INCLUDE, REDUCE, or FILE, an empty report or file is produced.

If values not relevant to REDUCE or FILE are used with EXCLUDE, the event type is not filtered.

WSNAME (End user workstation name)

The user's workstation name.