Shipping requests to another system requires that OAM obtain storage
for that object on the receiving system. To ensure that the OAM address
space does not run out of virtual storage when the maximum object
size is expanded above 50MB (with the MOS keyword in the OAM1 statement
of the IEFSSNxx parmlib member) the following limitations are in effect:
- Tape RETRIEVE requests for an object larger than 50MB will not
be shipped to the system in which the volume is currently mounted.
Instead, they will wait to be processed on the system where the request
originated. If the originating system is not capable of honoring the
request, the read request will fail on that system. To avoid problems,
ensure that all systems in the OAMplex are capable of honoring the
request.
- Optical RETRIEVE and STORE requests for objects larger than 50MB
must be processed on the system to which the optical library and drives
are attached. If not, OAM will fail the request with return code 12,
reason code X'0813'.
When planning for data objects larger than 50MB in an OAMplex,
consider storing and processing them only on disk (using DB2 tables
or a file system) or on tape.