© Copyright IBM Corp. 2003. All rights reserved. 125
Appendix A. CICS VSAM recovery
(CICSVR) example
DFSMStvs does not perform forward recovery, but it does provide log entries that
allow forward recovery to be done by another program. A number of programs
from independent software vendors may be able to give you this function.
In this appendix, we show how we used the IBM product, CICS VSAM Recovery
or CICSVR. This is the program we used to provide forward recovery capability
for our tests.
We used CICSVR to perform forward recovery for one of our recoverable data
sets. These are the steps we used to test forward recovery:
1. We had taken a backup of the data set using DFSMSdss logical dump.
Figure A-1 on page 126 shows the job that we used to take a dump of the
data set.
Here, the base data set ITSO2.KSDS100 is backed up to
ITSO3.KSDS100.DSDUMP on disk.
A
126 DFSMStvs Application Migration Guide
Figure A-1 DFSMSdss logical dump
2. We ran an update job against our master file, ITSO2.KSDS100. The update
job updated 250,000 records in the data set. It also caused log records to be
written to the forward recovery log.
3. We ran a CICSVR job to scan and register the log of logs. This ensured that
CICSVR knew about our recoverable data set. We ran program DWWAR with
the control statements
LOGOFLOGS REGISTER.
When we first set up CICSVR, it would not show us any VSAM clusters to
forward recover. Scanning the log of logs made our data set appear on the
CICSVR panels, as in Figure A-3 on page 127.
4. After the update job completed, we renamed the data set to simulate data set
loss.
We now had a situation where we simulated the loss of a recoverable data set.
We can perform recovery, starting with the recovery of the dumped data set, and
can then apply log records to recreate the latest version. We used these steps:
1. First, we recovered the data set from our dump copy
ITSO3.KSDS100.DSDUMP to ITSO2.KSDS100. Figure A-2 on page 127
shows the JCL that we ran to restore the data set from the backup copy.
// MSGLEVEL=(1,1),NOTIFY=ITSO3,REGION=0M,USER=ITSO3
//OPT1 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//OUTDD DD DSN=ITSO3.KSDS100.DSDUMP,DISP=(NEW,CATLG),
// UNIT=3390,SPACE=(CYL,(10,5))
//SYSIN DD *
DUMP DATASET ( INCLUDE(ITSO2.KSDS100)) -
OUTDD (OUTDD)
/*
Appendix A. CICS VSAM recovery (CICSVR) example 127
Figure A-2 Step 1 — restoring the recoverable data set
2. We ensured that we had RACF® read authority to the forward recovery logs.
3. Now, we started to use CICSVR to apply the changes from the forward
recovery log. From the CICSVR primary menu, we selected option 1, “List of
VSAM spheres”, which gives the next screen. Now we select the base data
set by typing an
S against it, then we select Utilities and choose option 2,
“Forward recover only”. Figure A-3 shows the resulting panel.
Figure A-3 Step 2 — choosing forward recovery
//RESTORE EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//INDD DD UNIT=3390,VOL=SER=338003,DISP=(SHR),
// DSN=ITSO3.KSDS100.DSDUMP
//SYSIN DD *
REST DATASET (INCLUDE(ITSO2.KSDS100)) -
INDD (INDD)
/*
Administrate Utilities Tools List View Help
------------- .-----------------------------------. ---------------------------
| 2 1. Complete recovery... F4 | Row 1 to 11 of 85
| 2. Forward recover only... F5 |
Select one or | 3. Backout only... F6 | ion.
.-----------------------------------.
Last time RLS RR
S VSAM sphere referenced flag on
S ITSO2.KSDS100 01.093 22:05:43 N
_ ITSO2.KSDS46 01.093 22:05:43 N
_ ITSO2.POSFILE1 01.093 22:05:43 N
_ ITSO2.POSFILE2 01.093 22:05:43 N
_ ITSO2.POSFILE3 01.093 22:05:43 N
_ ITSO2.POSFILE4 01.093 22:05:43 N
_ TVS.BATCH.AA.ACCUNTDB 01.093 22:05:43 N
_ TVS.BATCH.AA.BANKACCT 01.093 22:05:43 N
_ TVS.BATCH.AA.CARDHOLD 01.093 22:05:43 N
_ TVS.BATCH.AA.COMPOSDB 01.093 22:05:43 N
_ TVS.BATCH.AA.CUSTOMER 01.093 22:05:43 N
_ TVS.BATCH.AA.DATAENDB 01.093 22:05:43 N

Get DFSMStvs Application Migration Guide now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.