z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Objects not selected for class transition processing

z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support
SC23-6866-00

If once the system console log is examined no error messages are found, the possibility of OSMC not selecting the object for processing needs to be investigated.

The first step in determining if OSMC did not perform a class transition against the object, and why, is to examine the object’s directory table entry. Use the following SQL statement to query the object:
SELECT * FROM HLQ.OSM_OBJ_DIR
WHERE   ODNAME = 'object_name';

Verify that the pending action date (ODPENDDT) is the current date or earlier. An object with a pending action date that is assigned a date in the future will not be selected for processing. For example, if today’s date is 01/05/2012, and the pending action date for the object is 01/05/2012 or earlier, the object should be chosen for OSMC processing. If the pending action date for the object is 03/05/2012, the object is not chosen for OSMC processing until today’s date is the same or earlier than the pending action date for the object.

Check the expiration date (ODEXPDT). If the object’s expiration date has been reached, OSMC has no reason to move it to another level in the hierarchy.

For more information concerning expiration dates, see Processing object expiration.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014