Troubleshooting
Problem
This document provides information about how to take and collect an HTTP server trace running a CGI application.
Resolving The Problem
An HTTP trace traces all server jobs; however, it does not always dump all of them. In order to collect this part of the trace when a CGI application fails, you should do the following:
1. | Identify the CGI job: a. WRKACTJOB JOB(servername) b. Look for the job with PGM-QZSRCGI in the FUNCTION column. c. Take Option 5 on this job and record the job name/user/number for the commands below as indicated. Note: Record the name/user/number for all jobs with PGM-QZSRCGI in the FUNCTION column in case there is more than one, and if you do not know which job will be used. |
2. | Start the trace by issuing the following command: TRCTCPAPP APP(*HTTP) HTTPSVR(servername) TRCLVL(*VERBOSE) |
3. | Re-create the error, and issue the following two commands in this sequence: DMPUSRTRC JOB(number/user/name) (Repeat this command for all remaining CGI jobs recorded above) TRCTCPAPP APP(*HTTP) SET(*OFF) |
4. | Save the joblog: DSPJOBLOG JOB(number/user/name) OUTPUT(*PRINT) |
5. | Create a save file to save the CGI trace output by issuing the following command: CRTSAVF yourlib/yoursavf |
6. | Save the output of the CGI trace by issuing the following command: SAVOBJ OBJ(QAP0ZDMP) LIB(QTEMP) DEV(*SAVF) SAVF(yourlib/yoursavf) |
7. | Save the spooled file from the trctcpapp *off command. Use Navigator to drag and drop to PC; the name is QZSRHTTPTR. Do the same with the spooled file QPJOBLOG |
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]
Historical Number
564949706
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1012184
Manage My Notification Subscriptions