Collecting Diagnostic Data

Troubleshooting › Problem Resolution › Collecting Diagnostic Data

Collecting Diagnostic Data

The following information is helpful in diagnosing problems that might occur:

Short description of the problem
Control statements used to activate your product
JCL used to install or activate your product
Relevant system log or console listings
Relevant system dumps or product dumps
List of IBM or third-party products that might be involved
Manufacturer, model number, and capacity of your hardware
Numbers and text of IBM or CA error messages associated with the problem
Names of panels where the problem occurs
Listings of all fixes applied to all relevant software, including:
- The dates fixes were applied
- Fix numbers
- Names of components to which fixes were applied

In the table below, use the left column to categorize the problem your site has encountered. Then, follow the instructions in the corresponding right column to generate useful diagnostic data.

Type of Problem	Procedure
SMP error message	See IBM's System Modification Program Extended Messages and Codes and check the listing for all messages. Save all SMP output.
Installation with SAMPJCL members	See the installation steps in this guide and all installation PDCs. Save all output.
SMFD not link edited correctly, or not selected on APPLY install step	The APPLY step must have the following APPLY select statement: APPLY SELECT (CSFC000) Save all SMP output.
CA error message	Review message in the Message Guide. Before rerunning the SMFD program, make sure the JCL contains the SYSXDIAG SYSOUT DD statement and the SYSMDUMP DD statement. Save output from SYSXDIAG, SYSPRINT, JES job and messages log.
SMFD program abend	Review the audit trail for error messages. See the Message Guide to determine if the problem can be resolved. If not, save output from SYSXDIAG, SYSMDUMP, SYSPRINT DD statements, along with the JES job and messages log. Note: For the last two problems listed in this table, you should back up the SCDS file at the time of the error.

Tell Technical Publications how we can improve this information