There are some restrictions with an OAMplex that you should keep
in mind:
- Any instance of OAM running on a system in a Parallel Sysplex
that is not running in XCF mode cannot share any resources (optical
libraries, optical drives, optical volumes, or tape volumes for object
data) that another instance of OAM owns.
- Any OAM not running in XCF mode cannot share its DB2 databases
with any other instances of OAM.
- Optical libraries that are defined in a source control data set
(SCDS) as connected to a system where OAM is not running in XCF mode
must be logically connected to only that system.
- When you define optical libraries in an SCDS as logically connected
to multiple systems, all instances of OAM on those systems must be
part of a single OAMplex.
- If an OAM DB2 database is being shared, the catalog used for the
OAM collection names must also be shared.
- See OAMplex and file systems for additional
restrictions on using file systems within an OAMplex.
It is important that these restrictions be implemented and adhered
to. OAM cannot detect or prohibit processing that does not conform
to these standards, so unexpected results can occur if these restrictions
are not strictly enforced.