Implementing Siebel Business Applications on DB2 UDB for z/OS > Maintenance Considerations for z/OS >

Tracing the Source of a Query


Administrators can identify the terminals from which queries are generated using the Session ID.

The session ID is composed of three parts: ClientIP_ClientProcessID_SerialNumber. The following is an example of a session ID:

172.20.80.25_324_1.

Eventually, the Object Manager and the DB2 host share the same string which can be used to identify the current connection.

After the session ID is displayed at the Server Manager, you can also check it on the database side.

To verify session ID on the DB2 host

  1. At the Option prompt, enter the location of the DB2 Primary Option Menu.

    The DB2 Primary Option Menu appears.

  2. At the Command prompt, enter D to access the DB2 Defaults Panel.
  3. At the Command prompt, enter the name of the subsystem that you are connecting to.
  4. Press F3 to go back to the DB2 Primary Option Menu.
  5. At the Command prompt, enter the appropriate selection to go to the DB2 Command window.
  6. At the DB2 Command window, enter the following:

    -DISPLAY THREAD(*) DETAIL

    NOTE:  The "-" is required.

  7. Press Enter to display current active threads.

    The session ID string is displayed in the application name field. If there are many active threads shown, identify your thread by matching the corresponding host name and userid.

Implementing Siebel Business Applications on DB2 UDB for z/OS Copyright © 2008, Oracle. All rights reserved.