Communications Trace for TCP/IP Printers Using the STRCMNTRC Command

Resolving The Problem

Caution: When experiencing problems with TCP/IP printers, it is highly recommended to discuss the problem with a representative of the Rochester Support Center 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.

This document contains instructions for collecting a TCP/IP communications trace using the Start Communications Trace (STRCMNTRC) command. 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.

For instructions on collecting a TCP/IP communications trace using the Trace Connection (TRCCNN) command, rather than using the STRSST command, refer to the following Rochester Support Center knowledgebase document:

N1019135: Running a TRCCNN Trace for LAN Printing Problems

For instructions on collecting a TCP/IP communications trace using the Start System Service Tools (STRSST) command rather than using the STRCMNTRC command, refer to the following Rochester Support Center knowledgebase document:

N1019324: Communications Trace for TCP/IP Printers Using the STRCMNTRC Command

After the TCP/IP communications trace has been collected, it can be downloaded to a PC and e-mailed to the Remote Technical Support representatives using the instructions in the following Rochester Support Center knowledgebase document:

N1019300: Copying the Text from a Spooled File Using System i Navigator

This document was last updated on 8 April 2014.

---

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.

For instructions on collecting a trace using the TRCCNN command, refer to the following Rochester Support Center knowledgebase document:

N1019135: Running a TRCCNN Trace for LAN Printing Problems


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: o To collect a TCP/IP communications trace for a particular TCP/IP address, use the following Start Communications Trace (STRCMNTRC) command to start the communications trace: STRCMNTRC CFGOBJ(line-description-name) CFGTYPE(*LIN) MAXSTG(8192)           USRDTA(*MAX) CMNTRCOPTS(*RMTIPADR) RMTIPADR('ip-address')           TEXT('Printer Trace') where the buffer size (MAXSTG parameter) is set to 8192 (8MB) or higher, the number of user bytes to trace (USRDTA parameter) is set to *MAX, the communications trace options (CMNTRCOPTS parameter) is set to *RMTIPADR, and the remote IP address (RMTIPADR parameter) is the TCP/IP address of the printer or print server. The following is an example of the STRCMNTRC command with the CMNTRCOPTS parameter set to *RMTIPADR:

Start Communications Trace (STRCMNTRC)  Type choices, press Enter.  Configuration object . . . . . . > ETHLINE       Name  Type . . . . . . . . . . . . . . > *LIN          *LIN, *NWI, *NWS  Buffer size  . . . . . . . . . . > 8192          Number, *MIN, *MAX, 128K...  Data direction . . . . . . . . .   *BOTH         *SND, *RCV, *BOTH  Trace full . . . . . . . . . . .   *WRAP         *WRAP, *STOPTRC  Number of user bytes to trace:    Beginning bytes  . . . . . . . > *MAX          Number, *CALC, *MAX    Ending bytes . . . . . . . . .                 Number, *CALC  Communications trace options . . > *RMTIPADR     *ALLDTA, *RMTCTL, *RMTMAC...  Remote IP address  . . . . . . . > '192.168.2.15'  Trace description  . . . . . . . > 'Printer Trace'                                                                          Bottom  F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display  F24=More keys

o

To collect a TCP/IP communications trace for all TCP/IP addresses at the same time, use the following Start Communications Trace (STRCMNTRC) command to start the communications trace: STRCMNTRC CFGOBJ(line-description-name) CFGTYPE(*LIN) MAXSTG(8192)           USRDTA(*MAX) CMNTRCOPTS(*ALLDTA) TEXT('Printer Trace') where the buffer size (MAXSTG parameter) is set to 8192 (8MB) or higher, the number of user bytes to trace (USRDTA parameter) is set to *MAX, and the communications trace options (CMNTRCOPTS parameter) is set to *ALLDTA. Note: This is most useful when diagnosing an intermittent problem where more than one printer could fail. Otherwise, it is better to trace a single TCP/IP address because it is less likely to wrap the data because the Buffer size (MAXSTG) parameter was not set high enough. The following is an example of the STRCMNTRC command with the CMNTRCOPTS parameter set to *ALLDTA:

Start Communications Trace (STRCMNTRC)  Type choices, press Enter.  Configuration object . . . . . . > ETHLINE       Name  Type . . . . . . . . . . . . . . > *LIN          *LIN, *NWI, *NWS  Buffer size  . . . . . . . . . . > 8192          Number, *MIN, *MAX, 128K...  Data direction . . . . . . . . .   *BOTH         *SND, *RCV, *BOTH  Trace full . . . . . . . . . . .   *WRAP         *WRAP, *STOPTRC  Number of user bytes to trace:    Beginning bytes  . . . . . . . > *MAX          Number, *CALC, *MAX    Ending bytes . . . . . . . . .                 Number, *CALC  Communications trace options . . > *RMTIPADR     *ALLDTA, *RMTCTL, *RMTMAC...  Trace description  . . . . . . . > 'Printer Trace'                                                                          Bottom  F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display  F24=More keys

4.	The communications trace should be active at this time. Reproduce the problem.
5.	After the problem has been reproduced, use the following End Communications Trace (ENDCMNTRC) command to end the communications trace: ENDCMNTRC CFGOBJ(line-description-name) CFGTYPE(*LIN)
6.	After the trace has ended, use one of the following Print Communications Trace (PRTCMNTRC) commands to print the communications trace. PRTCMNTRC CFGOBJ(line-description-name) CFGTYPE(*LIN)           CODE(*ASCII or *EBCDIC)           SLTCTLD(*ALL) FMTTCP(*YES) TCPIPADR(ip-address)           FMTBCD(*NO) where the character code (CODE parameter) is set to *ASCII or *EBCDIC, the Controller description (SLTCTLD parameter) is set to *ALL, the format TCP/IP data (FMTTCP parameter) is set to *YES, the format TCP/IP data by address (TCPIPADR parameter) is the TCP/IP address of the failing printer or print server, and the format broadcast data (FMTBCD parameter) is set to *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 your Rochester Support Center representative before continuing.
7.	Use one of the following options to find and send in the spooled file: o 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. o The resulting QPCSMPRT spooled file can be found within IBM iSeries Navigator by going into the Basic Operations > Printer Output container and bringing up the Printer Output - Include dialog box. Set the User to same user profile used to collect the trace (or to Current user if you were signed on with your own user profile), set the User-specified data to TRCCNN, set everything else to All, and then click on the OK button. After the QPCSMPRT spooled file has been found, it can be copied to the PC by dragging it to the Microsoft Windows Desktop or to a folder within Windows Explorer. Note: To bring up the Printer Output - Include dialog box when using R520 iSeries Access for Windows, select View > Customize this View > Include... on the iSeries Navigator menu bar or press the F11 key. To bring up the Printer Output - Include dialog box when using R510 Client Access Express for Windows, select Options > Include... on the Operations Navigator menu bar. For more information, refer to the following Rochester Support Center knowledgebase document: N1019300: Copying the Text from a Spooled File Using System i Navigator
8.	It is recommended that the communications trace be left on the system just in case the Rochester Support Center must print the trace again using different options. When the trace is no longer required, use the following Delete Communications Trace (DLTCMNTRC) command to delete the trace: DLTCMNTRC  CFGOBJ(line-description-name) CFGTYPE(*LIN)