|Product:||DBConnectivity Products for IBM Db2 for i (HiT ODBC/400, HiT OLEDB/400, Ritmo/i, HiT JDBC/400)|
|Summary:||IBM Db2 for i job log can be useful for diagnosing errors|
When a HiT data connector for IBM Db2 for i accesses the database server (ODBS), any processes are represented by specific jobs: TCP connections are identified by QZDASOINIT jobs.
Sometimes, when there’s a problem, the error description reported by IBM Db2 for i and the database server is not clear. The job log can provide additional information by indicating which job is responsible for the issue.
The easiest way to access the job log is to specify the user profile:
On an IBM i console, run:
WRKOBJLCK OBJ(my_usr_prf) OBJTYPE(*USRPRF)
Find the associated QZDASOINIT /QZDAINIT job, then options 5, 10, F10, F18, F1=Help on eventual errors.
In many cases, when the client application is disconnected, the job gets closed and the job log is lost. The best option is to launch the application causing the error and, once it appears, access the job log as described above before closing the connection.