3. Installation › 3.8 Installation Checklists › 3.8.5 Split an Existing Database Unit › 3.8.5.1 Existing Database Split Checklist

3.8.5.1 Existing Database Split Checklist

__  1. Suspend Operation

       Suspend production operations for the unit database by
       using the Operational Status and Tracking SUSPEND
       command in MWF to deactivate production scheduling.

__  2. Back Up Existing Database Unit


       Use the Operational Status and Tracking RESUME,
       BACKUP, and SUSPEND commands in MWF to enable, backup,
       and block CA MICS operational jobs respectively.

       Ensure that the backup job completed with a condition
       code of zero and the data sets were correctly
       cataloged.

       +---------------------------------------------------+
       | Reference(s): Section 4.3.4.4                     |
       +---------------------------------------------------+

__  3. Save Existing RESTORE Job

       Save a copy of the existing RESTORE job.

       This step is necessary to preserve the old version of
       the RESTORE job in case a restore is needed from the
       old database unit structure. For example, you can use
       the ISPF copy utility or ISPF edit to copy
       'prefix.MICS.CNTL(RESTORE)' to
       'prefix.MICS.CNTL(RSTROLD)'.  The RESTORE job in
       prefix.MICS.CNTL will be regenerated by JCLGENE.

__  4. Edit DBSPLIT

       Edit prefix.MICS.PARMS(DBSPLIT) to add information
       areas and DDnames.

       +---------------------------------------------------+
       | Reference(s): Section 2.3.3.3.2.4                 |
       +---------------------------------------------------+

__  5. Execute JCLGENE

       Generate the jobs affected by DBSPLIT.  Submit the
       following job:

         'prefix.MICS.CNTL(JCLGENE)'

       +---------------------------------------------------+
       | Reference(s): Section 2.3.3.1.1 and 3.5.3.3       |
       +---------------------------------------------------+

__  6. Execute GDGSGEN


       Update/create GDG entries for installed products in
       the OS CVOL or VSAM catalog.  Submit the following
       job:

         'prefix.MICS.CNTL(GDGSGEN)'

       +---------------------------------------------------+
       | Reference(s): Section 3.5.6.3                     |
       +---------------------------------------------------+

__  7. Execute PROCJOB3

       Move CA MICS database set-up PROCS to the installation
       PROCLIB by submitting the following job:

         'prefix.MICS.CNTL(PROCJOB3)'

       +---------------------------------------------------+
       | Reference(s): Section 3.5.4                       |
       +---------------------------------------------------+

__  8. Allocate Additional SAS Data Libraries

       Allocate the additional SAS data libraries needed for
       a split database unit.

       The ALLOCATE job contains JCL statements for
       allocating the new database files in addition to the
       existing database files.  You can allocate your new
       database files by making a copy of the ALLOCATE job,
       deleting all DISP=(NEW,CATLG) JCL statements that
       refer to existing data sets, leaving just the DD
       statements to allocate and initialize your new
       database files.  Then fill in the UNIT, VOL=SER=,
       SPACE=, and/or other data set allocation parameters as
       required for your installation and database space
       requirements.  Then submit the tailored job to
       allocate and initialize the data sets.

       +---------------------------------------------------+
       | Reference(s): Section 3.5.6.2                     |
       +---------------------------------------------------+

__  9. Move Information Area Files

       Move information area files to new data libraries.

       Use PROC COPY to copy all of the files that belong to
       the information areas in these new libraries to the
       new data libraries (see DBSPLIT definition).  This
       copy operation can be done using a " SELECT iii:  ; "
       statement with PROC COPY, where iii is the information
       area ID.

__ 10. Delete Information Area Files

       Delete information area files in old data libraries.

       When you have verified that all the necessary files
       have been moved successfully to the new SAS data
       libraries, delete the original versions from the old
       data libraries using PROC DATASETS.

__ 11. Back Up New Database Unit Structure

       Use the Operational Status and Tracking RESUME,
       BACKUP, and SUSPEND commands in MWF to enable, backup,
       and block CA MICS operational jobs respectively.

       Ensure that the backup job completed with a condition
       code of zero and the data sets were correctly
       cataloged.

       +---------------------------------------------------+
       | Reference(s): Section 4.3.4.4                     |
       +---------------------------------------------------+

__ 12. Verify User SAS Code

       Change any user SAS code that refers to CA MICS files
       by using explicit DDnames to use &diiit macro
       variables instead.

       +---------------------------------------------------+
       | Reference(s): SAS Documentation                   |
       +---------------------------------------------------+

__ 13. Resume Operations


       Enable CA MICS operational jobs for this unit
       database.  Use the Operational Status and Tracking
       RESUME command in MWF to enable CA MICS operational
       jobs.

__ 14. Resume Daily Processing

       Use the Operational Status and Tracking DAILY command
       in MWF to resume daily processing.

       +---------------------------------------------------+
       | Reference(s): Section 3.5.7                       |
       +---------------------------------------------------+