Objects not moved to a new storage level during OSMC processing

This information allows you to identify, investigate, and overcome the problem when objects do not move to the expected level within the hierarchy as defined by the ISMF storage class and management class definitions.

To determine where an object resides within the storage management hierarchy (on disk, optical, or tape), query the directory table entry for the object using the following SQL statement:

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

The content of the ODLOCFL field indicates the location of the primary copy of the object as follows:

blank—primary copy resides on an optical disk volume
D—primary copy resides on disk sublevel 1 (DB2)
E—primary copy resides on disk sublevel 2 (file system)
T—primary copy resides on a tape sublevel 1 volume
U—primary copy resides on a tape sublevel 2 volume
R—primary copy has been recalled to disk sublevel 1 (DB2)
2—primary copy has been recalled to disk sublevel 2 (file system)

If the object is not found on the expected medium, it might be because an error has occurred during the OSMC cycle or because the SMS environment has not been properly defined to allow objects to make a transition between storage classes.

To determine if there has been an error during the OSMC cycle, examine the system console log from the start and through the completion of OSMC processing of the Object storage group containing the object.

Any CBRnnnn messages found in this log might indicate a problem.

Note: Objects greater than 256MB are supported on the DB2 sublevel, file system sublevel, tape sublevel 1, and tape sublevel 2 in the OAM storage hierarchy. OSMC will not attempt to transition or write backup copies of objects greater than 256MB to the optical level. CBR9226I will be issued once per collection if any objects greater than 256M (268,435,456 bytes) were encountered in a collection during OSMC processing that required writing the object or an object backup copy optical level of the OAM storage hierarchy.

For more information concerning these messages and how to resolve the problems that prompted these messages, see z/OS MVS System Messages, Vol 4 (CBD-DMO).