Starting a service job to diagnose application server problems

 

When an application uses Distributed Relational Database Architecture™ (DRDA^®), the SQL statements are run in the application server job. Because of this, you might need to start debug or a job trace for the application server job that is running on the i5/OS^® operating system. The technique for doing this differs based on the use of either Advanced Program-to-Program Communication (APPC) or TCP/IP.

• Service jobs for APPC servers
  When the DB2 Universal Database™ for iSeries™ application server recognizes a special transaction program name (TPN), it causes the application server to send a message to the system operator and then wait for a reply.

• Creating your own transaction program name and setting QCNTSRVC
  To create your own transaction program name (TPN) and set QCNTSRVC, do the following tasks.

• Service jobs for TCP/IP servers
  The DDM TCP/IP server does not use transaction program names (TPNs) as the Advanced Program-to-Program Communication (APPC) server does. However, the use of prestart jobs by the TCP/IP server provides a way to start a service job in that environment.

• QRWOPTIONS data area
  When DDM or DRDA TCP/IP server jobs are initiated, they look for a data area in which the user can specify diagnostic and other options. The name is QRWOPTIONS, and it must reside in the QGPL library to take effect. It consists of a string of 48 characters.

 

Parent topic:

Troubleshooting

 

Related concepts

Job tracing