Adding objects to the object storage hierarchy

OAM provides these functions for adding objects to the object storage hierarchy:

STORE function: STORE can be used for objects whose size is less than or equal to 256 megabytes that are to be written to the disk, tape, or optical levels of the storage hierarchy. STORE processing requires that the entire object be kept in storage. See STORE function for more information.
Store Sequence functions: Store Sequence can be used for objects whose size is greater than 50 megabytes that are to be written to the disk or tape (but not optical) levels of the storage hierarchy. Store Sequence processing handles objects in smaller chunks, rather than having the entire object in storage (as required by STORE processing), which can reduce the storage requirements for an application. See STOREBEG—Beginning a Store Sequence operation, STOREPRT—Storing an individual part in a Store Sequence operation, and STOREEND—Ending a Store Sequence operation for more information.

The Store Sequence functions must be used when writing objects whose size is greater than 256 megabytes to disk or tape.

Objects whose size is greater than 50 megabytes and less than or equal to 256 megabytes can be written to disk or tape using either the STORE function or Store Sequence functions, thus providing flexibility when storing such objects.

When storing objects to DB2, Store Sequence processing always writes the objects to a LOB table. If LOB=N is specified on the OAM1 entry in the IEFSSNxx parmlib member, or if a LOB storage structure does not exist for the target object storage group, then an attempt to do a Store Sequence to DB2 will fail.