Client Special Registers are Special
IBM i / Article / Systems management / i Can blog
Client special registers are very useful for understanding who requested work for database server jobs (QZDASOINIT, QSQSRVR, and QRWTSRVR).

By Dawn May
02/12/2019There are five possible values:
- Client application name
This is the name of the application that is issuing the SQL request. - Client program ID
This is the name of the program that issues the SQL statement. - Client accounting
This is the accounting information for the SQL request. For example, this could be the accounting code associated with the requesting user profile. - Client user ID
This is the user name. For example, this could be the user name of the client that originated the request. - Client workstation name
This could be the actual name of a workstation (PC) where a request came from, or it could be a job name. This is one way to pass the requesting job name to the database server job to link the two jobs together.
- SYSPROC.WLM_SET_CLIENT_INFO stored procedure.
Call this SQL procedure prior to execution of your SQL statements. - Set Client Information (SQLESETI) API
- SQL Call Level Interface (SQL CLI) - SQLSetConnectAttr()
- ODBC - SQLSetConnectAttr()
- JDBC - setClientInfo() connection method
- QSYS2.ACTIVE_JOB_INFO() with DETAILED_INFO => ‘ALL’
- QSYS2.GET_JOB_INFO()
- Retrieve Job Information (QUSRJOBI) API
- SQL Performance Center
- SQL Plan Cache Snapshots, SQL Statements
- SQL Plan Cache, SQL Details for Jobs
IBM i / Article / Community / Systems management / Application development / Db2 for IBM i / i Can blog
Dawn May is an IBM i consultant. She owns Dawn May Consulting, LLC in the Greater Boston area. Dawn is a former IBM senior technical staff member.