12. INSTALLATION › 12.2 Backups, Restores, and Compression
12.2 Backups, Restores, and Compression
PRIVATE CAPACITY PLANNING DATABASE BACKUP
Your private capacity planning database is NOT backed up as
part of the CA MICS primary unit database backup. For this
reason you need to run your own backup job periodically to
back up both your private capacity planning database SAS data
set and the ISPF tables that are essential to the operation
of the CA MICS Capacity Planner. The frequency with which you
run the backup job depends on how often you update your
capacity planning database files and how often you create and
save analysis inquiries. In general, if you update your
capacity planning database files weekly, you should run your
backup job weekly. If you run your updates monthly, you
should run your backup job monthly.
A number of methods are possible for backing up your private
capacity planning database SAS data set and the
corresponding ISPF tables. The checklist and sample JCL
below provide one method for accomplishing the backup to a
generation data set.
___ 1. You need to know the data set name of your private
capacity planning database file. If you already know
the data set name, proceed to Step 7 of this
checklist. Otherwise, access the main CA MICS
Workstation Facility (MWF) screen as described in
Chapter 1 of this guide. Select Option 4,
Management Support Applications (APPL)
___ 2. From the Management Support Applications screen,
select Option 3, Capacity Planning.
___ 3. From the Capacity Planning screen, select Option 0,
MICF Options.
___ 4. From the MICF Options screen, select Option 6, Data
Set Allocation Parameters.
___ 5. From the Data Set Allocation screen, select the row
identified as CAPACITY by placing an S in the Cmd
column of this row. The resulting screen displays
the data set name and the allocation parameters that
you will use to allocate your private capacity
planning database file.
___ 6. Record the data set name for use in the JCL shown in
Figures 12-2 and 12-3.
___ 7. If you have not already defined the generation data
sets for backing up your private capacity planning
SAS data set and the corresponding ISPF tables, you
need to do so now. You only need to execute this
step the first time you back up your capacity
planning database file. Figure 12-2 shows one
method of doing so for a VSAM catalog structure.
//DEFINGDG EXEC PGM=IDCAMS
//*
//* DEFINE VSAM BACKUP GDG FOR PRIVATE CAPACITY FILE
//*
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE GDG -
(NAME(userid.MICS.BACKUP.CAPACITY) -
SCRATCH -
LIMIT(3) )
DEFINE GDG -
(NAME(userid.MICS.BACKUP.TABLES) -
SCRATCH -
LIMIT(3) )
Figure 12-2. JCL to Define Backup GDGs for Private Files
___ 8. You are now ready to execute the JCL to back up your
private capacity planning database file and the
corresponding ISPF tables. You may use the JCL shown
in Figure 12-3 for this purpose. Note that this is a
two-step job and that you can make several
assumptions.
Refer to the first step, BKUPSAS, in Figure 12-3. If
the name of the SAS PROC at your installation is not
SAS, change the JCL to reflect the correct name.
Also, if the name of the private capacity planning
SAS data set that you identified in Step 6 of this
checklist does not match the format shown below for
the CAPACITY DD statement, then change the JCL to
reflect the correct name. The data set named on the
BKUPCAP DD statement refers to a generation data set
that you either defined previously or that you
defined by executing the JCL in Step 7 of this
checklist. As with the CAPACITY DD statement, ensure
that the data set name on the BKUPCAP DD statement
reflects the correct name at your installation.
Refer to the second step, BKUPTBL, in Figure 12-3.
If the name of your private ISPF table library does
not follow the format shown on the SYSUT1 DD
statement, change the JCL to reflect the correct
name. The data set name on the SYSUT2 DD statement
refers to a generation data set that you either
defined previously or you defined by executing the
JCL in Step 7. As with the SYSUT1 DD statement,
ensure that the data set name on the SYSUT2 DD
statement reflects the correct name at your
installation.
//BKUPSAS EXEC MICSNDBx
//*
//* PRIVATE CAPACITY PLANNING DATABASE SAS DATA SET BACKUP
//*
//CAPACITY DD DSN=userid.MICS.USER.CAPACITY,DISP=SHR
//*
//BKUPCAP DD DSN=userid.MICS.BACKUP.CAPACITY(+1),
// DISP=(NEW,CATLG,DELETE),UNIT=unit,
// DCB=(userid.MICS.USER.CAPACITY),
// LABEL=(1,RETPD=360)
//SYSIN DD *
PROC COPY IN=CAPACITY OUT=BKUPCAP; RUN;
/*
//BKUPTBL EXEC PGM=IEBCOPY
//*
//* PRIVATE CAPACITY PLANNING ISPF TABLE BACKUP
//*
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DISP=SHR,DSN=userid.MICS.USER.TABLES
//SYSUT2 DD DSN=userid.MICS.BACKUP.TABLES(+1),
// DISP=(NEW,CATLG,DELETE),UNIT=unit,
// DCB=(userid.MICS.USER.TABLES),
// LABEL=(1,RETPD=360)
//SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(3))
//SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(3))
//SYSIN DD *
COPY INDD=SYSUT1,OUTDD=SYSUT2
Figure 12-3. Private Capacity Planning Backup JCL
___ 9. You have now backed up your private capacity planning
database file SAS data set and the corresponding
ISPF tables.
PRIVATE CAPACITY PLANNING DATABASE RESTORE
If you find it necessary to restore your private capacity
planning database file, you may do so by executing the sample
JCL shown in Figure 12-4. As with the backup job described
above, you can make a number of assumptions about data set
and PROC names at your installation. Review the discussion
above and ensure that the PROC and data set names at your
installation are correctly reflected in the following JCL
before submitting the job.
//RSTRSAS EXEC MICSNDBx
//*
//*PRIVATE CAPACITY PLANNING DATABASE SAS DATA SET RESTORE
//*
//CAPACITY DD DSN=userid.MICS.USER.CAPACITY,DISP=OLD
//*
//BKUPCAP DD DSN=userid.MICS.BACKUP.CAPACITY(0),
// DISP=OLD
//SYSIN DD *
PROC COPY IN=BKUPCAP OUT=CAPACITY; RUN;
/*
//RSTRTBL EXEC PGM=IEBCOPY
//*
//*PRIVATE CAPACITY PLANNING ISPF TABLE RESTORE
//*
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=userid.MICS.BACKUP.TABLES(0),
// DISP=OLD
//SYSUT2 DD DISP=SHR,DSN=userid.MICS.USER.TABLES
//SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(3))
//SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(3))
//SYSIN DD *
COPY INDD=SYSUT1,OUTDD=SYSUT2
Figure 12-4. Private Capacity Planning Restore JCL
PRIVATE CAPACITY PLANNING DATABASE COMPRESSION
If you find it necessary to compress your private capacity
database files containing the historical observations
(CAPxxxnn), where xxx is the file identifier and nn denotes a
cycle number, you may do so by executing sample JCL shown in
Figure 12-5.
This JCL first creates a temporary SAS data set. The first
PROC COPY will copy all historical files from your private
capacity database into the temporary data set. The second
PROC COPY will copy and compress all files back into your
private capacity database.
Review your SASLOG to determine your compression savings for
the entire capacity database. In some cases, a compressed SAS
file may take more space than if it were not compressed. If
you determine that compression is not a good option for your
private capacity database, rerun the compression JCL, setting
the COMPRESS option to COMPRESS=NO. Running this job will
uncompress all your private capacity historical database
files.
As with the backup & restore jobs described above, you can
make a number of assumptions about data set and PROC names at
your installation. Review the discussion above and ensure
that the PROC and data set names at your installation are
correctly reflected in the following JCL before submitting
the job.
//CMPRSPR EXEC MICSNDBx
//*
//*PRIVATE CAPACITY PLANNING DATABASE COMPRESSION
//*
//CAPACITY DD DSN=userid.MICS.USER.CAPACITY,DISP=OLD
//*
//TEMPCAP DD DSN=userid.MICS.TEMP.CAPACITY,
// DISP=(NEW,DELETE,DELETE),UNIT=unit,
// DCB=(userid.MICS.USER.CAPACITY),
// SPACE=(CYL,(5,2))
//SYSIN DD *
PROC COPY IN=CAPACITY OUT=TEMPCAP;
SELECT CAP: ; RUN;
OPTIONS COMPRESS=YES;
PROC COPY IN=TEMPCAP OUT=CAPACITY NOCLONE;
SELECT CAP: ; RUN;
/*
Figure 12-5. Private Capacity Planning Compression JCL
NOTE:
To turn off compression during a capacity database
initialization or subsequent database update, modify the SAS
macro variable CAPCMPRS=YES in shared.prefix.SOURCE($CAPMSTR)
to CAPCMPRS=NO;
SHARED CAPACITY PLANNING DATABASE BACKUP AND RESTORE
The CA MICS shared capacity planning database and its
associated tables are backed up whenever the CA MICS primary
unit database backup job is executed. The JCL required to
restore the shared capacity planning database and the tables
is shown in Figure 12-6.
*************************************************************
* WARNING: This restore process will also restore tables *
* which are used in controlling and maintaining the entire *
* CA MICS system. *
* *
* YOU SHOULD NOT PERFORM THIS YOURSELF, BUT SHOULD ASK THE *
* CA MICS SYSTEM ADMINISTRATOR TO PERFORM IT FOR YOU AFTER *
* CONFIRMING THAT THIS RESTORE PROCESS WILL NOT DESTROY ANY *
* RECENT MAINTENANCE, SHARED MICF INQUIRIES, OR SHARED MICF *
* CATALOGED REPORTS THAT THE ADMINISTRATOR HAS APPLIED TO *
* THE SYSTEM. *
* *
* If you need to restore only a few tables describing *
* shared files or shared inquiries, you should call *
* CA MICS Product Support *
*************************************************************
Use the MICSNDBx cataloged procedure to execute the program,
where x is the database identifier of the primary CA MICS
unit database.
//RSTRSAS EXEC MICSNDBx
//*
//* SHARED CAPACITY PLANNING DATABASE RESTORE
//*
//CAPACITY DD DSN=sharedprefix.MICS.CAPACITY,DISP=OLD
//*
//BKUPCAP DD DSN=tapeprefix.MICS.BACKUP.CAPACITY(0),
// DISP=OLD
//SYSIN DD *
PROC COPY OUT=CAPACITY IN=BKUPCAP; RUN;
/*
//RSTRTLIB EXEC PGM=IEBCOPY
//*
//*SHARED CAPACITY PLANNING ISPF TABLE RESTORE
//*
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=tapeprefix.MICS.BACKUP.ISPTLIB(0),
// DISP=OLD
//SYSUT2 DD DISP=OLD,DSN=sharedprefix.MICS.ISPTLIB
//SYSUT3 DD UNIT=SYSDA,SPACE=(TRK,(3))
//SYSUT4 DD UNIT=SYSDA,SPACE=(TRK,(3))
//SYSIN DD *
COPY INDD=SYSUT1,OUTDD=SYSUT2
//
Figure 12-6. Shared Capacity Planning Restore JCL
SHARED CAPACITY PLANNING DATABASE COMPRESSION
Copyright © 2014 CA.
All rights reserved.
|
|