How to recover expired reports in CA View.

Products

• View

Issue/Introduction

Process to recover the expired reports from View.

Resolution

An expired report from a View database can be recovered in 2 ways explained below:

1. If you know which tape contains the missing report, proceed with setting up the SARTDR ADDDS job against that tape and go to Case 1.
2. You don't know where the report resides and the report was deleted by the backup process?
   
   1. If yes, check the SARBKLST report that lists the reports deleted by the backup and the tapes on which they resided.
   2. If no, proceed with next step.
3. If the report was accidently deleted by a user:
   
   1. Obtain the archive date of the missing report from the user.
   2. Find other reports archived on the same date in View.
   3. Do repeated PF11s until you find the tape sequence for the report archived on the same date as the missing report.
   4. Can Run a SARTCP tapemap on the tape with the same tape sequence number.
      
      1. If the report is on that tape. Proceded with Case 1.
      2. If the report is not there, try running the SARTCP tapemap job on the preceeding tapes and the following tapes until you find the missing report. Then proceed with Case 1.

Case 1 ( recovering the report when it is still on a View tape)

Use the SARTDR/TADD function to re-add specific reports, generations, or resource groups from an archival tape that has expired from a View database. An entire archive tape can also be re-added. The function will add the report(s) back to the View master index.
After the function has completed, the report should be selected with "L" (Load) to cause it to be put back on disk.

Note: At the next View standard backup, the report will expire again unless there has been an adjustment to either the View retention parameters (NGEND, NGENT) or to the report's corresponding entry in the ERO table.

Below is sample JCL for SARTDR:

 //SARTDR      JOB ... 
 //STEP1        EXEC PGM=SARTDR,PARM='VIEW.HLQ' 
 //STEPLIB    DD  DISP=SHR,DSN=VIEW.CVDELOAD 
 //SYSPRINT DD  SYSOUT=* 
 //TAPEINP   DD  DISP=SHR,DSN=VIEW.HLQ.SARTAPE.T000nnnn,
 //   VOL=SER=nnnnnn,UNIT=CART 
 //SYSIN       DD  * 
 /TADD DDNAME=TAPEINP
       ID=(sysout-id,...)
       GEN=(gen,...)
       RESOURCE=(name,...)
       UNIT=xxxxxxxx
       STORGRP=xxxxxxxx 
 /* 
 //

Case 2 (recovering the report when the report is not on any backup tape but is on a full volume backup created by FSS or DFDSS)

Identify the archival date for the missing report and then locate an FDR or DFDSS full volume backup from that time frame. Restore the full volume backup to a temporary database. Verify the missing report is on disk. Then run SARBCH using a /LOAD control card to load the report to a sequential dataset. Run IEBGENER to put the dataset into Jes in the correct class/destination/form so the View task will archive the report into the production database. Run another SARBCH using the /CHANGE control card and the new function that allows the archive date to be changed back to the original archive date. See QI87782 for documentation on the new backdating feature.

Below is sample JCL for SARBCH /LOAD:

//SAARLOAD JOB ...
//STEP1 EXEC PGM=SARBCH
//STEPLIB DD DISP=SHR,DSN=...........VIEW.CVDELOAD
//SYSPRINT DD SYSOUT=*
//REPORT DD SYSOUT=*
//LOAD DD DSN=XXXXXXXXX,DISP=(NEW,CATLG),
// UNIT=SYSDA,SPACE=(CYL,(NN,NN),RLSE),
// DCB=(RECFM=XX,LRECL=NNNNNN,BLKSIZE=NNNNNNN)
//SYSIN DD *
/DBASE NAME=VIEW.HLQ
/LOAD DDNAME=LOAD
GEN=nnnnn
ID=id
/*
//

Below is sample JCL for SARBCH /CHANGE:

//SARLOAD JOB ...
//STEP1 EXEC PGM=SARBCH
//STEPLIB DD DISP=SHR,DSN=............VIEW.CVDELOAD
//SYSPRINT DD SYSOUT=*
//REPORT DD SYSOUT=*
//SYSIN DD *
/DBASE NAME=VIEW.HLQ
/CHANGE ARCHDATE=mm/dd/yyyy
GEN=nnnnn
ID=reportid
SEQ=nnnnn
/*
//