Example 7: Using the COPY Command to Convert to SMS

Example 7 shows non-SMS-managed volumes that are converted to SMS-managed volumes. It is a two-step process.

//JOB9      JOB  accounting information,REGION=nnnnK
//STEP1    EXEC PGM=ADRDSSU
//SYSPRINT  DD   SYSOUT=*
//SYSIN     DD   *
 COPY  -
   DS(INC(**))  -
       LOGINDYNAM ( -
           (338001) -
           (338002) -
           ) -
       STORCLAS(DB2PERF) -
       MGMTCLAS(DBBACKUP) -
       BYPASSACS(**) -
       DELETE -
       PURGE
/*

In step 1 of Example 7, all data sets on the non-SMS-managed volumes 338001 and 338002 are copied to SMS-managed volumes on the system. DELETE and PURGE processing is used to avoid duplicate catalog entries. ACS routines are not invoked to determine the target data set classes for this copy operation. Instead, users provide storage and management classes with the STORCLAS and MGMTCLAS keywords. In addition, users can suppress calls made to the ACS routines with the BYPASSACS(**) keyword. All data sets that are supported by SMS are given these new storage and management classes. All data sets that cannot be SMS-managed (for example, unmovable data sets) are not copied.

//JOB9      JOB  accounting information,REGION=nnnnK
//STEP2    EXEC PGM=ADRDSSU
//SYSPRINT  DD   SYSOUT=*
//SYSIN     DD   *
 COPY  -
   DS(INC(**))  -
       LOGINDYNAM ( -
           (338001) -
           (338002) -
           ) -
       RENUNC(AUG0387)
/*

In step 2 of Example 7, all data sets on the non-SMS-managed volumes 338001 and 338002 are copied to SMS-managed volumes on the system. The RENUNC command is used to avoid duplicate catalog entries. The ACS routines select a target storage and management class for each data set. Those data sets that cannot be SMS-managed (storage class ACS routine returns a null storage class) are not copied because no output volume is specified. Each data set that is copied is given a new high-level qualifier (AUG0387) and automatically cataloged.