Analyzing the DEDB during change

If your site has a license for the Fast Path Analyzer/EP product, pointer validation will occur automatically (by default) when you execute a database change.

This automatic process applies the default value of QUICK for the POINTER_VALIDATION keyword to perform a checksum validation of pointers for each segment type within each UOW of the database that is specified on the CHANGE command.

Automatic pointer validation provides an assurance of the area’s pointer integrity, while providing statistics that show how the database change process affected space usage.

Note

You can override automatic quick pointer validation and request more detailed validation by specifying POINTER_VALIDATION=FULL on the CHANGE or GLOBAL command. Direct pointers are validated by using the cross-reference technique. You can also specify any other valid value for the POINTER_VALIDATION keyword (such as POINTER_VALIDATION=NONE to completely disable the analysis function).

If an SDEP segment is defined for the database, SDEP pointers are also validated by default using the same technique as specified for direct pointers. You can manually specify another valid value for the SDEP_VALIDATION keyword to control how SDEP pointers are to be validated.

You can also specify additional functions that are associated with the analysis function:

  • Use the RAP_VALIDATION keyword to control how RAPs are processed.

  • Use the LARGEST_DATABASE_RECORDS keyword to specify the number of largest database records to be tracked by the analysis process.

  • Use the REPORT and THRESHOLD subcommands to control the generation of analysis reports and exception testing.

The example in below figure requests that analysis be performed on all output areas that are created by the CHANGE command. Direct pointers are validated by specifying FULL for the POINTER_VALIDATION keyword. SDEP pointers (if any exist) are validated by using the same technique. For more information, see Pointer validation. Default reports are to be produced and no threshold checking is performed.

Requesting analysis during DEDB change

CHANGE  DBD=dbdname,
 POINTER_VALIDATION=FULL


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments