$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
 
 

Fast Path Offline Suite 4.0 ... Using Analyzing a DEDB

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


Was this page helpful? Yes No Submitting... Thank you
Last modified by Winner kumar Jaiswal on Nov 28, 2019
using

Comments

Orphaned sequential dependents
Restrictions for correcting pointer errors
© Copyright 1992-2019 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2020 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.