z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


I/O trace operation

z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures
GC27-3667-00

Before starting the I/O trace, make sure that the GTF with the TRACE=USR option is active. See Starting the generalized trace facility (GTF).

Start the I/O trace with the MODIFY TRACE command or the TRACE start option.

Specify: To trace:
ID=nodename Requests and responses flowing between VTAM® and nodename.
ID=VTAM Request and response units (RUs) for SSCP sessions.
ID=ISTPUS Request and response units (RUs) for sessions between the host physical unit and another physical unit type 4 or 5 (these RUs include ER-ACT, ER-OP, and ER-TEST RUs).
ID=ISTIRN Request and response units (RUs) that flow through this host while this host is acting as an intermediate routing node.
Notes:
  1. If you use the SCOPE=ALL or EVERY operand when you start the trace, the trace contains I/O activity for the specified node and all its valid subnodes. You must specify SCOPE=ALL when tracing a channel-attachment major node or when tracing an APPN PU. You cannot use the SCOPE=ALL or EVERY operands with ID=ISTPUS or ID=ISTIRN.
  2. You may trace a link in a channel-attachment major node but not a link station.

See z/OS Communications Server: SNA Operation for information on the MODIFY command. See z/OS Communications Server: SNA Resource Definition Reference for more information on the TRACE start option.

Parent topic: I/O trace

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014