Objects not selected for expiration processing by OSMC

There might be a number of reasons why an object is not selected for expiration during OSMC processing. The expiration date assigned to an object might not be correct, the object might be in a management class that has different expiration attributes assigned to it than you think it has, a collection entry might not be found within the collection table, inconsistencies might exist in a collection ID between the catalog and the collection table, or the Deletion-Hold flag in the ODSTATF field might be set on. The first step in investigating why OSMC does not select the object for expiration processing is to examine the object directory table (HLQ.OSM_OBJ_DIR). The following SQL command retrieves the object’s directory table entry:

SELECT * FROM HLQ.OSM_OBJ_DIR
WHERE ODNAME = 'object_name';

Examine the ODSTATF field in the object directory to verify that deletion-hold (ODSTATF_DELHOLD) is not turned on for this object. See Table 3 for more information about the ODSTATF field.

Verify that the pending action date (ODPENDDT) is the current date or earlier.

If the expiration date (ODEXPDT) in the object directory table is less than or equal to the current date, then the object should expire. If the expiration date is the special value 9999-12-31, the object never expires. If the expiration date is 0001-01-01, OAM uses the management class attributes to determine the expiration date. If the expiration date is 0002–02–02, the object is in event-based-retention mode and cannot be deleted until OAM receives notification by the EVENTEXP keyword on an OSREQ API request.

During OSMC processing, a management cycle called the shelf manager runs after storage management has completed for each Object or Object Backup storage group. Shelf manager examines all the volumes in an Object or Object Backup storage group to determine if there are any volumes on which all of the objects are expired. If all of the objects on a tape volume are expired and the tape volume is full, the tape volume is dispositioned as specified in the SETOAM TAPERECYCLEMODE keyword of the CBROAMxx PARMLIB member.

If all objects on both sides of a rewritable optical platter are expired, the platter is reinitialized and dispositioned as specified in the SETOPT OPTICALREINITMODE keyword of the CBROAMxx PARMLIB member. If all objects on both sides of a WORM optical platter are expired and both sides of the platter are full, the WORM platter is scheduled for ejection and the operator is prompted to remove it from the input/output station of the optical library. Knowledge of the WORM volume is removed from the OAM inventory.