Event trace (SYSTCPIP) for TCP/IP stacks and Telnet
The TN3270E Telnet server running as its own procedure also uses the SYSTCPIP event trace.
Restrictions: All discussion that follows where TCP/IP is used as an
example also pertains to the TN3270E Telnet server with the following
exceptions:
- The TN3270E Telnet server does not use 64-bit common storage for trace collection, it uses its own private storage.
- A subset of trace commands are used by Telnet. A default parmlib member, CTIEZBTN, is provided that indicates all trace options available. The default parmlib member can be overridden in the same manner as the TCP/IP parmlib can be overridden.
- A subset of IPCS commands are used by Telnet.
Event trace for TCP/IP stacks traces individual TCP/IP components (such as STORAGE, INTERNET, and so forth) and writes the information either to a data set (using an external writer), or internally to 64-bit common storage. To aid in first failure data capture, a minimal component trace is always started during TCP/IP initialization if you use the TCP/IP Component Trace SYS1.PARMLIB member, CTIEZBxx.You can select trace records at run time by any of the following methods:
- JOBNAME
- Address space identifiers (ASID)
- Trace option
- IP address
- Port number
- Event identifier
Restriction: If using the TELNET
options, do not specify the JOBNAME parm when starting CTRACE.