Running the trace EXEC creates a trace file that you can
submit as part of your problem documentation. Complete the following
steps to generate a trace.
Procedure
- Start the trace EXEC by entering the following statement:
EX 'smphlq.SFABCLIB(FABZTRAP)' 'smphlq workhlq csvol fdebug'
Where:
- smphlq
- Is the high-level qualifier of the SMP/E target data sets.
- workhlq
- Is an optional high-level qualifier for work data sets.
- csvol
- Is an optional parameter that specifies the volume serial of a
DASD device to be used by IMS Database
Repair Facility data
sets (for non-SMS sites only).
- fdebug
- Is an optional parameter. Set it to 1 to enable tracing. The
default is to have tracing disabled.
The workhlq, csvol,
and fdebug parameters are optional. When one of
these parameters is omitted, but subsequent ones appear, an asterisk
is used as a placeholder. See Examples for what happens
when these parameters are specified or omitted.
- Duplicate the steps that caused IMS Database
Repair Facility to
fail or to produce incorrect results.
After you run
IMS Database
Repair Facility in
tracing mode, a trace file is produced with the following naming convention:
userid.DBRTRAP.Dnnnnn.Tnnnnn
Dnnnnn and
Tnnnnn are
today's date and time.
Examples
The following examples
illustrate what happens when these parameters are specified or omitted.
- All three, workhlq, csvol,
and fdebug are specified:
EX 'smphlq.SFABCLIB(FABZTRAP)' 'smphlq ZZZ SYS666 1'
The work data set names default to ZZZ.userid.xxx,
the data set allocation uses UNIT=SYS666, and tracing takes place.
- Only csvol and fdebug are
specified:
EX 'smphlq.SFABCLIB(FABZTRAP)' 'smphlq * SYS123 1'
The
work data set names default to userid.xxx,
the data set allocation uses UNIT=SYS123, and tracing takes place.
- workhlq and csvol are not
specified, but fdebug is specified:
EX 'smphlq.SFABCLIB(FABZTRAP)' 'smphlq * * 1'
The
work data set names default to userid.xxx,
and the data set allocation uses UNIT=SYSDA. Tracing takes place.