Migrating from an existing object tape library to another object tape library using OAM's Tape Sublevel 2 support

About this task

To migrate from an existing object tape library to another object tape library using OAM's Tape Sublevel 2 support, follow these steps:

Step 1: To start writing new OAM objects to the new tape library
Step 2: To start transitioning any existing tape OAM object data to the new tape library
Step 3: To move existing OAM backup copies to the new tape library

Step 1: To start writing new OAM objects to the new tape library

Procedure

Create a data class for the new tape sublevel 2 (TSL2) library.

Ensure that the ACS routine for the data class is set up to retain the data class that was set in the CBROAMxx parmlib member. That is, the data class is not changed.

For example,


/******************************************************************************/ 
/* IF OAM OBJECT TAPE DSN, DO NOT SET THE DATA CLASS                          */
/* (DC is set per SETOAM statement in CBROAMxx PARMLIB)                       */
/* If using DSN Name format - you will need to add the Storage groups to the  */  
/* dataset names below.                                                       */ 
/******************************************************************************/ 
IF (&DSN = 'OAM.PRIMARY.DATA') OR 
(&DSN = 'OAM.BACKUP.DATA') OR 
(&DSN = 'OAM.BACKUP2.DATA') THEN 
DO 
      EXIT CODE(0) 
END

Create a storage class for directing objects to the tape sublevel 2 tier. For example, a storage class that is defined with IARS=1, SDR=3, and OSL=2 would equate to TSL2.

Modify the storage class ACS routine to make sure that the routine assigns the new storage class when it receives the data class that OAM specified in the CBROAMxx parmlib member in environment ALLOC.

For example,


/******************************************************************************/ 
/* ALLOC environment (for OAM DSN data class from SETOAM)                     */ 
/******************************************************************************/ 

IF &ACSENVIR = 'ALLOC' then 
DO 
      IF &DATACLAS = ' ' THEN               /* data class is specified        */ 
             SELECT (&DATACLAS)             /* set SC based on data class     */
             WHEN('new_SC')                 /* automated tape library dc      */
                SET &STORCLAS = 'new_SC'    /* set tape library storage class */
             OTHERWISE                      /* invalid dc for alloc           */    
                     /* existing DC logic */ 
		END
END

Create a storage group that includes the new tape library.

Modify the storage group ACS routine so that it assigns the new tape storage group that is defined for the new tape library in environment ALLOC.

For example,


/***************************************************************************/ 
/* ALLOC environment                                                       */
/***************************************************************************/ 

IF &ACSENVIR = 'ALLOC' then 
DO 
      IF &STORCLAS = 'new_SC' THEN      /* If we set the atl storage class */
             SET &STORGRP = 'new_SG'    /* set tape library storage group  */
END

If the existing storage class is the storage class that was originally set for objects on the existing tape library you are transitioning from, then modify the storage class ACS routine in environment CTRANS to assign the new storage class. If you are storing objects directly to the tape storage tier, then also update the storage class ACS routine in environment STORE.

Modify the CBROAMxx parmlib member by updating every object and object backup storage group in the new tape sublevel 2 library that you want to start writing to.

For example,


/****************************************************************************/ 
/* Object storage groups                                                    */
/****************************************************************************/ 

SETOAM STORAGEGROUP(group_name 
TAPEUNITNAME(old_Name)        /* OLD esoteric tape unit name                */  
DATACLASS(old_DC))            /* OLD Data class                             */
L2TAPEUNITNAME(new_Name)      /* NEW Esoteric tape unit name                */
L2DATACLASS(new_DC))          /* NEW Data class                             */ 
...

/****************************************************************************/ 
/* Object Backup storage groups                                             */
/* Note: Object backup storage groups do not transition so they only have   */
/*       one tape unit name and data class                                  */
/****************************************************************************/
 
SETOAM STORAGEGROUP(backup_group_name 
TAPEUNITNAME(new_Name)                     /* NEW esoteric tape unit name   */  
DATACLASS(new_DC))                         /* NEW Data class                */
...

Mark all existing OAM object tape volumes to non-writable to prevent OAM from writing to old tape volumes.
For example,
```
F OAM,UPDATE,VOL,volser,WRITABLE,N 
```
Translate, validate, and activate the updated source control data set (SCDS).
Restart the OAM address space to pick up the new CBROAMxx parmlib update and SCDS changes.

Results

A Db2-only OAM configuration was dynamically replicated to another LPAR. Now writes to tape for new data will go to the new tape library.

Step 2: To start transitioning any existing tape OAM object data to the new tape library

Procedure

Issue an OSREQ CHANGE for each object that needs to be transitioned by updating the storage class to the new tape sublevel 2 storage class. The pending action date (ODPENDDT) is updated to be today, so the next OSMC cycle that runs will see that the object needs to be in tape sublevel 2 (based on ACS routine changes as well). It will then schedule a read from the old media and write to the new media.
The OSREQ CHANGE command can be done in batch. We recommend opening a case to OAM if you would like to use SPUFI for a more expedited approach.
Run OSMC for each storage group.

Results

Now all writes to tape for new data will go to the new sublevel 2 tape library.

Step 3: To move existing OAM backup copies to the new tape library

Procedure

Use the OAM MOVEVOL utility with the DELETE option to move data one volume at a time and to delete the old volume from OAM's knowledge.

Results

Once all objects have been moved, the volume is returned to scratch.