You can direct OAM to create a first and a second backup copy of objects using the existing NUMBER OF BACKUP VERSIONS (DATA SET EXISTS) field that is located in the SMS management class definition. OAM uses this field to determine how many backup copies of an object are to be made when OSMC processing is done for an object's storage group, if there are SETOSMC statements in the CBROAMxx member of PARMLIB indicating that second backup copies are to be created. See page Defining management classes for the specifics of defining this field.

An Object Backup storage group can serve as either a first backup storage group, or as a second backup storage group, but not both. OAM fails initialization if SETOSMC specifies the same Object Backup storage group name as both a first backup storage group and a second backup storage group.

Assigning Object Backup storage groups differs from assigning the Object storage group in that you must use SETOSMC statements to indicate that you want the second backup copy stored in an Object Backup storage group that is not the default Object Backup storage group. If you do not provide SETOSMC statements, then OAM does not process second backup copies of objects.

See Displaying SETDISK, SETOAM, SETOPT, SETOSMC, and SETTLIB parameters for the specifics of assigning Object Backup storage groups using SETOSMC statements.