Displaying OAM Status

The following command syntax displays OAM status:


>>-+-DISPLAY-+--SMS,OAM-+----------------+---------------------><
   '-D-------'          '-,L=-+-a------+-'   
                              +-name---+     
                              '-name-a-'

OAM: Displays OAM status.

L={a | name | name-a}: Specifies the location where the results of the inquiry are to be displayed, where name is the console name, and a is the display area on the console screen.

To display OAM status, enter the following command:

DISPLAY SMS,OAM

This results in F OAM,D,OAM command being issued.

The OAM display status shows which backup copy is being used by automatic access to backup processing for each of the possible reasons. If automatic access to backup is not active for a specific reason, the status display shows that no backup copy is being used. The following information is displayed for an optical library.

CBR1100I OAM status:
TOT   USE   TOT  USE  AVL  TOT  USE   AVL  TOT  USE  AVL  SCR   REQ
LIB   LIB   DRV  DRV  DRV  LDR  LDR   LDR  SDR  SDR  SDR  VOL    CT
aaa   bbb   ccc  ddd  eee  fff  ggg   hhh  iii  jjj  kkk  lll   mmm
exitname processing {ENABLED|DISABLED|BYPASSED|BYPASSED_RS|OPERATOR-DISABLED}.
Access Backup status for xxx reasons, using yyy backup copy.
Diagnostic messages {ACTIVE|INACTIVE} for OSREQFS. Limit=nnnn.
DB2 SSID: ssid
XCF GROUP NAME: group-name
XCF MEMBER NAME: member-name
CBROAM: parmlib-suffix  
OAM1 Parms: TIME=xxx MSG=xx UPD=x QB=x
            MOS=xxxx OTIS=x LOB=x DP=x

The fields in the data line specify the number of each resource, as follows:

aaa

Total number of optical libraries in the configuration.

bbb

Number of usable optical libraries (online and operational).

ccc

Total number of optical drives in the configuration.

ddd

Number of usable optical drives.

eee

Number of available optical drives (online, operational, and not in use).

fff

Total number of library optical drives in the configuration.

ggg

Number of usable library optical drives.

hhh

Number of available library optical drives.

iii

Total number of operator-accessible optical drives in the configuration.

jjj

Number of usable stand-alone or operator-accessible optical drives.

kkk

Number of available operator-accessible optical drives.

lll

Number of scratch optical volumes in the OAM configuration database.

mmm

Total number of optical read requests waiting to be scheduled.

nnnn

When the status for diagnostic messages issued for file system related errors originating from OSREQ requests is ‘ACTIVE’, indicates the approximate number of messages yet to be issued.

exitname

The name of the exit for which status is being displayed. This line is repeated for each installation exit. You can use the CBRUXSAE and EDGTVEXT exits for object support. However, you would use the other exits (CBRUXENT, CBRUXEJC, CBRUXCUA, and CBRUXVNL) with tape libraries. The status codes are as follows:

ENABLED: The exit is enabled and executed when the requested function is required.
DISABLED: The exit has been disabled due to an error or an abend in the installation exit. For EDGTVEXT, OAM continues releasing object tape volumes from the OAM inventory.
BYPASSED: For CBRUXVNL, either the exit returned code 16, indicating that it was not to be called again, or an error (or abend) occurred in the exit and the exit will not be invoked. For CBRUXSAE, either the exit returned a return code 16, or it returned return codes for each of the five OSREQ functions (STORE, RETRIEVE, QUERY, CHANGE and DELETE), effectively putting all OSREQ functions in bypass mode. For all other exits, the exit returned a return code 16, indicating that the requested function is to continue without calling the exit.
BYPASSED_RS: Bypass in restricted-store mode: This is used exclusively for the CBRUXSAE PROCESSING for STORE. The exit returned a return code 254 for an OSREQ STORE (or STOREBEG) request indicating that subsequent stores are allowed to existing collections but are not allowed to collections that do not exist.
OPERATOR-DISABLED: Only the exits for the tape library uses this status code. For information on displaying OAM status for tape libraries, see z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries.

If the CBRUXSAE user exit is in ENABLED mode then the following lines are displayed:

CBRUXSAE processing {ENABLED|BYPASSED|BYPASSED_RS} for STORE.
CBRUXSAE processing {ENABLED|BYPASSED} for RETRIEVE.
CBRUXSAE processing {ENABLED|BYPASSED} for QUERY.
CBRUXSAE processing {ENABLED|BYPASSED} for CHANGE.
CBRUXSAE processing {ENABLED|BYPASSED} for DELETE.

The following fields are displayed in the status message for the OAM access backup processing:

access backup status

The status of Access Backup processing for this reason. The following are valid status values:

ACTIVE—Access Backup processing is active for this reason.
INACTIVE—Access Backup processing is inactive for this reason.

xxx

The reason for which Access Backup processing can be activated. The following are valid xxx values:

DB2 OBJECT TABLE ERRORS—The backup copy of an object is retrieved when a DB2 object table error occurs while attempting to retrieve the primary copy of the object.
FILE SYSTEM ERRORS—The backup copy of an object is retrieved when a file system error occurs while attempting to retrieve the primary copy of the object.
LOST VOLUMES—The backup copy of an object is retrieved when the optical or tape volume on which the object resides is marked lost or is not-defined.
NOT OPERATIONAL LIBRARIES—The backup copy of an object is retrieved when the primary copy resides on a volume that is in a library that is not operational.
OFFLINE LIBRARIES—The backup copy of an object is retrieved when the primary copy resides on a volume that is in an offline library.
UNREADABLE VOLUMES—The backup copy of an object is retrieved when the primary copy resides on a volume with READABLE=N.

yyy

The indicator of which backup copy, if any, is being used for automatic access to backup processing. The following are valid values for yyy:

1st—Access Backup processing accesses the first backup copy of the object when the primary copy is unavailable for the reason shown in xxx.
2nd—Access Backup processing accesses the second backup copy of the object when the primary copy is unavailable for the reason shown in xxx.
NO—Access Backup processing is inactive for the reason shown in status; therefore, no backup copy is being used.

ssid

Specifies the name of the DB2 subsystem that OAM uses for object support. The subsystem name is from 1 to 4 characters.

group-name

The XCF group name for this OAMplex.

member-name

The XCF member name for this instance of OAM in an OAMplex.

cbroam-parmlib-suffix

This field displays the suffix of the CBROAMxx PARMLIB member that was in effect during OAM initialization.

OAM1 Parms

Displays settings that resulted from the parameters specified for the OAM1 entry in the IEFSSNxx PARMLIB member when the OAM1 subsystem was initialized at IPL time.

Note: Refer to z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support for more information on these parameters.

TIME=xxx

Specifies whether or not the timestamp value in the object directory in DB2 is to be based on GMT or local times.

TIME=GMT Indicates that the timestamp value is based on GMT.
TIME=LOC Indicates that the timestamp value is based on local time.

MSG=xx

Specifies the format for how the OAM message text appears:

MSG=EM Indicates that the message text is in mixed-case English. This is the default.
MSG=EU Indicates that the message text is in uppercase English.

UPD=x

Specifies whether DB2 updates for the pending action date (ODPENDDT) and the last reference date (ODLREFDT) fields should be performed:

UPD=Y Indicates that the ODPENDDT and ODLREFDT fields should be updated on all OSREQ RETRIEVE requests.
Note: The OLDREFDT field is not updated for OSREQ CHANGE requests. This is the default.
UPD=N Indicates that the ODPENDDT and ODLREFDT fields should not be updated for any OSEQ RETRIEVE requests.
Note: The ODLREFDT field is not updated for OSREQ CHANGE requests.
Restriction: If you use UPD=N, you cannot base transition criteria on the time since last use parameter in the ISMF management class definition.
UPD=C Indicates that the ODPENDDT and ODLREFDT fields should be updated on all OSREQ RETRIEVE and on all OSREQ CHANGE requests.
Note: ODLREFDT is not updated when:
- OSREQ RETRIEVE results in RECALL being scheduled, or
- OSREQ RETRIEVE of object currently in RECALL mode.

QB=x

Specifies whether or not an OSREQ QUERY request results in a call into the OAM address space to retrieve the backup retrieval order keys. This specification is at the global level and pertains to all OSREQ QUERY processing.

QB=Y Indicates that OSREQ QUERY requests result in a call into the OAM address space for each backup copy. The OSREQ QUERY will return a complete backup retrieval order key for each backup copy. If a backup copy does not exist, then the OAM address space will not be called and the backup retrieval order key will contain binary zeros. This is the default.
QB=N Indicates that OSREQ QUERY requests will not result in a call into the OAM address space for each backup copy. The backup retrieval order key will contain binary zeros for each backup copy regardless if the backup copy exists or not.

MOS=xxxx

Specifies the maximum object size limit in MB. Valid values are 50–2000. The maximum object size is checked when objects are initially stored through the OSREQ programming interface and is not checked on subsequent retrievals.

OTIS=x

Specifies whether OTIS should wait for JES to completely initialize before OTIS is started:

OTIS=Y Indicates that OTIS will not start until JES is completely initialized.
OTIS=N Indicates that OTIS will start independently from JES. This is the default.

LOB=x

Specifies whether or not OAM exploits DB2 LOB support for large objects that exceed 32 KB (32640 bytes). LOB has the following options:

LOB=A Indicates that, for all storage groups, objects that exceed 32 KB are to be stored in a LOB storage structure when stored to DB2. LOB=A indicates to OAM that the installation has created LOB storage structures and associated V_OSM_LOB_BASE_TBL views for ALL object storage groups defined in the ACDS. This results in optimal performance when you want to store large objects (greater than 32 KB) to DB2, because OAM does not query DB2 to see if the LOB base table view exists. If the LOB base table view does not exist, the large object store fails.
LOB=P Indicates to OAM that the installation has created LOB storage structures and associated V_OSM_LOB_BASE_TBL views for a PARTIAL list of object storage groups defined in the ACDS. However, for object stores to DB2 greater than 256M, the LOB=P designation is treated the same as LOB=A; an attempt to store the object to the LOB base table is made without first checking if the V_OSM_LOB_BASE_TBL view exists.
If the object being stored is less than or equal to 256M and greater than or equal to 32KB, then LOB=P requires OAM to query DB2 to see if the LOB base table view exists for a given object storage group. If the LOB base table view does exist for a given object storage group, large objects are stored in the associated LOB storage structure. If the LOB base table view does not exist, large objects are stored in the 32KB data table.
LOB=N Indicates that objects that exceed 32 KB and less than or equal to 256 MB are to be stored in a 32 KB data table when stored to DB2. Stores will fail for objects that exceed 256 MB. This is the default.

DP=x

Specifies that scope at which deletion-protection is enabled or disabled. If a given object storage group has deletion-protection enabled, then no objects can be deleted from that object storage group prior to the object's expiration date.

DP=A Indicates that deletion-protection is enabled for all object storage groups.
DP=P Indicates that deletion-protection is partially enabled. Specifically, deletion-protection is enabled only for object storage groups that have the OAM Deletion Protection setting defined as ENABLED in ISMF for the object storage group SMS construct.
DP=N Indicates that deletion-protection is not enabled for any object storage group. This is the default.

The following is a sample of DISPLAY SMS,OAM status:

CBR1100I OAM status: 418                                            
OPT. TOT  USE  TOT  USE  AVL  TOT  USE  AVL  TOT  USE  AVL  SCR  REQ
     LIB  LIB  DRV  DRV  DRV  LDR  LDR  LDR  SDR  SDR  SDR  VOL  CT 
       4    0   10    0    0    8    0    0    2    0    0    4    0
TAPE TOT  ONL  TOT  TOT  TOT  TOT   TOT   ONL   AVL   TOTAL         
     LIB  LIB  AL   VL   VCL  ML    DRV   DRV   DRV  SCRTCH         
       6    0    0    0    0    1     0     0     0     107         
There are also 0 VTS distributed libraries defined.                 
CBRUXCUA processing ENABLED.                                        
CBRUXEJC processing ENABLED.                                        
CBRUXENT processing ENABLED.                                        
CBRUXVNL processing ENABLED.                                        
CBRUXSAE processing ENABLED.                                        
CBRUXSAE processing ENABLED for STORE.                              
CBRUXSAE processing ENABLED for RETRIEVE.                           
CBRUXSAE processing ENABLED for QUERY.                              
CBRUXSAE processing ENABLED for CHANGE.                             
CBRUXSAE processing ENABLED for DELETE.                             
EDGTVEXT processing ENABLED.                                        
Access Backup processing ACTIVE for UNREADABLE VOLUMES, using 1st   
backup copy.                                                        
Access Backup processing ACTIVE for OFFLINE LIBRARIES, using 1st    
backup copy.                                                        
Access Backup processing ACTIVE for NOT OPERATIONAL LIBRARIES, using
1st backup copy.                                                    
Access Backup processing ACTIVE for DB2 OBJECT TABLE ERRORS, using  
1st backup copy.                                                    
Access Backup processing ACTIVE for LOST VOLUMES, using 1st backup  
copy.                                                               
Access Backup processing ACTIVE for FILE SYSTEM ERRORS, using 1st   
backup copy.                                                        
Diagnostic messages ACTIVE for OSREQFS. Limit=  10.                 
DB2 SSID:  DB2                                                      
XCF GROUP NAME: -N/A-                                               
XCF MEMBER NAME: -N/A-                                              
CBROAM: 19                                                          
OAM1 Parms: TIME=LOC  MSG=EM  UPD=C  QB=Y                           
            MOS=2000  OTIS=N  LOB=P  DP=P

If both optical and tape libraries are defined in the active SMS configuration, the optical library information is displayed first, followed by the tape library information. For an example of this display for a tape library, see z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries.

The CBRUXSAE installation exit performs security authorization checking for users performing OSREQ transactions on object data. For information on the CBRUXSAE exit, see z/OS DFSMS OAM Application Programmer's Reference.