IFCID 003 - Initial Client/Server Correlation Data

This topic shows detailed information about Record Trace - IFCID 003 - Initial Client/Server Correlation Data.

This topic also shows detailed information about Initial Other Requester Correlation Data.

                                  INITIAL CLIENT/SERVER CORRELATION DATA
BYTES: 255                    PRODUCT ID: COMMON SERV                                 PRODUCT VERSION: V10R05M0
CLIENT PLATFORM: NT 64BIT             CLIENT APPLICATION NAME: IS-255-0123456789012   CLIENT AUTHID : IS-128--
DDCS ACCOUNT SUFFIX: IS-255-012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789
                     012345678901234567890123456789IS-128--01234567890123456789012345678901234567890123456789012345678
                     901234567890123456789012345678901234567890123456789012345-END

BYTES

The length of the product ID and accounting string.

For DDF/RRSAF rollup records, the field will contain a value derived from the last thread to rollup.

Field Name: QMDAASLN

PRODUCT ID

Shows the product identifier (ID) of the requester. It can have the following values:

DB2

For DB2 UDB for z/OS®

SQL/DS

For DB2® UDB for VSE and VM

JDBC DRIVER

For Universal JDBC driver

COMMON SERV

For DB2 UDB for Linux®, UNIX, Windows

DB2/400

For DB2 UDB for iSeries

Otherwise, it shows the first 3 characters of the product ID, or N/P if the record was written at the application requester location.

For DDF/RRSAF rollup records, the field will contain a value derived from the last thread to rollup.

Field Name: QMDAPRID

PRODUCT VERSION

The version, release, and modification level of the product, which generated the accounting information. It has the following format: vv rr m, where:

vv

Version level

rr

Release level

m

Modification level

N/P is shown if the record was written at the application requester location.

For DDF/RRSAF rollup records, the field will contain a value derived from the last thread to rollup.

Field Name: QMDAPMOD

CLIENT PLATFORM

The client platform, such as AIX®. This is a 1 to 18 character field padded with blanks.

For DDF/RRSAF rollup records, the field will contain a value derived from the last thread to rollup.

Field Name: QMDAPLAT

CLIENT APPLICATION NAME

The name of the client application. This is a 1 to 20 character field padded with blanks. An example is "PAYROLL".

For DDF/RRSAF rollup records, the field will contain a value derived from the last thread to rollup.

Field Name: QMDAAPPL

CLIENT AUTHID

The client authorization ID of an application process. This is a 1 to 8 character field padded with blanks. An example is "SMITH".

For DDF/RRSAF rollup records, the field will contain a value derived from the last thread to rollup.

Field Name: QMDAATID

DDCS ACCOUNT SUFFIX

The account suffix. The maximum length of this field is 200 bytes. This field is the user-supplied portion (suffix) of the accounting string. An example is "DEFAULT_DRDA". A value of zero in QMDASFLN Indicates there is no account suffix.

For DDF/RRSAF rollup records, the field will contain a value derived from the last thread to rollup.

Field Name: QMDASUFX

ACCOUNTING STRING

The accounting string:

• For local DB2 threads, the format of the accounting string is shown in QMDAINFO.
• For database access threads, the accounting string contains the accounting string sent by the requester.
• The QMDAPRID value identifies which product generated the accounting string.
  • If the requester is DB2, the accounting string is defined in QMDAINFO.
  • If QMDAPTYP is DSN, QMDAINFO defines the format.
  • If QMDAPTYP is SQL or JCC, QMDASQLI defines the format.
  • Otherwise, the format is undefined.

For DDF/RRSAF rollup records, the field will contain a value derived from the last thread to rollup.

Field Name: QMDAASTR