Troubleshooting
Problem
This document contains a list of objects that are created by the diagnostic tools built in to the database client/server interfaces.
Resolving The Problem
The following data providers feature a diagnostic property to enable server-side diagnostics such as a database monitor and job trace:
- IBM i Access Client Solutions Windows Application Package (ACS-WinAP) ODBC driver
- IBM Toolbox for Java JDBC driver
- IBM Developer Kit for Java JDBC driver(starting at V5R2)
- IBM i .Net provider
- IBM i OLE DB provider
Following is a list of trace objects that can be generated and their naming convention. The name of the trace object starts with a 3- or 4-letter prefix that is unique for each client. This name is followed by a 6-digit number that represents the job number of the job being traced.
The object type of *FILE with text Output file for STRDBMON is created when the database monitor is enabled. It is not deleted automatically when the job ends.
The objects of type *MGTCOL and *USRSPC are related to the job trace command (STRTRC). The STRTRC command uses a PEX trace to collect the job trace information. These objects contain the unformatted trace data. They are normally deleted when the job ends. If the job ends abnormally, the traces might not be ended.
If there is a steady increase in these object types, it is likely the trace is enabled in a program or data source. To locate the user that left tracing enabled use the DSPOBJD command. The user that created the object is the user profile used to make the ODBC or JDBC connection. If necessary, an administrator can revoke this users authority to the appropriate commands (STRTRC or STRDBMON).
For more information, see
Tracing IBM i Access for Windows ODBC Jobs
The All-In-One Toolbox Tracing Guide
WRKOBJ output:
Object Type Library Attribute Text
/* iSeries Access for Windows ODBC datasource diagnostics tab */
QODB134371 *FILE QUSRSYS PF Output file for STRDBMON
QDPC134371 *MGTCOL QUSRSYS *PEX PEX data
QDPC134371 *USRSPC QUSRSYS PF PEX SESSION OBJECT
/* IBM Toolbox for Java JDBC driver "server trace" property */
QJT133819 *FILE QUSRSYS PF Output file for STRDBMON
QJT133819 *MGTCOL QUSRSYS *PEX PEX data
QJT133819 *USRSPC QUSRSYS PF PEX SESSION OBJECT
/* IBM Developer Kit for Java JDBC driver "server trace" property */
QSQL133645 *FILE QUSRSYS PF Output file for STRDBMON
QSQL133645 *MGTCOL QUSRSYS *PEX PEX data
QSQL133645 *USRSPC QUSRSYS PF PEX SESSION OBJECT
/* Any user trace (CLI trace, java UDF/Procedure trace, etc */
QP0Z096353 *USRSPC QUSRSYS 096353/V2KEA84/QP0ZSYSC
/* iSeries Access for Windows .Net data provider Trace connection property */
QNET123456 *FILE QUSRSYS PF Output file for STRDBMON
QNET123456 *MGTCOL QUSRSYS *PEX PEX data
QNET123456 *USRSPC QUSRSYS PF PEX SESSION OBJECT
/* iSeries Access for Windows OLEDB Trace property */
QODB123456 *FILE QUSRSYS PF Output file for STRDBMON
QODB123456 *MGTCOL QUSRSYS *PEX PEX data
QODB123456 *USRSPC QUSRSYS PF PEX SESSION OBJECT
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"Host Servers","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]
Historical Number
314220195
Was this topic helpful?
Document Information
Modified date:
29 June 2021
UID
nas8N1019272