Get the backup information from a copy of the files dataset

Products

• Disk Backup and Restore - MVS
• DISK BACKUP AND RESTORE- ADD-ON OPTIO
• DISK BACKUP AND RESTORE

Issue/Introduction

Several data sets were deleted due to wrongly set expiration date modified.
We would like to restore them and for this we would like to know how can we get the backup information from a copy of the files data set or in our case the Datacom database.

Environment

Release: Disk-Backup and Restore 12.5

Resolution

Collect the data needed:

Several points can help:

• DMSAR STC LOG or JOB

Can be used to find the current Disk load libraries and parmlib. Locate the following DDs:

• STEPLIB - It should contain the Datacom load libraries and Disk ones. If no STEPLIB, go to the result of D PROG,LNKLST MVS command and look for Disk load library.
• PARMLIB - It is the Disk one DISKR125.CCUWPARM or user PARMLIB, so concatenate USER parmlib first and Disk second in JCLs/Procs

The Files reload operation:

 
You will have to run the following JCL in sequence:
DBDEF
DBINIT
DBLOAD
DBADD
ISPF Rexx
 
Verify your jobs have updated the sample JCL with the new DBID number. You must have OPERATIONS level or STORAGE ADMIN to perform these jobs or security violation will occur 

• DBDEF

This job defines the DBID to Datacom and create a base GDG. In case of rerun, first delete manually the GDG base created and second add DELETE as parm to the exec as follow:
//   DELOPT=',DELETE',
The Datacom DDUPDATE step will create also a backup of its generated contents into the library specified by
//   P='DISKR125.CCUWJCL',
  
Verify the proc use first and then that you use the new decided DBID number. If needed, modify the PROC you are pointing using the
//SAMS JCLLIB ORDER=DISKR125.CCUWPROC
to match customer names. Try as much as possible to overwrite all using the JCL instead of modifying the PROC used or create a new one and use the new PROC name.
 

• DBINIT

This job allocates and defines the Datacom libraries for the new FILES. Specify a correct space to recover the data using the actual Datacom FILES allocation information.
//   DMSSPACE='(CYL,(40,25))',
//   IXXSPACE='(CYL,(10,10))',
 
Refer to Files Data Set (FDS) Capacity for space estimation if needed:

 

In case of restarting from scratch, run DBDELETE 

• DBLOAD

This job reloads the Backup Datacom FILES data into the new allocated Datacom Files. Verify that the DD DATAIN points to the backup copy to restore.
//DATAIN    DD   DISP=(OLD,KEEP),DSN=DISKR125.DMS650.BACKUP.G01020V00
Change the DBID 650 in all places of the SYSIN (not change anything else) to match your new DBID number.  

• DBADD

This job defines the Backup Datacom FILES data into Disk ADSDC650 load module. The Disk Files data set name associated is to be define by you .
A tip, add the DBID number into it so the customer knows which FILES it is pointing to.
 

• ISPF Rexx sample

/* REXX */
PANEL="DISKR125.CCUWPNL0"                                                 
MSG="DISKR125.CCUWMSG0"
SKEL="DISKR125.CCUWSKL0"
PRM0="DISKR125.USERPARM" 
PRM1="DISKR125.CCUWPARM"
LOAD="DISKR125.CCUWLINK"
LOAD1="DISKR125.CCUWLOAD"
LOAD2="AD14.CUSLIB"
LOAD3="AD14.CAAXLOAD"
ADDRESS TSO
"ALLOCATE FILE("FILES") DA("DISKR125.FILES.DBxxx") SHR REUSE"
"ALLOCATE FILE("PARMLIB") DA('"PRM0"','"PRM1"') SHR REUSE"
"ALLOCATE FILE("DMSOSLIB") DA('"LOAD"','"LOAD1"','"LOAD2"','"LOAD3"')
SHR REUSE"
ADDRESS ISPEXEC
"LIBDEF ISPPLIB DATASET ID('"PANEL"')"
"LIBDEF ISPMLIB DATASET ID('"MSG"')"
"LIBDEF ISPSLIB DATASET ID('"SKEL"')"
"LIBDEF ISPLLIB DATASET ID('"LOAD"','"LOAD1"','"LOAD2"','"LOAD3"')"
"SELECT PGM(ADSSP202) PARM(ADSSP044) NEWAPPL(DMSB) PASSLIB"
"LIBDEF ISPPLIB"
"LIBDEF ISPMLIB"
"LIBDEF ISPSLIB"
"LIBDEF ISPLLIB"
ADDRESS TSO
"FREE FILE("FILES" "PARMLIB" "DMSOSLIB")"
EXIT
 

Verification:

         Verify the result by running:

• DBLIST
• DBSTATS

These 2 jobs will permit you to verify that the new DBID is correctly associated with the new FILES data set name and that the data is correctly reloaded into it. 

Post cleanup:

As soon as the recovered Datacom Files is no longer needed, it can be cleaned up by following these steps:

• DBDELETE remove the DBID into all the environment Datacom MUF and Disk load module.
• Manually delete the GDG created by the DBDEF

To verify all is cleanup correctly run these jobs:

• DBLIST list all defined FILES from Disk load library
• DBCXXRPT provide a check if in Datacom dictionary the DBID exists as entry or not. 

To do a full Datacom database Files recovery, refer to DBRECOV - Forward Recovery After Loading or Rebuilding the Index 

Additional Information

Recover a Datacom Files from a Backup
 
A backup of the Datacom Files restored into a new DBID can be used to research previously deleted DSNINDEX and ARCHVOL records for recovery.  If the ARCHVOLs still exist, the missing data sets can be restored using the backup. If restore is not required, the ARCHVOLs can be used with REBUILD to bring back the missing DSNINDEX records into the production Files.   
This process is only recommended if a broad range of data sets have been lost.  Single data sets or ARCHVOLS should continue to use the Rebuild functionality or the Datacom recovery processing and rebuild the entries using Datacom logs.
Notice that you can have lost data sets which you will never recover. All depends on the situation, it is an eventuality to consider.
 

Prerequisites:

You need to have the following information by you or see how to collect them below:

• Disk CCUWLOAD or Production loadlib name
• Disk proclib name (normally CCUWPROC)
• Disk sample JCL CCUWSAMP or JCL library to perform Disk utilities
• Location of the ADSDC650 module (normally into CCUWLOAD)
• Free DBID number for Disk based on DBLIST
• Clist or Rexx library containing Disk ISPF interface
• Name of the restore Datacom Files to be used