In the following table, the left column categorizes the problems. Follow the instructions in the right column to generate useful diagnostic data.
|
For problems in |
Be sure to check |
|---|---|
|
Installation |
Your operating system type, maintenance level, and the options you established during installation. The SMP/E RECEIVE and APPLY output. Ensure that they completed successfully, with no unexplained linkage editor messages. That there are not mixed versions of CA TLMS. Check STEPLIB and LNKLST data sets. |
|
Batch programs/utilities |
The options in effect at the time of the problem (run CATOPTS). The SYSUDUMP/SYSABEND dump if the problem resulted in an abend. The CA TLMS reports, if any indicate the problem, and create a snapshot of volumes involved. |
|
Online screens |
Prints of screens involved, if possible. Otherwise, the sequence of keystrokes and fields modified. Snapshot of VMF records. Dump, if one was generated. (SYSUDUMP must be located.) CLIST used to invoke CATLISPF. |
|
All areas |
The SYSPRINT output from an execution of CATOPTS. Other vendor or IBM products that might affect the situation. All special PTFs, user exits/modifications and operating system intercepts that are installed and active. The combined console log for the period during which the problem occurred. Activity in other address spaces that may have a bearing on the problem (for example, tape mounts). Whether there was a system or user abend. If a user abend, please check user abend codes in the Message Reference Guide. |
|
Online modules, online recorder, VMF updates |
The options in effect at the time of the problem. Use TLMSSTAT. The JCL to execute CATOPTS is //OPTS EXEC CATOPTS. The SYSUDUMP/SYSABEND dump if the problem resulted in an abend, or the snap dump through the CTS command 'SPINOFF SNAP' or 'SPINOFF DUMP'. The execution JCL listing and cataloged procedures for the job involved, and the console log for the time involved. Allocation messages, job log, actual output of execution JCL. The CTS log for the time period can be obtained using the CTS command SPINOFF LOG. Type of tape involved: SL, BLP, NL, NSL, multivolume/multi-data set. Disposition of tape involved: NEW, MOD, PASS, OLD, and so on. Your operating system version number, and a snapshot of the volumes involved (see Chapter 6 of the User Guide), and DVs of the volumes before and after the job. The trace output for the period of the job and events causing the failure (see Tracing). |
|
Copyright © 2014 CA.
All rights reserved.
|
|