IMS Version 9

/TRACE

Format

Read syntax diagramSkip visual syntax diagram/TRACE Command:  EXIT through PSB

                    .-ON--.
>>-+-/TRACE-+--SET--+-----+------------------------------------->
   '-/TRA---'       '-OFF-'

>--+-EXIT--+-ALL--+--DFSMSCE0------------------------------------+-><
   |       +-LRDI-+                                              |
   |       +-LRIN-+                                              |
   |       +-LRLT-+                                              |
   |       +-LRTR-+                                              |
   |       +-PRCH-+                                              |
   |       +-PRIS-+                                              |
   |       +-TR62-+                                              |
   |       +-TRBT-+                                              |
   |       +-TROT-+                                              |
   |       '-TRVT-'                                              |
   |         .-------.                                           |
   |         V       |                                           |
   +-LINE--+---line#-+-+--+--------------+--| A |----------------+
   |       '-ALL-------'  '-LEVEL--+-1-+-'                       |
   |                               +-2-+                         |
   |                               +-3-+                         |
   |                               '-4-'                         |
   |         .-------.                                           |
   |         V       |                                           |
   +-LINK--+---link#-+-+--+--------------+--| A |----------------+
   |       '-ALL-------'  '-LEVEL--+-1-+-'                       |
   |                               +-2-+                         |
   |                               +-3-+                         |
   |                               '-4-'                         |
   |             .--------.                                      |
   |             V        |                                      |
   +-LUNAME--+-+---luname-+-+--+-INPUT--+-+----------------------+
   |         | '-ALL--------'  '-OUTPUT-' |                      |
   |         |                 .--------. |                      |
   |         |                 V        | |                      |
   |         '-luname--TPNAME----tpname-+-'                      |
   +-MONITOR--| B |----------------------------------------------+
   +-MSCT--------------------------------------------------------+
   |           .---------------.                                 |
   |           V               |                                 |
   +-NODE--+-+---+-nodename--+-+-+----+--+--------------+--| A |-+
   |       | |   '-nodename*-'   |    |  '-LEVEL--+-1-+-'        |
   |       | '-ALL---------------'    |           +-2-+          |
   |       '-nodename--USER--username-'           +-3-+          |
   |                                              '-4-'          |
   +-OSAMGTF-----------------------------------------------------+
   +-PI--+------------------+--+--------------------+------------+
   |     |         .-LOG--. |  |         .-MEDIUM-. |            |
   |     '-OPTION--+------+-'  '-VOLUME--+--------+-'            |
   |               +-TIME-+              +-LOW----+              |
   |               '-ALL--'              '-HIGH---'              |
   |          .-------------.                                    |
   |          V             |                                    |
   +-PROGRAM----programname-+------------------------------------+
   |               .-NOCOMP-.                                    |
   '-PSB--psbname--+--------+------------------------------------'
                   '-COMP---'

A:

|--+-----------------+--+----------+----------------------------|
   '-MODULE--+-DDM-+-'  '-TAKEOVER-'
             +-MFS-+
             '-ALL-'

B:

     .-------------------------------------.
     V         .-ALL-------------------.   |
|--+---+-APDB--+-----------------------+-+-+-+------------------>
   |   |       | .-------------------. | |   |
   |   |       | V                   | | |   |
   |   |       '---+-dbname--------+-+-' |   |
   |   |           +-areaname------+     |   |
   |   |           '-partitionname-'     |   |
   |   +-APMQ----------------------------+   |
   |   +-LA------------------------------+   |
   |   '-SCHD----------------------------'   |
   '-ALL-------------------------------------'

>--+--------------------------------+--+--------------------+---|
   |           .----------------.   |  '-INTERVAL--#seconds-'
   |           V                |   |
   '-REGION--+---+-reg#-------+-+-+-'
             |   +-reg#-reg#--+   |
             |   '-regionname-'   |
             '---ALL--------------'

Read syntax diagramSkip visual syntax diagram/TRACE Command: TABLE through UNITYPE

                    .-ON--.
>>-+-/TRACE-+--SET--+-----+------------------------------------->
   '-/TRA---'       '-OFF-'

>--+-TABLE--+-ALL--+--+-------------------+--+--------------------+-+-><
   |        +-CSLT-+  |         .-NOLOG-. |  |         .-MEDIUM-. | |
   |        +-DISP-+  '-OPTION--+-------+-'  '-VOLUME--+--------+-' |
   |        +-DL/I-+            '-LOG---'              +-LOW----+   |
   |        +-DLOG-+                                   '-HIGH---'   |
   |        +-FAST-+                                                |
   |        +-FPTT-+                                                |
   |        +-IDC0-+                                                |
   |        +-LATC-+                                                |
   |        +-LOCK-+                                                |
   |        +-LRTT-+                                                |
   |        +-LUMI-+                                                |
   |        +-OCMD-+                                                |
   |        +-OTMT-+                                                |
   |        +-QMGR-+                                                |
   |        +-ORTT-+                                                |
   |        +-RETR-+                                                |
   |        +-RRST-+                                                |
   |        +-SCHD-+                                                |
   |        +-SQTT-+                                                |
   |        +-STRG-+                                                |
   |        '-SUBS-'                                                |
   +-TCO------------------------------------------------------------+
   |          .-00--------------.                                   |
   +-TIMEOUT--+-----------------+-----------------------------------+
   |          '-time#--+------+-'                                   |
   |                   +-MSG--+                                     |
   |                   '-AUTO-'                                     |
   +-TMEMBER--+-tmembername-+--+----------------------+-------------+
   |          '-ALL---------'  '-TPIPE--+-tpipename-+-'             |
   |                                    '-ALL-------'               |
   |              .----------.                                      |
   |              V          |                                      |
   +-TRANSACTION----tranname-+--------------------------------------+
   +-TRAP--+-1-+----------------------------------------------------+
   |       '-2-'                                                    |
   |          .-------------.                                       |
   |          V             |                                       |
   '-UNITYPE----unitypename-+--+--------------+---------------------'
                               '-LEVEL--+-1-+-'
                                        +-2-+
                                        +-3-+
                                        '-4-'

Environments and Keywords

Table 169 lists the environments (DB/DC, DBCTL, and DCCTL) from which the command and keywords can be issued.

Table 169. Valid Environments for the /TRACE Command and Keywords
Command / Keywords DB/DC DBCTL DCCTL
/TRACE X X X
AUTO X X
COMP X X
EXIT X X
INPUT X X
LEVEL X X
LINE X X
LINK X X
LUNAME X X
MODULE X X
MONITOR X X X
MSG X X
NOCOMP X X
NODE X X
OPTION X X X
OSAMGTF X X
OUTPUT X X
PI X X
PROGRAM X X X
PSB X X
SET X X X
TABLE X X X
TAKEOVER X X
TCO X X X
TIMEOUT X X
TMEMBER X X
TPIPE X X
TPNAME X X
TRANSACTION X X
TRAP X X
UNITYPE X X
USER X X
VOLUME X X X

Usage

/TRACE directs and controls the IMS capabilities for tracing internal IMS events. It also starts, stops, and defines the activity to be monitored by the IMS Monitor.

The information developed by the LINE, LINK, NODE, UNITYPE, TRANSACTION, PROGRAM, PSB, and TCO keywords is written on the IMS system log (type X'5F' for PSB, and type X'67' records for the other keywords mentioned.) PI (program isolation) and TABLE trace information is kept in storage or logged (type X'67' records), depending on specification of additional keywords. The MONITOR keyword provides no such output on the system log; it only controls the IMS Monitor. The monitor develops its own output data and writes it on a separate data set. For an explanation of the output reports provided by the monitor, refer to the IMS Version 9: Utilities Reference: System.

The status and options of the current IMS traces can be displayed with the /DISPLAY TRACE command.

DFSMSCE0
The TM and MSC Message Routing and Control user exit. When this keyword is used on the /TRACE EXIT command, the traces causes IMS to write type 6701-MSEA and 6701-MSEB log records to the log data set when the exit routine is called. A 6701-MSEA record is logged when the exit is called if the trace is active for the entry point. A 6701-MSEB record is logged when the exit returns to IMS. For more information on the user exit, see the IMS Version 9: Customization Guide. For information on printing and interpreting the trace records from the user exit, see the IMS Version 9: Diagnosis Guide and Reference.
EXIT
Identifies user exit tracing. When using the EXIT keyword, you must specify one of the following parameters to turn on or off:
ALL
The trace is turned on or off for all entry points.
LRDI
Calls the Link Receive Direct Routing exit entry point.
LRIN
Calls the Link Receive Intermediate exit entry point.
LRLT
Calls the Link Receive LTERM exit entry point.
LRTR
Calls the Link Receive Transaction exit entry point.
PRCH
Calls the Program Routing CHNG Call exit entry point.
PRIS
Calls the Program Routing ISRT Call exit entry point.
TR62
Calls the Terminal Routing LU62 exit entry point.
TRBT
Calls the Terminal Routing BTAM exit entry point.
TROT
Calls the Terminal Routing OTMA exit entry point.
TRVT
Calls the Terminal Routing VTAM exit entry point.
LEVEL
Expands the LINE, LINK, NODE, or UNITYPE trace functions. The LEVEL specification is for the entire IMS system and is changed only by reissuing /TRACE with different values or by restarting the IMS control region.

LEVEL indicates the extent of the control block trace information desired. The indicated control blocks are only traced at relevant times. All levels are inclusive of numerically lower levels. The following list displays the levels and their associated blocks.

Level
Blocks
1
CLB (DECB) or LLB(MSC)
CTB or LTB(MSC)
IOB (for BTAM lines) or IOSB (MSC for channel-to-channel links)
2
CNT or LNB(MSC)
CXB
CRB
CIB
CCB
PD stack
3
queue manager buffers
Input/output line buffers
LXB (for channel-to-channel links and processor storage to processor storage)
4
save area sets (IMS dispatching)

If the first /TRACE SET ON command does not specify LEVEL, a default of 4 will be used. Specifying LEVEL on subsequent commands will change the defaults.

LINE
Enter this keyword (and the associated parameters) to cause events related to the lines to be traced.
LINK
Enter this keyword (and the associated parameters) to cause events related to the logical links to be traced.
LUNAME TPNAME
Activates and deactivates tracing for a particular LU name or TP name of the LU name. 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:

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.

MODULE
Is used to expand the LINE, LINK, NODE, or UNITYPE trace functions. The MODULE specification is for the entire IMS system and is changed only by reissuing /TRACE with different values or by restarting the IMS control region.

MODULE indicates which modules are to have their control blocks traced.

ALL
Both DDM and MFS
DDM
Communication analyzer and device-dependent module interfaces
MFS
Communication analyzer and message format service module interfaces

If the first /TRACE SET ON command does not specify MODULE, a default of ALL will be used. Specifying MODULE on subsequent commands will change the defaults.

MONITOR
Enter this keyword to activate or deactivate the IMS Monitor.

When activating the monitor, you must specify one or more of the following MONITOR parameters to indicate the events to be monitored:

ALL
Monitor all of the activity in this list.
APDB
Monitor activity between application programs and databases, including Fast Path activity. Monitoring includes all application program requests to external subsystem databases. Monitoring can optionally be limited to a subset of full-function databases or partitions, Fast Path DEDBs and MSDBs, and the areas comprising those DEDBs by specifying database names or area names.

You can specify the ALL parameter to indicate all databases, areas, and partitions, or you can explicitly enter database names, area names, and partition names.

APMQ
Monitor activity between application programs and message queues, including Fast Path activity.
INTERVAL
Monitor events for a fixed interval of time, entered in seconds. INTERVAL defines the period of time after which no monitor log records will be written.

The duration of the monitoring must be less than twenty-four hours (86,400 seconds). When INTERVAL is not specified, monitoring will continue until the /TRACE SET MONITOR OFF command is issued, or until IMS shuts down.

INTERVAL does not define when the Monitor will be turned off, because the IMS Monitor will not be turned off until the first attempt is made to write a monitor log record after the defined interval has expired.

LA
Monitor line and logical link events.
REGION
Monitor events related to specific dependent regions. The regions might or might not currently be active. Each region can be specified as:
  • A region number from 1 to 999 (reg#). The number cannot exceed the MAXPST with which IMS was brought up.
  • A range of region numbers from 1 to 999 (reg#-reg#). The number cannot exceed the MAXPST with which IMS was brought up.
  • A region name (regionname).
If REGION is not specified, or when REGION ALL is specified, the activities of all dependent regions are monitored.
SCHD
Monitor scheduling and termination events, including Fast Path activities.

You can specify any combination of ALL, APDB, APMQ, INTERVAL, LA, REGION, and SCHD parameters on the MONITOR keyword, as shown in Table 170

Table 170 lists the environments (DB/DC, DBCTL, and DCCTL) from which the MONITOR keyword parameters can be issued.

Table 170. MONITOR Keyword Parameter Environments
Keyword Parameter DB/DC DBCTL DCCTL
ALL X X X
APDB X X
APMQ X X
INTERVAL X X X
LA X X
REGION X X X
SCHD X X X

The IMS Monitor report output varies depending upon which keywords or parameters you specify. Sections of the report can be misleading if required records are excluded. For example, if you specify the APDB parameter without the SCHD parameter, PSB/PCB relationships will not be correctly represented. To get the total DL/I call reports without the IMS line activity, the correct parameters to specify are APDB, APMQ, and SCHD.

The monitor writes log records until one of the following occurs:

When deactivating the monitor, no parameters are required. Any parameters that are entered, other than ALL, are ignored. ALL is the default. If the monitor is to be reactivated, a new set of MONITOR keyword parameters must be selected.

NODE
Causes events related to the node or nodes to be traced.

The NODE parameter can be generic if the USER keyword is not specified and applies to nodes that already exist. Generic NODE parameters do not cause any dynamic nodes to be created.

For ISC nodes, the /TRACE NODE nodename without the USER applies to all half-sessions for NODE nodename, including dynamic ISC sessions that are dynamically allocated later.

For nodes that do not exist, /TRACE SET ON NODE nodename without the USER keyword causes the dynamic NODE nodename to be created to maintain knowledge of the trace request when the node becomes active. Until the node becomes active, /DISPLAY NODE shows a type of UNK (unknown). If the trace is subsequently turned off and the temporary node still exists, it is deleted at the next checkpoint.

/TRACE NODE nodename USER username is valid:

If global resource information is kept in Resource Manager, /TRACE NODE sets a global trace status for the node and sets the trace status locally. If global resource information is not kept in Resource Manager, /TRACE NODE sets the trace status locally. If the node does not exist in an ETO environment, IMS creates the node and sets trace status for the local node.

OSAMGTF
Causes the OSAMGTF keyword to activate or deactivate the OSAM GTF (Generalized Trace facility).
PI
Causes program isolation trace entries to be written to a trace table. PI trace entries are written in the same trace table as DL/I and lock activity trace entries. A PI trace entry contains information about program isolation ENQ/DEQ calls and DL/I calls. The trace entry created by /TRACE TABLE DLI contains different information about DL/I calls and is written as a separate entry in the same trace table. Starting the LOCK trace also causes PI tracing to occur.

If PI is entered without the OPTION keyword, the program isolation trace is kept in storage without being logged. If you are using the program isolation trace to provide statistics and performance data, you should enter OPTION(ALL).

Table 171 lists various /TRACE command formats and shows whether the command influences tracing, logging, and the additional time field.

Table 171. /TRACE Command Formats
Command Tracing Logging Additional Time Field
/TRACE SET ON PI Yes No No
/TRACE SET OFF PI No No No
/TRACE SET ON PI OPTION1 Yes Yes No
/TRACE SET OFF PI OPTION1 Yes No No
/TRACE SET ON PI OPTION TIME Yes No Yes
/TRACE SET OFF PI OPTION TIME Yes No No
/TRACE SET ON PI OPTION ALL Yes Yes Yes
/TRACE SET OFF PI OPTION ALL Yes No No
Note:
  1. This is the same command as /TRACE SET ON/OFF PI OPTION LOG.
OPTION
Indicates a request for one of the following program isolation trace options:
ALL
Both LOG and TIME.
LOG
Requests that traced data be written to the system log. If SET OFF, tracing continues but no buffers are transferred to the system log. LOG is the default.

The log option includes the possibility of externally tracing to a data set other than the IMS OLDS. If specified, DASD external tracing has first priority, TAPE external tracing has second priority, and IMS OLDS has third priority. External tracing to the OLDS is not done without operator approval. EXTERNAL trace is available to the alternate system only for DASD/TAPE type, but not for OLDS. For more information, see IMS Version 9: Diagnosis Guide and Reference and IMS Version 9: Operations Guide.

TIME
Requests that an additional time field be included in each ENQ/DEQ request trace record if a WAIT was needed. This field will contain elapsed wait time. If set OFF, tracing continues but only the time of day is recorded.

Entries for Fast Path have no elapsed wait time.

VOLUME
Specifies the volume of entries to be written to the PI trace table: LOW volume, MEDIUM volume (default), or HIGH volume.

PROGRAM
Is used to trace the DL/I portion of Data Communications (DC) for a specific program. Each DL/I call to a TPPCB, issued by the user application program, is traced on entry to and exit from the DC call handler DFSDLA30. On entry to DFSDLA30 a type 6701-LA3A record is written, on exit from DFSDLA30 a type 6701-LA3B record is written.

Each record will contain the following items if applicable:

If the batch message program (BMP) being traced is the Queue Control Facility (QCF) program product 5697-E99, a 6701-MRQB record is logged by the QCF module DFSQMRQ0. The default program name for the QCF BMP is MRQPSB, and can be overridden on the MSGQUEUE SYSGEN macro.

Items logged in the 6701-MRQB record, if applicable, are:

For more information about the QCF module DFSQMRQ0 and the 6701-MRQB trace, refer to IMS Version 9: Diagnosis Guide and Reference. For more information about the QCF product, refer to IMS Queue Control Facility for z/OS, User's Guide V1R2 (SC26-9685-02).

When CPI Communications driven transaction programs issue the DL/I APSB call specifying a PSB that contains alternate PCBs, only the PROGRAM keyword is applicable.

PSB
Records all full function IMS DL/I database calls issued for the named PSB. FP/DC/SAA calls are not captured when /TRACE SET ON PSB initiated tracing of PSBs.

For LU 6.2, the PSB keyword is applicable only if the CPI Communications driven transaction program has issued a DL/I APSB call to allocate a PSB.

COMP
Used with the /TRACE SET PSB command to generate PCB and data-compare statement images.

The /TRACE SET PSB psbname COMP command only applies to BMPs in a DBCTL environment.

NOCOMP
Prevents PCB and data-compare statement images from being generated. NOCOMP is the default.

The information resulting from the use of this keyword is written on the X'5F' log record.

SET
This keyword turns ON or OFF one of the following:
TABLE
Is used with the SET keyword to start or stop online tracing into the specified trace tables. The TABLE keyword parameter indicates the specific trace that is to be activated or deactivated. The DL/I, LOCK, and PI traces share the same trace tables. However, turning on the DL/I trace does not turn on the LOCK trace, and vice versa.

The following trace into trace tables can be turned on or off with the online /TRACE command.

Table 172 shows the environments in which the trace tables are valid.

Table 172. Trace Tables and Environments in Which They Are Valid
Trace Table DB/DC DBCTL DCCTL
ALL X X X
CSLT X X X
DISP X X X
DL/I X X X
DLOG X X X
FAST X X X
|FPTT X X X
IDC0 X X
LATC X X X
LOCK X X
LRTT X X X
LUMI X X
MSCT X X
OCMD X X X
ORTT X X
OTMT X X
QMGR X X
RETR X X
RRST X X
SCHD X X X
SQTT X X
STRG X X X
SUBS X X X
ALL
Indicates that traces into all trace tables are to be enabled or disabled. This is the default.
CSLT
Indicates that the CSL trace is to be activated or deactivated.
DISP
Indicates that the dispatcher trace is to be activated or deactivated.
DL/I
Indicates that DL/I tracing is to be activated or deactivated.
DLOG
Indicates that the logging trace is to be activated or deactivated.
FAST
Indicates that the Fast Path trace is to be activated or deactivated.

Fast Path Trace is activated by including the FPTRACE DD statement in the dependent region JCL to define the destination of the trace output and by issuing the operator command /TRACE SET ON TABLE FAST.

Recommendation:  Only run this trace in a test environment because the FPTRACE output is very large.

| |
FPTT
|
Indicates that the Fast Path table trace is to be activated |or deactivated. |
IDC0
Indicates that tracing of errors in modules DFSCNXA0 and DFSIDC00 is to be activated or deactivated.
LATC
Indicates that the latch trace is to be activated or deactivated.
LOCK
Indicates that LOCK and PI tracing is to be activated or deactivated.
LRTT
Indicates that the log router trace table is to be activated or deactivated. LRTT is only valid for an RSR tracking subsystem.
LUMI
Indicates that the LU 6.2 manager trace is to be activated or deactivated. /TRACE SET ON TABLE LUMI must be entered first before entering any /TRACE SET ON LUNAME command in order to create the LUMI trace table for trace entries.

LUMI is not valid for an RSR tracking subsystem.

MSCT
|Indicates that the MSC trace is to be activated |or deactivated.
OCMD
Indicates that the OM command trace is to be activated or deactivated.
ORTT
Indicates that the Online Recovery System trace is to be activated or deactivated.
OTMT
Indicates that the IMS Open Transaction Manager Access (OTMA) trace is to be activated or deactivated.
QMGR
Indicates that the queue manager trace is to be activated or deactivated.
RETR
Indicates that the DL/I retrieve trace is to be activated or deactivated. RETR is not valid for an RSR tracking subsystem.
RRST
Indicates that the Resource Recovery trace is activated or deactivated.
SCHD
Indicates that the scheduler trace is to be activated or deactivated. SCHD is not valid for an RSR tracking subsystem.
SQTT
Indicates that the shared queues trace is to be activated or deactivated. SQTT is only valid in a shared-queues environment.
STRG
Indicates that the storage manager trace is to be activated or deactivated.
SUBS
Indicates that the external subsystem trace is to be activated or deactivated. SUBS is not valid for an RSR tracking subsystem.
OPTION
Is used to indicate whether or not the trace tables are to be logged.

The meaning of the OPTION parameters are:

LOG
Requests that the trace tables be written to the system log before they are reused (wrapped).

The log option includes the possibility of externally tracing to a data set other than the IMS OLDS. If specified, DASD external tracing has first priority, TAPE external tracing has second priority, and IMS OLDS has third priority. External tracing to the OLDS is not done without operator approval. This option is ignored for the retrieve trace and the Fast Path trace, (default).

FPTRACE has its own SYSOUT. EXTERNAL trace is available to the alternate system only for DASD/TAPE type, but not for OLDS. For more information, see IMS Version 9: Diagnosis Guide and Reference and IMS Version 9: Operations Guide.

NOLOG
Indicates that the trace tables are not logged. This means that there will be no record of trace tables that have been reused. NOLOG is the default.

The same trace table is used for DL/I, LOCK, and PI trace information. Whether or not this table is logged will depend on the logging option of the last /TRACE command that was entered for DL/I, PI, or LOCK.

VOLUME
Specifies the volume of entries to be written to the specified trace table: LOW volume, MEDIUM volume (default), or HIGH volume.

The VOLUME keyword is valid on active and RSR tracking subsystems.

TAKEOVER
Controls tracing during takeover only, and is separate from regular tracing. TAKEOVER tracing can be set for LINE, LINK, NODE, and UNITYPE keywords.

TAKEOVER only applies in an XRF environment. When TAKEOVER is used with SET OFF, the trace is turned off before takeover. When an output message is dequeued for a terminal, takeover tracing will stop for that terminal.

If both regular and takeover tracing are entered, the most recent setting will override any previous settings; for example, takeover tracing will override regular tracing if regular tracing was entered first. This means that either regular or TAKEOVER tracing can be in effect, but not both.

/TRACE TAKEOVER can be issued only from an XRF active system. It is rejected if entered from an alternate or non-XRF system. It is recovered across restart and takeover, and only needs to be entered once until cold start. Tracing occurs only if the session was active at the time of the takeover.

TCO
Is used to trace TCO (Time Controlled Operation) activity. For the first /TRACE command with the TCO keyword, the default module and level information is used. TCO trace is basically a DC LINE or NODE trace, and the information developed is also written on the type X'67' log record.
TIMEOUT
Is used to start or stop the I/O Timeout Detection facility.
time#
is the number of minutes used to determine if the I/O response is overdue. After this number of minutes, time has run out for the response. The range is from 1 through 60; the default value is 0.

If time# is 0, or not specified, then when I/O is initiated for a node, the node will be placed on a queue, so that its status can be displayed with the /DISPLAY TIMEOVER command. You will not be notified if the node does not receive a response and the time elapses, and the node will not be reactivated.

If time# is not 0, then the following keywords can be used.

MSG
Indicates that a message is issued to the master terminal when I/O takes longer than time# minutes. The message indicates that the time has elapsed.
AUTO
IMS issues a message to the master terminal, then perform a VTAM VARY NET,INACT and a VARY NET,ACT, if I/O takes longer than time# minutes. An /OPNDST is performed for operable devices that are not shared. For ISC nodes, a message is issued, but there is no automatic (AUTO) restart of any sessions and no VTAM VARY commands issued.

If you wish to change the time period or the action to be taken if timeout occurs, you can enter the /TRACE SET ... TIMEOUT command while the Timeout Detection facility is already active. However, if nodes are receiving or sending input or output, they will function according to the previous settings of the /TRACE ... TIMEOUT command. If this is undesirable, then you should enter the /TRACE SET OFF TIMEOUT command before reentering /TRACE SET ... TIMEOUT.

If the timeout trace facility failed during IMS initialization, the /TRACE SET ... TIMEOUT command is rejected with an error message.

The VTAM TIMEOUT I/O facility is automatically started during IMS shutdown. It is set for 1 minute and AUTO.

TMEMBER
Is used to trace IMS Open Transaction Manager Access (OTMA) client activity for OTMA clients.
TPIPE
Is used to trace transaction pipe activity for OTMA clients.

While processing the /TRACE TMEMBER TPIPE command, IMS creates a temporary transaction pipe (if one does not already exist) with the trace status. IMS sets the synchronization status for this transaction pipe when it sends or receives the first message for the transaction pipe.

TRANSACTION
Is used to trace the DL/I portion of Data Communications (DC) for a specific transaction. Each DL/I call to a TPPCB, issued by the user application program, is traced on entry to and exit from the DC call handler DFSDLA30. Upon entry to DFSDLA30, a type 6701-LA3A record is written; upon exit from DFSDLA30, a type 6701-LA3B record is written.

Each record will contain the following items, if applicable:

For more information about this trace, see the discussion of the DLA3LOG trace in IMS Version 9: Diagnosis Guide and Reference.

TRAP
Is used to detect overwrites of MFS blocks. When /TRACE is used, IMS attempts to detect overwrites in the MFS blocks. If an overwrite occurs, IMS sends a warning message. See IMS Version 9: Diagnosis Guide and Reference for a description of trace records.
UNITYPE
Causes events related to the physical terminals of specified type to be traced.

The UNITYPE keyword is used to trace all terminals of a specific type. Parameters (unitypename) are similar to the identifiers displayed in the TYPE column by the /DISPLAY NODE and /DISPLAY LINE/PTERM commands. Table 173 shows the terminal types for UNITYPE parameters.

Table 173. UNITYPE Parameters and Terminal Types
UNITYPE Parameter Terminal Type
2260R 2260/2265 REMOTE
3286 3284/3286
SYSTEM/7 SYSTEM 7
2980 2980
3270R 3270 REMOTE
3270I 3270 LOCAL
RDR/PTR LOCAL SYSIN/SYSOUT
SYSTEM/3 SYSTEM 3
FIN 3600
3277 3270 VTAM
SYS/7BS SYSTEM 7 BSC
SLU1 SLU TYPE 1
SLU2 SLU TYPE 2
SLUP SLU TYPE P
LU 6 LU TYPE 6
NTO NTO
CONSOLE z/OS SYSTEM CONSOLE
TWX TWX SWITCHED
3275SW 3270 SWITCHED
MSCBSC Binary Synchronous Communication
MSCMTM Memory to Memory Communication
MSCCTC Channel to Channel Adapter
MSCVTAM MSC VTAM

If global resource information is kept in Resource Manager, /TRACE UNITYPE sets a global trace status for all of the nodes of a specific type. This requires that the inactive static nodes be processed on every IMS system. The UNITYPE keyword is similar to specifying a generic parameter. If global resource information is not kept in Resource Manager, /TRACE UNITYPE sets the trace status locally.

Examples

Example 1 for /TRACE Command

To turn on message format service module and communication analyzer level 4 control block tracing for all physical terminals on line 4.

Entry ET:

  /TRACE SET ON LINE 4 LEVEL 4 MODULE MFS

Response ET:

  DFS058I  TRACE COMMAND COMPLETED

Example 2 for /TRACE Command

To turn on tracing for a logical link:

Entry ET:

  /TRACE SET ON LINK 2 LEVEL 4 MODULE ALL

Response ET:

  DFS058I  TRACE COMMAND COMPLETED

Example 3 for /TRACE Command

Entry ET:

  /TRACE SET ON MONITOR ALL

Response ET:

  DFS058I TRACE COMMAND COMPLETED
  DFS2500I DATASET DFSDCMON SUCCESSFULLY ALLOCATED
  DFS2212I DC MONITOR STARTED

Explanation: The monitor is activated and all events will be monitored.

Entry ET:

  /TRACE SET OFF MONITOR

Response ET:

  DFS058I TRACE COMMAND COMPLETED
  DFS2500I DATASET DFSDCMON SUCCESSFULY DEALLOCATED
  DFS2212I DC MONITOR STOPPED

Explanation: The monitor is deactivated.

Entry ET:

  /TRACE SET ON MONITOR LA

Response ET:

  DFS058I TRACE COMMAND COMPLETED

Explanation: The monitor is activated. Line and logical link activities will be monitored. The monitoring of events from the previous activation of the monitor no longer apply.

Example 4 for /TRACE Command

To turn on program isolation tracing, include the additional time field in the trace record and have the trace information logged:

Entry ET:

  /TRACE SET PI OPTION ALL

Response ET:

  DFS058I  TRACE COMMAND COMPLETED

Example 5 for /TRACE Command

To turn off logging of program isolation trace data but continue the trace in storage:

Entry ET:

  /TRACE SET OFF PI OPTION LOG

Response ET:

  DFS058I  TRACE COMMAND COMPLETED

Example 6 for /TRACE Command

To stop program isolation tracing.

Entry ET:

  /TRACE SET OFF PI

Response ET:

  DFS058I  TRACE COMMAND COMPLETED

Example 7 for /TRACE Command

To trace all DL/I calls issued for PSB AALST:

Entry ET:

  /TRACE SET ON PSB AALST COMP

Response ET:

  DFS058I  TRACE COMMAND COMPLETED

Example 8 for /TRACE Command

To turn on online tracing into the DL/I trace table:

Entry ET:

  /TRACE SET ON TABLE DL/I

Response ET:

  DFS058I TRACE COMMAND COMPLETED

Example 9 for /TRACE Command

To turn on the dispatcher's trace tables and have them written to the system log:

Entry ET:

  /TRACE SET ON TABLE DISP OPTION LOG

When the dispatcher's trace tables are no longer required:

Entry ET:

  /TRACE SET OFF TABLE DISP

Response ET:

  DFS058I  TRACE COMMAND COMPLETED

Example 10 for /TRACE Command

To turn on storage manager trace tables:

Entry ET:

  /TRACE SET ON TABLE STRG

Response ET:

  DFS058I TRACE COMMAND COMPLETED

When the storage manager trace tables are no longer needed:

Entry ET:

  /TRACE SET OFF TABLE STRG

Response ET:

  DFS058I TRACE COMMAND COMPLETED

Example 11 for /TRACE Command

Entry ET:

  /TRACE SET ON TMEMBER CLIENT1 TPIPE TPIPESY

Response ET:

  DFS058I 15:45:05 TRACE COMMAND COMPLETED   SYS3
  DFS996I *IMS READY*  SYS3

Example 12 for /TRACE Command

To log the PCB, I/O area, and PST whenever module DFSDLA30 is invoked to process transaction APPLE:

Entry ET:

  /TRACE SET ON TRANSACTION APPLE

Response ET:

  DFS058I TRACE COMMAND COMPLETED

Example 13 for /TRACE Command

To trace all 2740 model 2 terminals:

Entry ET:

  /TRACE SET ON UNITYPE 2740II

Response ET:

  DFS058I TRACE COMMAND COMPLETED
Note:
The control blocks and modules traced depend on the last LEVEL and MODULE specifications entered before the command. If the LEVEL and MODULE keywords have not yet been entered, the defaults of 4 and ALL will be used.

Example 14 for /TRACE Command

This is an example of temporary nodes created to retain trace status data.

Entry ET:

  /TRACE SET ON NODE DTSLU607

Response ET:

  DFS058 TRACE COMMAND COMPLETED

Entry ET:

  /DISPLAY NODE DTSLU607

Response ET:

NODE-USR TYPE   CID       RECD ENQCT DEQCT   QCT  SENT
DTSLU607 UNK    00000000     0     0     0     0     0 TRA
*90127/091634*

Entry ET:

  /DISPLAY NODE DTSLU607

Response ET:

NODE-USR TYPE   CID       RECD ENQCT DEQCT   QCT  SENT
DTSLU607 LUT6
-N/A     UNK    00000000     0     0     0     0     0 TRA
-IMSUS01        01000002     0     0     0     0     0 SIGN(IMSUS01 )
                                                       IDLE CON TRA PRI
-IMSUS02        01000004     0     0     0     0     0 SIGN(IMSUS02 )
                                                       IDLE CON TRA PRI
*90127/091432*

Explanation: The /TRACE command is issued for a dynamic ISC NODE that does not yet exist, DTSLU607, causing a temporary node to be created to retain the trace status. Once the ISC parallel sessions IMSUS01 and IMSUS02 are allocated, the trace status is applied to them both.

Go to the previous page Go to the next page

IBM Confidential

Downloads | Library | Support | Support Policy | Terms of use | Feedback
Copyright: IBM Corporation 1974, 2004 Copyright IBM Corporation 1974, 2004  timestamp Last updated: March, 2004