Solve communication problems using communications trace

Sometimes, program debugging tasks are easier if you can trace the data that is sent and received on the communications line or within the network server. To perform a communications trace, you must have IBM® *SERVICE special authority or be authorized to the Service Trace function of i5/OS™ through iSeries™ Navigator. See iSeries Security Reference (SC41-5302), Chapter 4 User Profiles, for more information on this special authority.

To run a communications trace, see Perform a communications trace for the specific steps you should use.

The following commands might be used to perform a communications trace.

STRSST (Start Service Tools)

The STRSST command takes you to a menu of tools to obtain error log information and communications trace information. For a detailed description of system service tools, see: Communications trace and communication problems

STRCMNTRC (Start Communications Trace)

The STRCMNTRC command starts a communications trace for the specified line, network interface description, or network server description. The communications trace continues until one of the following occurs:

• The system runs the End Communications Trace (ENDCMNTRC) command
• A physical line problem causes the trace to end
• The Communications Trace function of the STRSST command ends the trace
• The *STOPTRC parameter is specified, and the buffer becomes full

ENDCMNTRC (End Communications Trace)

The ENDCMNTRC command ends the trace currently running on the specified line, network interface description, or network server description. The ENDCMNTRC command saves the communications trace buffer and the associated System Licensed Internal Code (SLIC) data.

PRTCMNTRC (Print Communications Trace)

The PRTCMNTRC command writes the communications trace data for the specified line, network interface description, or network server description to a spooled file or a database file. The system can print trace data multiple times in either form, and parameters on the command allow for dividing and formatting of the data.

DLTCMNTRC (Delete Communications Trace)

The DLTCMNTRC command deletes the communications trace buffer and associated SLIC data for the specified line, network interface description, or network server description. The communications trace can be deleted once the trace has ended.

CHKCMNTRC (Check Communications Trace)

The CHKCMNTRC command returns the communications trace status for a specific line, network interface description, or network server description. The CHKCMNTRC command returns status for all of the traces of a specific type that exist on the system. The system returns the status through a message.

TRCCPIC (Trace Common Programming Interface (CPI) Communications)

You can start to trace Common Programming Interface (CPI) Communications either before running a job or after a job is active to find out where the error might have occurred. The TRCCPIC command captures information about CPI-Communications calls that is processed by your program.

For more information on how to access System Service Tools, see the Backup and Recovery book.