Correcting pointer errors

If pointer errors occur during the analysis process, you can use the optional CORRECTIONS_FILECTL subcommand with the ANALYZE command to correct pointer errors.

If the CORRECTIONS_FILECTL subcommand is specified, pointer corrections control cards are created and then written to a pointer corrections output data set that can be used to zap pointer errors to zero. If the CORRECTIONS_FILECTL subcommand is not specified, no pointer corrections control cards are created, and invalid pointers are not removed.

Error counts

The message BMC110005I summarizes the number of warnings, errors, and critical errors generated while running the ANALYZE command. However, when you run ANALYZE under another command, the message BMC110005I shows counts from the ANALYZE function only. The message counts in this message do not include counts from the other command.

Tip

You can run the ANALYZE command as the main command in Fast Path Analyzer/EP product or as a subcommand under Fast Path Reorg/EP product.

BMC110005I dbdName,areaName: x WARNING(S), y ERROR(S), z CRITICAL ERROR(S)

Example

BMC110005I DPR3S,DPR3SA0: 0 WARNING(S), 3 ERROR(S), 0 CRITICAL ERROR(S)

This section contains the following topics:

Related topic

Analyzing-a-DEDB


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*