TRACE command

The TRACE command activates and deactivates the HCD trace facility. The command allows you also to limit the detail of data written into the trace data set by requesting that only certain functions and details should be traced.

The TRACE command can be entered on any HCD panel showing a command line. The command can also be specified in the HCD profile data set. It is, however, not shown in the HCD Profile Options dialog.

For HCD to write the output to the trace data set, ON must be specified with at least one trace category (or you must have invoked HCD with the TRACE parameter, see Activating the trace). To view the trace output, you have to close the trace data set first. You can do this by either leaving HCD or by entering the command TRACE OFF,CLOSE.

The format of the command is as follows:

TRACE Command

Read syntax diagramSkip visual syntax diagramTRace ONOFF,CLOSE reset trace-category
trace-category
Read syntax diagramSkip visual syntax diagram,ALLBatchCommandDialogDYNamicHOMMigrationRepositoryRepServiceRESETServiceUIMUIMServiceUtilityValidationOther,LEVEL=n,ID=IODF,REPAIR,ID=JCL,ID=CLOG
Notes:
  1. You may abbreviate some of the keywords. The characters you have to use are indicated by uppercase (you must then omit lowercase). For example RepService may be abbreviated as RS.
  2. At least one parameter must be specified with TRace.
ON
Starts the trace facility.
OFF
Stops the trace facility.
CLOSE
Closes the trace data set.
Note: ON, OFF and CLOSE can not be used if the profile is allocated by the HCD dispatcher and used by HCM.
reset
Reset all currently active categories, LEVEL and ID. If not using RESET, HCD will remember the trace categories specified with previous trace commands and adds them up. If combined with trace categories, it should be specified before the categories, because the keywords and categories are evaluated in sequence. RESET at the end would clear the specified trace category.
trace category
Specifies the functional scope to be traced:
ALL
Traces for all categories except DEBug and RepService. To have a complete trace, use categories ALL, DEBug, RepService.
Batch
Trace all batch routine.
Command
Trace all command routines.
DEBug
Traces internal services (not included, when ALL is specified).
Dialog
Trace all dialog routines.
DYNamic
Trace all dynamic routines.
HOM
Trace all object management routines.
Migration
Trace all migration routines.
Repository
Trace all repository main routines.
RepService
Trace all repository service routines. (Not included, when ALL is specified).
Service
Trace all service routines.
UIM
Trace all UIM routines.
UIMService
Trace all UIM service routines.
Utility
Trace all utility routines.
Validation
Trace all validation routines.
Other
Trace all other not yet mentioned routines.
LEVEL=n
Assigns a level of detail to the functions to be traced, where n is a decimal number ranging from 0 to 255. If the option is omitted, the default level of 5 is assumed. The TRACE option described in Input parameter string is equivalent to the command TRACE ON,ALL,LEVEL=255.
ID=IODF
Writes an IODF dump into the trace data set. This parameter cannot be specified in the HCD profile. If you have a consistent IODF, an output in the trace data set is only shown when you set LEVEL=128 or higher. Otherwise, an output is only shown if the IODF contains defects.
REPAIR
Removes detected errors in the work IODF and reports corrections in the trace data set. Before you use the REPAIR option, you must set the work IODF in update mode.
ID=JCL
Writes into the trace data set all statements generated when action Transmit configuration package is invoked from the HCD dialog.
ID=CLOG
Writes the contents of the change log file into the HCD trace data set. You should use this option together with LEVEL=8. This parameter cannot be specified in the HCD profile.