Occasionally, there are problems in specific environments
or certain problem types, that require special handling. If IMS can accept commands, you can
set a trace.
Procedure
- If IMS can accept
commands, use the following IMS command
to set up the internal trace environment:
/TRA SET ON TABLE nnnn
where
nnnn= is
the DISP, SCHD, DLI, LOCK or LATCH parameter. Each parameter must
be entered in a separate
/TRA command.
- Set the z/OS® system
trace table size to 999K and turn on branch tracing by issuing the
following command:
- Obtain two z/OS SVC
dumps of the CTL, DL/I, suspicious dependent region, or CCTL, DBRC,
and IRLM regions. Taking a second z/OS SVC
dump will help differentiate normal IMS processing
from the problem. Obtain a z/OS SVC
dump with this series of commands:
DUMP COMM=(dump title)
R id JOBNAME=(j1,j2,j3,j4,j5,j6),
SDATA=(CSA,PSA,RGN,SQA,SUM,TRT),END
In the previous
example,
- j1
- is the IMS CTL or DBCTL region
job name
- j2
- is the IMS DL/I region job
name
- j3
- is the suspicious IMS dependent
region job name, if any
- j4
- is the suspicious CCTL (CICS®)
region name, if any
- j5
- is the IRLM region job name (if IRLM DB locking is used)
- j6
- is the DBRC region job name
- Reset the z/OS system
trace table to its original settings.
Note: IMSplex partner dumps are probably not required for
loop problems, unless they are also looping.