/TRACE LUNAME command

Use the /TRACE LUNAME command to activate and deactivate tracing for a particular LU name or TP name of the LU name.

Environment

The following table lists the environments (DB/DC, DBCTL, and DCCTL) in which you can use the commands and keywords.

Table 1. Valid environments for the /TRACE LUNAME command and keywords
Command / Keywords DB/DC DBCTL DCCTL
/TRACE X X X
INPUT X   X
LUNAME X   X
OUTPUT X   X
SET X X X

Syntax

Read syntax diagramSkip visual syntax diagram
                    .-ON--.   
>>-+-/TRACE-+--SET--+-----+------------------------------------->
   '-/TRA---'       '-OFF-'   

               .--------.                   
               V        |                   
>--LUNAME--+-+---luname-+-+--+-INPUT--+-+----------------------><
           | '-ALL--------'  '-OUTPUT-' |   
           |                 .--------. |   
           |                 V        | |   
           '-luname--TPNAME----tpname-+-'   

Usage notes

Specifying this command causes trace entries to be written to the LUMI trace table. For this reason, the /TRACE SET ON TABLE LUMI command must be entered first in order to create the table for trace entries that will be created by subsequent /TRACE SET ON LUNAME commands. A trace entry is written:

  • On LU 6.2 module entries/exits
  • When APPC calls are made
  • When errors are encountered

The INPUT and OUTPUT keywords provide the operator with the flexibility to control the volume of trace data for LU 6.2 devices.

Specifying the keyword INPUT with the LUNAME keyword indicates tracing is activated or deactivated for input and synchronous outbound activities. Specifying the parameter ALL with the INPUT keyword causes all future LU 6.2 input and synchronous outbound activities to be traced as well.

Specifying the keyword OUTPUT with the LUNAME keyword indicates tracing is activated or deactivated for asynchronous outbound activities. Specifying the parameter ALL with OUTPUT causes all future LU 6.2 asynchronous outbound activities to be traced as well.

Specifying neither INPUT or OUTPUT is the same as both INPUT and Tracing is activated or deactivated for input and both synchronous and asynchronous outbound activities. Specifying the parameter ALL in this case causes all future LU 6.2 inbound activities, synchronous and asynchronous outbound activities to be traced as well.

The network-qualified LU name is optional for the LUNAME keyword. If the LU name is not a network-qualified LU name and no TP name is specified, tracing is activated or deactivated for all the network-qualified LU names in the system whose LU name matches the LU name specified.

If the specified resource does not exist and tracing is activated, a structure is created to retain the status.