CBR1100I   OAM status:

Explanation

The OAM status is:
Table 1. OAM status
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
     aaa  bbb  ccc  ddd  eee  fff  ggg   hhh  iii  jjj  kkk  lll  mmm
TAPE TOT  ONL  TOT  TOT  TOT  TOT   TOT   ONL   AVL    TOTAL
     LIB  LIB  AL   VL   VCL  ML    DRV   DRV   DRV   SCRTCH
     nnn  ooo  ppp  qqq  rrr  sss ttttt uuuuu vvvvv wwwwwwww
exit-name processing {ENABLED|DISABLED|BYPASSED|OPERATOR DISABLED}.
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.
Access Backup {ACTIVE|INACTIVE}for reason, using {1st|2nd|no} backup copy.
Diagnostic messages {ACTIVE|INACTIVE} for OSREQFS. Limit=nnnn.
DB2 SSID: db2-ssid
XCF GROUP NAME: group-name
XCF MEMBER NAME: member-name
CBROAM: cbroam-parmlib-suffix
OAM1 Parms: TIME=xxx  MSG=xx  UPD=x  QB=x    
            MOS=xxxx  OTIS=x  LOB=x  DP=x
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
     aaa  bbb  ccc  ddd  eee  fff  ggg   hhh  iii  jjj  kkk  lll  mmm
TAPE TOT  ONL  TOT  TOT  TOT  TOT  TOT   ONL  AVL  TOTAL
     LIB  LIB  AL   VL   VCL  ML   DRV   DRV  DRV  SCRTCH
     nnn  ooo  ppp  qqq  rrr  sss tttt  uuuu vvvv wwwwwww
exit-name processing {ENABLED|DISABLED|BYPASSED|OPERATOR DISABLED}.
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.
Access Backup {ACTIVE|INACTIVE}for reason, using {1st|2nd|no} backup copy.
DB2 SSID: db2-ssid
XCF GROUP NAME: group-name
XCF MEMBER NAME: member-name
CBROAM: cbroam-parmlib-suffix
OAM1 Parms: TIME=xxx  MSG=xx  UPD=x  QB=x    
            MOS=xxxx  OTIS=x  LOB=x  DP=x
The operator has entered the following command: 
D SMS,OAM
A display of OAM address space status has been generated. If both optical and tape libraries have been defined in the SMS configuration, the sample display above will be generated. Otherwise, only the data for the library type defined will be generated.
For an optical library, the fields displayed in the data line of the multiline message are 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 currently 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 stand-alone optical drives in the configuration.
jjj
Number of usable stand-alone optical drives.
kkk
Number of available stand-alone optical drives.
lll
Number of scratch optical volumes in the optical configuration database.
mmm
Total number of read requests waiting to be scheduled.
For a tape library, the fields displayed in the data line of the multiline message are as follows:
nnn
Total number of tape libraries defined in the active SMS configuration (excluding the Peer-to-Peer VTS distributed libraries) that are connected to the current system (referred to in the following explanations as a connected tape library). The current system is the system on which the OAM command is entered. For the number of distributed libraries that are defined to the system, refer to the status line towards the bottom of the display.
ooo
Number of connected tape libraries that are online (excluding the Peer-to- VTS distributed libraries).
ppp
Number of connected automated tape library dataservers (non-virtual tape servers).
qqq
Number of connected virtual tape servers (excluding the Peer-to-Peer VTS tape libraries).
rrr
Number of connected Peer-to-Peer VTS composite libraries.
sss
Number of connected manual tape libraries.
tttt
Total number of tape drives, known to the current system, residing in the connected tape libraries.
uuuu
Total number of tape drives, known to the current system and residing in the connected tape libraries, that are online.
vvvv
Total number of tape drives, known to the current system and residing in the connected tape libraries, that are online and not allocated.
wwwwwww
Total number of scratch volumes of all media types in the connected tape libraries.

If there are Peer-to-Peer VTS subsystems defined to the system, the following status line will be displayed reflecting the number of distributed libraries that are associated with the composite libraries above:

There are also numvdl-lib VTS distributed libraries defined.
For OAM installation exits, the fields displayed in the status messages are as follows:
exit-name
The name of the exit for which status is being displayed. This can be CBRUXENT, CBRUXEJC, CBRUXCUA, CBRUXVNL, or CBRUXSAE or EDGTVEXT.
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 CBRUXCUA, the exit is disabled for CBRXLCS FUNC=CUA PRIVATE to SCRATCH requests only. For EDGTVEXT, OAM continues releasing object tape volumes from the OAM inventory.
BYPASSED
For CBRUXVNL, either the exit returned a return 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
For CBRUXENT, the operator has requested that cartridge entry processing be disabled by issuing the LIBRARY DISABLE, CBRUXENT command. Cartridge entry processing can only be enabled by issuing a LIBRARY RESET,CBRUXENT command, or a system IPL.

For CBRUXVNL, the operator has requested that the volume not in library installation exit be disabled by issuing the LIBRARY DISABLE, CBRUXVNL command. The CBRUXVNL installation exit is not invoked during job processing. Use the LIBRARY RESET, CBRUXVNL command or IPL the system to reactivate the invoking of the CBRUXVNL installation exit.

If the CBRUXSAE user exit is in ENABLED mode, 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.

For OAM Access Backup processing, the fields displayed in the status messages are as follows:

reason
The reason for which Access Backup processing can be activated. This can be:
  • UNREADABLE VOLUMES
  • OFFLINE LIBRARIES
  • NOT OPERATIONAL LIBRARIES
  • DB2® OBJECT TABLE ERRORS
  • FILE SYSTEM ERRORS
  • LOST VOLUMES
ACTIVE
Access Backup processing is active for one of these reasons.
INACTIVE
Access Backup processing is inactive for one of these reasons.
1st
Access Backup processing accesses the first backup copy of the object when the primary copy is unavailable for one of these reasons.
2nd
Access Backup processing accesses the second backup copy of the object when the primary copy is unavailable for one of these reasons.
no
Access Backup processing is inactive for one of these reasons; therefore, no backup copy is being used.
For OAM diagnostic messages processing, the fields displayed in the status messages are as follows:
ACTIVE
Diagnostic messages will be issued for file system related errors originating from OSREQ requests
INACTIVE
Diagnostic messages will not be issued for file system related errors originating from OSREQ requests
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

If a DB2 subsystem name was specified for OAM object support either in the IGDSMSxx member of PARMLIB or in response to a WTOR during OAM initialization, the following information is displayed:

db2-ssid
The DB2 subsystem used by OAM for object support.
For OAM XCF processing, the fields displayed in the status messages are as follows:
group-name
The XCF group name for this OAMplex, if a group name and member name were specified in the CBROAMxx PARMLIB member when OAM was initialized. If OAM is not running as part of an OAMplex, the value of this field will be ‘N/A’.
member-name
The XCF member name for this instance of OAM in an OAMplex, if a member name and group name were specified in the CBROAMxx PARMLIB member when OAM was initialized. If OAM is not running as part of an OAMplex, the value of this field will be ‘N/A’.
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: See z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Object Support for more information on these parameters.
TIME=xxx specifies whether the timestamp value in the object directory in DB2 is to be based on GMT. If this option is omitted, or if any value other than GMT is specified, the object directory time stamp in DB2 is based on local time.
  • 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 ODLREFDT 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 OSREQ RETRIEVE requests.
    Note: The ODLREFDT field is not updated for OSREQ CHANGE requests.

    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.
QB=x specifies whether 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 returns a complete backup retrieval order key for each backup copy. If a backup copy does not exist, the OAM address space is not called, and the backup retrieval order key contains binary zeros. This is the default.
  • QB=N indicates that OSREQ QUERY requests do not result in a call into the OAM address space for each backup copy. The backup retrieval order key contains 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. If this keyword is omitted, the maximum supported object size remains at 50MB. 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 does not start until JES is completely initialized.
  • OTIS=N indicates that OTIS starts independently from JES. This is the default.
LOB=x specifies whether 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. This requires OAM to query DB2 to see if the LOB base table view exists for a given object storage group for each large object stored. 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 32 KB data table.
  • LOB=N indicates that objects that exceed 32 KB and that are less than or equal to 256 MB are to be stored in a 32 KB data table when stored to DB2. Stores fail for objects that exceed 256 MB. This is the default.
DP=x specifies the scope at which deletion-protection is enabled or disabled. If a given object storage group has deletion-protection enabled, no objects can be deleted from that object storage group before the expiration date of the object.
  • 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 enabled for no object storage groups. This is the default.

System action

None.

Source

Object Access Method (OAM)

Routing Code

-

Descriptor Code

5,8,9

Parent topic: CBR messages