Requesting analysis during DEDB change or reload
This automatic process applies the default value QUICK for the POINTER_VALIDATION keyword. The analysis function performs a checksum validation of pointers for each segment type within each UOW of the database that is specified on the CHANGE or RELOAD command.
Automatic pointer validation provides assurance of the area’s pointer integrity, while providing statistics that show how the database change or reload 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, RELOAD, 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 process).
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 REPORT and THRESHOLD subcommands to control the generation of analysis reports and exception testing.
The example in the following figure requests that analysis be performed on all output areas created by the CHANGE command. Direct pointers are validated by specifying a value of FULL for the POINTER_VALIDATION keyword. SDEP pointers (if any exist) are validated by using the same technique. Default reports are produced, and no threshold checking is performed. For more information, see Pointer validation.
CHANGE DBD=dbdname,
POINTER_VALIDATION=FULL,
For more information about the change function, see Changing DEDB structure in place. For more information about the reload function, see Unloading and Reloading a DEDB.
Comments
Log in or register to comment.