Orphaned sequential dependents

If a root segment is deleted, its sequential dependent segments become 'orphans.' The segments still exist within the active sequential dependent portion of the area, but they are not referenced by a valid SDEP pointer.

The SDEP validation modes handle orphaned sequential dependents as follows:

  • SDEP_VALIDATION=NONE and SDEP_VALIDATION=OFF do not detect orphaned segments and will not report them as errors.
  • SDEP_VALIDATION=QUICK reports a pointer error if an orphaned segment exists. This mode of pointer validation cannot distinguish between orphaned segments and other problems, and it is not recommended if orphaned segments are known to exist in the area.
  • SDEP_VALIDATION=FULL identifies the individual segments as orphans.

You can use the ORPHANED_SDEP_MSG keyword to control the severity that is associated with this condition and the generation of messages.

Note

If you are running IMS version 6.1 or later, any SDEP with a timestamp less than the logical begin timestamp is treated as deleted. SDEP_VALIDATION=QUICK might report a pointer problem after SDEP scan/delete has been run. This condition occurs if a root segment is deleted, and that root segment was previously the owner of one of the logically deleted SDEP segments.

Related topic

Verifying-area-integrity


 

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