Getting data to report a failure

 

The i5/OS^® licensed program provides data that you can print to help you diagnose a problem in a distributed relational database.

You can also use system operator messages and the application program (along with its data) to diagnose problems.

• Printing a job log
  Every i5/OS job has a job log that contains information related to requests entered for that job. When a user is having a problem at an application requester (AR), the information in the job log might be helpful in diagnosing the problem.

• Finding job logs from TCP/IP server prestart jobs
  When the connection ends that is serviced by one of the QRWTSRVR prestart jobs associated with the distributed data management (DDM) TCP/IP server, the prestart job is recycled for use by another connection. When this happens, the job log associated with the ended connection is cleared.

• Printing the product activity log
  The i5/OS product activity log is a record of machine checks, device errors, and tape statistics. It also contains first-failure data capture (FFDC) information including the first 1000 bytes of each FFDC dump. By reviewing these errors, you might be able to determine the nature of a problem.

• Job tracing
  Sometimes a problem cannot be tracked to a specific program. In these cases, Start Trace (STRTRC) and Trace Job (TRCJOB) commands can be used for tracing module flow, i5/OS data acquisition and CL commands executed.

• Communications trace
  If you get a message in the CPF3Exx range or the CPF91xx range when using Distributed Relational Database Architecture™ (DRDA^®) to access a distributed relational database, you should run a communications trace.

• TCP/IP communications trace
  One of the uses of the trace tool is to show the clear text of a transmission in an environment where the data is encrypted.

 

Parent topic:

Troubleshooting