OAM address space
An OAM address space is used to perform a subset of OAM processing. Start an OAM address
space if you plan to use the file system sublevel, optical devices, tape devices
, or cloud storage
for storing objects and OSMC functions or if you plan to
delete objects within your data storage environment.
Restrictions for OAM address spaces in a classic OAM configuration
- Only one OAM address space can be active in the z/OS system.
- Only one Db2 subsystem can be associated with the active OAM address space.
- Optical devices can only be directly accessed by the owning OAM address space. However, requests for the optical devices can be shipped to the OAM in an OAMplex that owns the optical devices by using the XCF messaging service.
- Specifying a region size other than 0 MB on the OAM-started procedure JCL can result in storage shortage abends, especially during an OSMC cycle.
These restrictions apply regardless of whether the address space is part of an OAMplex.
Restrictions for OAM address spaces in a multiple OAM configuration
- Only one tape library OAM address space can be active in the z/OS system. For more information on a tape library address space, see z/OS DFSMS OAM Planning, Installation, and Storage Administration Guide for Tape Libraries.
- Up to five object OAM address spaces can be active in the z/OS
system.
- Each object OAM address space must be associated with a unique Db2 subsystem.
- A unique PROCLIB member with a unique name (OAMA, OAMB) is recommended for each OAM instance. A single member of PROCLIB can be used and started with a unique task identifier for each address space (S OAM.OAMA and S OAM.OAMB), but a unique value for the D= keyword is required for each address space. This approach requires specifying the D= value on the START command.
- The optical level of the OAM storage hierarchy is not supported.
- Specifying a region size other than 0 MB on the OAM-started procedure JCL can result in storage shortage abends, especially during an OSMC cycle.
These restrictions apply regardless of whether the address space is part of an OAMplex.