Troubleshooting
Problem
This document contains instructions for collecting a TCP/IP communications trace using the Start Communications Trace (STRCMNTRC) command.
Symptom
Note: When experiencing problems with TCP/IP printers, it is highly recommended to discuss the problem with a support representative before collecting a TCP/IP communications trace. The problem might be a known issue that can easily be resolved through configuration changes, printer hardware settings, or Program Temporary Fixes (PTFs). In these cases, a TCP/IP communications trace may not be required.
Diagnosing The Problem
These instructions can be used for collecting trace for an ASCII printer (such as a *LAN 3812 device description, Remote Output Queue, PC5250 printer session or third-party emulation session) or a *LAN IPDS device description. However, a TCP/IP communications trace can also be taken using the Trace Connection (TRCCNN) command or the Start Communications Trace (STRCMNTRC) command.
STRCMNTRC contains the MAC address of the hardware that is involved in the connection and can be helpful to determine which hardware is resetting a connection or answering. But most of the time a TRCCNN is enough.
For instructions on collecting a TCP/IP communications trace using the Trace Connection (TRCCNN) command, refer to the following document:
Running a TRCCNN Trace for LAN Printing Problems
Regarding Gigabit or 1Gbps Ethernet Adapters
When attempting to trace TCP traffic through a Gigabit or 1Gbps Ethernet adapter (for example the FC2760, FC2843, FC5700 or FC5701 adapters), the Communications Trace (STRCMNTRC) utility might fail to capture adequate data due to the high rate of speed at which the interface transmits and receives data, coupled with the slow rate of speed at which the system collects trace data. An alternative for this situation is to use the Trace Connection (TRCCNN) command, which will capture all transmitted and received data on the Gigabit Ethernet line.
STRCMNTRC contains the MAC address of the hardware that is involved in the connection and can be helpful to determine which hardware is resetting a connection or answering. But most of the time a TRCCNN is enough.
For instructions on collecting a TCP/IP communications trace using the Trace Connection (TRCCNN) command, refer to the following document:
Running a TRCCNN Trace for LAN Printing Problems
Regarding Gigabit or 1Gbps Ethernet Adapters
When attempting to trace TCP traffic through a Gigabit or 1Gbps Ethernet adapter (for example the FC2760, FC2843, FC5700 or FC5701 adapters), the Communications Trace (STRCMNTRC) utility might fail to capture adequate data due to the high rate of speed at which the interface transmits and receives data, coupled with the slow rate of speed at which the system collects trace data. An alternative for this situation is to use the Trace Connection (TRCCNN) command, which will capture all transmitted and received data on the Gigabit Ethernet line.
Resolving The Problem
Instructions for Collecting a TCP/IP Communications Trace Using the STRCMNTRC Command
| 1. |
Use the following Work with Line Descriptions (WRKLIND) command to verify the name of your Ethernet and/or token-ring line description(s).
To work with Ethernet line descriptions, use the following command: WRKLIND LIND(*ELAN) To work with token-ring line descriptions, use the following command: WRKLIND LIND(*TRLAN) Both commands should be used because Ethernet and token-ring lines can be configured and active at the same time. Select Option 8 (Work with status) to determine if each line is active. It is recommended that a TCP/IP communications trace be configured for each active line even if both Ethernet and token-ring lines are active. This is because TCP/IP data frames could be sent on one line and received on another and can sent on Ethernet and received on token-ring, or vice-versa. |
| 2. |
Use the following Check Communications Trace (CHKCMNTRC) command to see if there is already a trace on the line:
CHKCMNTRC CFGOBJ(line-description-name) CFGTYPE(*LIN) Message CPF39A5 - Communications trace &1 type &2 has status &3 indicates if the trace is in STARTING, ACTIVE, WAITING, ENDING, ENDED, or ERROR status. If the trace is in ENDING status, wait for a minute or two. Then, repeat the CHGCMNTRC command above. If the trace is in ERROR status, use the End Communications Trace (ENDCMNTRC) and Delete Communications Trace (DLTCMNTRC) commands, listed in Steps 5 and 8. Then, repeat the CHKCMNTRC command above to check for a communications trace again. If the trace is in STARTING, ACTIVE or WAITING or ERROR status, determine if the existing trace is still required. If not, use the End Communications Trace (ENDCMNTRC) and Delete Communications Trace (DLTCMNTRC) commands, listed in Steps 5 and 8. Then, repeat the CHKCMNTRC command above to check for a communications trace again. After the trace is in ENDED status, proceed to the next step. |
| 3. |
Start the communications trace by using one of the following options:
|
| 4. |
The communications trace should be active at this time. Reproduce the problem.
|
| 5. |
After the problem has been reproduced, use the following to end the communications trace:
ENDCMNTRC CFGOBJ(linename) CFGTYPE(*LIN) |
| 6. |
After the trace has ended, use one of the following to print the communications trace:
PRTCMNTRC CFGOBJ(linename) CFGTYPE(*LIN) CODE(*ASCII) SLTCTLD(*ALL) FMTTCP(*YES) TCPIPADR('1.2.3.4') FMTBCD(*NO) Note: If a Remote Output Queue, a *LAN 3812 device description, or a printer emulation session (such as PC5250) is being traced, set the Character code (CODE) parameter to *ASCII. If a *LAN IPDS device description is being traced, set the Character code (CODE) parameter to *EBCDIC. If unsure whether to use *ASCII or *EBCDIC, consult with support representative before continuing. |
| 7. |
The resulting QPCSMPRT spooled file can be found by using the Work with Job (WRKJOB) command and taking Option 4 (Work with spooled files) or by using the following WRKJOB command with the Option (OPTION) parameter set to *SPLF:
WRKJOB JOB(*) OPTION(*SPLF) After the QPCSMPRT spooled file has been found, it can be printed, faxed through Facsimile Support/400 (FAX/400), or converted to PDF format and e-mailed through IBM Infoprint Server. The resulting QPCSMPRT spooled file can be found within Access Client Solution (ACS) or Navigator for i. For more information, refer to the following document: How to download spool files - Small, Medium, Large - and in the correct ASCII format |
| 8. |
It is recommended that the communications trace be left on the system just in case must print the trace again using different options. When the trace is no longer required, use the following command to delete the trace:
DLTCMNTRC CFGOBJ(linename) CFGTYPE(*LIN) |
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CP4AAM","label":"Print-\u003EPrinter Configurations-\u003ETrace"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
10 January 2025
UID
nas8N1019324