//ERASE    EXEC  PGM=FDRERASE,REGION=0M
//SYSPRINT  DD   SYSOUT=*
//SYSIN     DD   *
   ERASE TYPE=FULL,MAXTASKS=20
   MOUNT  ERASEUNIT=(1A*,1B*)
      

FDR520 PRINTING FROM DEVICE TYPE 3390-3 TO OUTPUT DDNAME TAPE1 FDR521 CYLINDER 00003 TRACK 0000 ------------------ RECORD ZERO 0003000000000008 -- DATA 0000000000000000 ------ FDR522 COUNT FIELD 000300000100DD58 000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 *...............................* LINE 000020-00DD40 SAME AS ABOVE

FDRERASE takes offline disk addresses as input. You can also use FDREPORT to select offline disks based on their volume serials and generate an FDRERASE step for those disks.

An example can be downloaded as file: FDREPORT_FDRERASE.txt

I receive an FDR152 ICF VSAM ERROR REASON=J trying to restore a VSAM cluster to a pre-allocated file. How can I restore this VSAM cluster?

Restoring VSAM clusters to pre-allocated target clusters where the source and the target clusters do not have the same attributes can result in message FDR152 ICF VSAM ERROR REASON=I, J, or N. In current MVS levels, the DEFINE CLUSTER attributes of IMBED, KEYRANGE, and REPLICATE are ignored, so the cluster created will not have those attributes. Also, the rules for the default index CISIZE changed in a recent release. So, even though you use the same DEFINE as the original cluster, the new cluster may have different attributes. An FDR dataset restore or copy requires that the target cluster have the same attributes as the original cluster. If they don’t match, the FDR152 message is issued.

The solution is to let FDR allocate the cluster. FDR can force it to have the characteristics needed to perform a successful restore.

Can I produce a report of all VSAM files that are allocated with any of the obsolete options of IMBED, KEYRANGE, and REPLICATE?

This report can be produced by FDREPORT with the XSELECT AMDATTR= statement specifying the obsolete options (IMBED, KEYRANGE, REPLICATE) you wish to report on.

Here is an example of this report:

XSELECT AMDATTR=IMBED XSELECT AMDATTR=KEYRANGE XSELECT AMDATTR=REPLICATE REPORT FIELD=(SPLCLS,COMPTYPE,VOL,CRDATE,SIZE,AMDATTR) PRINT ENABLE=ONLINE,SORT=YES CLUSTER NAME CPTYP VOLSER CRDATE ALLOC AMDATTR ATTRIBUTES ------------- ----- ------ -------- ------ ------------------ CICS.V4R1M0.CICSIDP1.DFHGCD DATA SYSLB3 1997.227 15 KS IM CICS.V4R1M0.CICSIDP1.DFHGCD INDEX SYSLB3 1997.227 1 IM RE

This jobstream can be downloaded as file: FDREPORT_Obsolete_Options_in_VSAM_Files.txt

We backup our system catalogs after all other backups are complete. Occasionally, new catalogs are created and we may not realize a new catalog is not being backed up until there is a disaster. I would like to extract all the catalog names from the master catalog and create JCL for our catalog backup jobs. Is there a way to do this with FDREPORT?

A list of catalogs can be obtained by FDREPORT by selection on the OPTCD flag as follows:

   XSELECT  OPTCD=BC,COMPTYPE=DATA
	REPORT   FIELD=(SPLDSN,VOL,CRDATE)
	PRINT    DATATYPE=CATALOG

      

This would produce the following listing:

DATA SET NAME VOLSER CRDATE ------------- ------ -------- AFEF.CATALOG SCR083 1989.009 BNCHMARK.ICFCAT BMRKD9 2002.253 CATALOG.ABRBASE SYSLB2 1998.132 CATALOG.ABRSCRCH SAFEC1 1999.311

A similar jobstream which actually generates an ABR Application Backup job for those catalogs can be downloaded as file: FDREPORT_Backup_Catalogs.txt

How can I produce a “tape pull” list showing all the tape volumes for the most current generation?

FDREPORT can generate a tape pull list by extracting the backup data set names for the current ABR generation for each selected volume and then getting the backup data set information from the catalog. This is done in two passes where the first pass creates FDREPORT XSELECT statements for the backup data sets, and the second pass reads those statements to generate the backup tape report. A SUMMARY statement is used to generate the pull list (one line for each unique tape volser).

The first section of the listing shows backup information for the current generation of each disk:

BACKUP TAPES FOR CURRENT ABR GENERATION, SORTED BY DISK VOLUME DISK BACKUP BACKUP FILE DEVICE VOLUME BACKUP DATA SET NAME DATE VOLUME SEQ TYPE CLASS ------- ----------------------- -------- ------ ---- ------- ---- ... VIDPBK0 FDRABR.VIDPBK0.C1030200 2004.065 ST0055 1 3590-1 TAPE VIDPBK0 FDRABR.VIDPBK0.C2030200 2004.065 ST0071 1 3590-1 TAPE VIDPBK0 FDRABR.VIDPBK0.C1030201 2004.068 ST0550 61 3590-1 TAPE VIDPBK0 FDRABR.VIDPBK0.C2030201 2004.068 ST0555 61 3590-1 TAPE

The “tape pull list” is the FINAL TOTALS section of the listing, showing a sorted list of all the tape volumes and the number of backup files referenced on each tape:

PULL LIST FOR BACKUP TAPES FOR CURRENT GENERATION FINAL TOTALS -- VALUE SUMMARY OF VOL --- TOTAL NUMBER OF VALUES VOL-------CCR047 ( 1) ... ST0055 ( 17) ST0063 ( 129) ST0068 ( 129)

This jobstream can be downloaded as file: FDREPORT_Tape_Pull_List.txt

Can we get a report showing all volumes that have a VTOC, VTOC Index, or VVDS that is full or close to being full?

FDREPORT can provide this report by comparing the volume-level fields VL%UDSCB, VL%UINDX, and VL%UVVDS with a specified percentage. Any volumes exceeding this percentage will be listed.

This sample report shows the volumes on which the VTOC, VTOC Index, or VVDS is more than 80% full.

VOLS WITH VTOC, VTOC INDEX, OR VVDS OVER 80% FULL %USED %USED %USED VOLSER UADR DEVTYPE VTOC VTOCIX VVDS ------ ---- ------- ----- ------ ----- IPLOSA 8050 3390-9 91 58 3 RVA7C6 07C6 3390-2 3 2 84 SH23C1 23C1 3390-27 100 0 31 SOFTC2 803E 3390-2 40 84 36

This jobstream can be downloaded as file: FDREPORT_Full_VTOC_VTOCIX_VVDS.txt

How can we identify volumes whose Indexed VTOCs are disabled?

FDREPORT can easily identify volumes that have a SYS1.VTOCIX. data set allocated but not active:

    TITLE   LINE=’VOLUMES WITH INACTIVE VTOCIX’
    REPORT  FIELD=(VLVOLSER,VLINDSTA)
    XSELECT VLINDSTA=YES
    PRINT   DATATYPE=VOLDATA,ENABLE=ONLINE
      

The FDREPORT option DIAGNOSEVVDS checks the VVDS of the volumes for duplicate or orphaned VVRs and VVRs with certain errors, such as a mismatch between the extents in the VVR and the DSCB. It even suggests an IDCAMS jobstream to correct some errors. In V 5.4/40 and above, FDREPORT will do most of these checks regardless of whether DIAGNOSEVVDS is enabled. The option ICFERRPRT will print error messages from the ICF/VSAM identification processor.

If you include a //DIAGPCH DD statement in the JCL and add the option PUNCHDIAGNOS to the PRINT statement, FDREPORT will write out the corrective IDCAMS steps so you can edit and submit them.

Some of the possible diagnostic messages are shown in the sample report below.

In addition, in FDREPORT V 5.4/40 and above, a new field VVRSTATS can be used to select and report on VVR, NVR, and DSCB discrepancies. If you are using a level of FDREPORT less than V5.4/40, omit the XSELECT and the VVRSTATS report field from the following example; it will then report on all data sets, and give the diagnostic messages for those with VVDS errors.

This sample report combines the above features for detecting VVDS errors.

XSELECT VVRSTATS.NE.NONE REPORT FIELD=(VOL,SPLCLS,SPLDSN,VVRSTATS,DSORG,SIZE) PRINT ENABLE=(ONLINE,DIAGNOSEVVDS,ICFERRPRT,PUNCHDIAGNOS), DISABLE=CONTROLBREAK VVR/NVR D/S VOLSER CLUSTER NAME DATA SET NAME ERRSTATS ORG ALLOC ------ ------------ ------------- --------- --- ------ FDR421 ICF LOCATE ERROR -- RETURN CODE---4 - REASON IGGOCLAH-120 -- DSN=ICF006.KRNG.A0007.DATA.A002 FDR495 NO DATA SETS MATCHED SELECTION CRITERIA -- VOLSER=RVA7C7 ORPHANED VVR ON VOLUME RVA7C9 AT RBA 00002008 WITHIN VVDS SYS1.VVDS.VRVA7C9 REMOVE ORPHANED VVR WITH: //STEPXX EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //DD1 DD UNIT=SYSALLDA,DISP=SHR,VOL=SER=RVA7C9 //SYSIN DD * DELETE ICF7C6.KSDS92.KRNG.MULTIVOL.EXTS6.T7F34.D - FILE(DD1) VVR CATALOG(CATALOG.VRVA7C6) // FDR421 ICF LOCATE ERROR -- NO MATCHING VVR -- ICFSOURCE=VVDS -- DSN=XCAT.TIMKO SAFEC8 XCAT.TIMKO NVVR EF 30 FDR421 ICF LOCATE ERROR -- NO MATCHING VVR -- ICFSOURCE=VVDS -- DSN=XCAT.TIMKO.CATINDEX SAFEC8 XCAT.TIMKO.CATINDEX NVVR EF 1 FDR421 ICF LOCATE ERROR -- MULTIPLE VVRS (02) ON VOLUME IDPT01 -- DSN=NATIVE.VSAM.KSDS1.DATA VVR/DSCB EXTENT MISMATCH -- RBA=00024CA9 -- IDPT01 NATIVE.VSAM.KSDS1 NATIVE.VSAM.KSDS1.DATA EXTM MLTR EF 855 FDR421 SMS LOCATE ERROR -- NO MATCHING NVR -- SMSSOURCE=VVDS -- DSN=TEST.STRIPED.SEQ IDPT01 TEST.STRIPED.SEQ NVVR PSE 15

This example can be downloaded as file: FDREPORT_Diagnose_VVDS.txt

We are using FDREPORT to produce a daily report on the DFSMShsm MCDS and would like to have the Migration Volser as one of the fields within the report. Is the Migration Volser mapped by FDREPORT as it is returned from the DFSMShsm HSEND LIST command?

For users of the IBM program product DFSMShsm, FDREPORT can report basic information about HSM migrated data sets. The MCDS contains a field for each migrated data set or cluster called MCDVSN, the volume serial number of the first ML1 or ML2 migration volume containing the migrated data set. FDREPORT release 5.4 and above can report this volser using field name HSMIGVOL (the column heading will be FMIVOL).

An example of this report would be:

TITLE LINE=' DFSMSHSM MIGRATED DATASETS' DEFAULT MCDSCLUSTER=HSM.MCDS XSELECT XDSN=** REPORT FIELD=(SPLDSN,VOL,ADATE,LRDATE,HSMIGVOL) PRINT DATATYPE=MCDS,TITLE=LEFT DFSMSHSM MIGRATED DATASETS DATA SET NAME VOLSER ADATE LRDATE FMIVOL ------------- ------ -------- -------- ------ JSB.HSM.TEST2 BMRKE2 2004.026 2004.026 BMRK00 JSB.HSM.TEST5 BMRKC5 2004.026 2004.026 BMRK00

This example can be downloaded as file: FDREPORT_DFSMShsm_Migrated_Report.txt

When I run FDREPORT, the value for %FREE always shows as zero for POE datasets. Is there any way I can report on the free space in POE datasets?

To get free space values for POE (PDSE) or HFS datasets, you need to turn on the FAMSFREESP and POEUSEPAGE options of FDREPORT, which enables calls to IBM services to get these values. These are enabled on a PRINT or DEFAULT statement by the operand:
ENABLE=(FAMSFREESP,POEUSEPAGE).

The UPDATE flag is in the DS1DSIND field in each DSCB in the VTOC; DSIND=UPDAT will select updated data sets. CATALOG=YES and VOL=mask will limit the search to data sets that are cataloged to the volumes specified.

Sample control cards to create this report:

XSELECT  DSIND=UPDAT,CATALOG=YES,VOL=(mask)
REPORT   FIELD=(SPLDSN,VOL,DSIND,LRDATE,other fields)
PRINT

      

In FDREPORT V5.4, you can generate a report that contains only one line per dataset, even if the dataset extends across multiple volumes, using the operand RECORDSUMMARY. For VSAM, you can choose either one line per cluster (RECORDSUMMARY=CLUSTER) or one line per component (RECORDSUMMARY=COMPONENT). For this feature to work, the input must be sorted by cluster and dataset name. DATATYPE=CATARCH or CATVTOC automatically sorts in this sequence.

This jobstream can be downloaded as file: FDREPORT_Using_RECORDSUMMARY.txt

The jobstreams for all examples shown in this newsletter are available from the Innovation FTP site. Go to the Innovation web site at: www.innovationdp.fdr.com Click on "Customer Support and FTP Access" and "FTP Downloads". Enter your access code (if you don't have one, you can request it on this page). Click on the "Download" directory, then on "Tech_Support_Samples", then on "May 2004".

Can I copy an FDR backup tape or transmit an FDR backup from one computer site to another directly?

Backups created by FDR, FDRDSF, SAR, and FDRABR are in a unique FDR format and cannot be correctly copied by programs other than the FDR utilities FDRTCOPY and FDRTSEL or our tape utilities FATAR and FATSCOPY. If you copy FDR-format backups with any other copy utility, such as the IBM utility IEBGENER, the copy may appear to be successful, but any attempt to restore from the copied backup will fail. Similarly, programs that transmit files from one computer site to another will usually corrupt FDR backups.

FTP, for example, does not handle binary mainframe files with variable-length or undefined-length records, so if you want to transmit an FDR backup file with FTP, it is necessary to use a procedure like TRANSMIT/RECEIVE or the IBM Terse program TRSMAIN to convert the backup file to fixed-length records. To use TRANSMIT/RECEIVE, the steps are:

1. Direct the FDR backup to a disk data set, so that the backup records are no larger than 32760 bytes (FORMAT=SPLIT).
2. From TSO READY, ISPF Option 6, or a batch job executing the TMP, issue the following command to convert the backup to a RECFM=FB,LRECL=80 file that can be FTP’d:
   TRANSMIT X.X DA('inputdsn') OUTDA('outputdsn')
   X.X is required, exactly as shown, but is ignored when OUTDA is specified.
3. FTP this output data set in Binary mode to the receiving system. It can go through intermediate systems (such as PCs) if necessary, but be sure each transfer is done in Binary mode.
4. When the FTP’d file reaches the destination mainframe, be sure that the data set still has attributes RECFM=FB and LRECL=80.
5. At the destination mainframe, receive the dataset from TSO READY, ISPF Option 6 or a batch job executing the TMP by issuing:
   RECEIVE INDA('inputdsn') You will be prompted for the data set name to be assigned to the reconstructed FDR backup file.
6. You can now execute an FDR restore against that backup file.

	TYpe E	or	EBcdic
	MOde B	or	BLock

Although the FDR data is binary, not EBCDIC, no translation will be done on the data in this mode, so the FDR data is preserved.

We use FDRINSTANT to create backup images of our volumes and then dump these backup images at a later time, leaving the backup images on the offline volumes. Now that we have FlashCopy V2, is it possible to use FlashCopy to recover a data set from the offline volumes after the DUMP job has run?

As long as the flashed point-in-time copy of the volume still exists on the target volume, you can copy data sets from the offline copy by using FDRCOPY with FCOPY=USE, as shown below. This will work with or without FlashCopy V2. If you wish to use FlashCopy V2 to recover the data sets, there are additional requirements.

To be able to recover data sets from the offline copy, you will use a sequence such as:

1. Take an FDRINSTANT backup, using PGM=FDRFLASH with FCOPY TYPE=FDR or PGM=FDRABR with FCOPY TYPE=FDR or TYPE=ABR. FDRINSTANT uses a FlashCopy NOCOPY session to create an offline copy of the source volume; in NOCOPY mode, tracks are physically copied only when they are updated, and the FlashCopy session will continue to run until it is released.
2. Dump the offline volume, using PGM=FDR with DUMP TYPE=FDR or PGM=FDRABR with DUMP TYPE=FDR or TYPE=ABR. On the DUMP command, specify FCOPY=USE, which leaves the session active (do not specify FCOPY=(USE,REL), which would end the FlashCopy NOCOPY session and make the offline volume unusable).
3. You can then recover data sets from the offline volume using PGM=FDRCOPY with FCOPY=USE, similar to this example:

    //FDRCOPY  EXEC PGM=FDRCOPY,REGION=0M 
    //SYSPRINT  DD  SYSOUT=*
    //SYSIN     DD  * 
      COPY TYPE=DSF,FCOPY=USE
      SELECT CATDSN=PLOUS.FCV2.TEST,NEWI=MARK5,NVOL=SH20C9

  FCOPY TYPE=FDR,FCOPY=COPY,...

DEFAULT  DATEFORMAT=MMDDYY,BYTEFORMAT=MEGABYTES       
XSELECT  VOL=IDP*                                
REPORT   FIELD=(VOL,VLBYTVOL,VLALOBYT,RUNDATE)        
SORT     FIELD=(VOL)                                  
PRINT    RPTYPE=TABLE,DATATYPE=VOLDATA,RPTDDNAME=TABLE
      

//ALLOC    EXEC PGM=IEFBR14
//PDS       DD  DSN=temp.pds,UNIT=SYSALLDA,VOL=SER=volser,
//             DISP=(,CATLG),SPACE=(TRK,(2,,1))
//*
//CPKRLSE  EXEC PGM=FDRCPK,REGION=0M
//SYSPRINT  DD  SYSOUT=*
//SYSMAP    DD  SYSOUT=*
//SYSUDUMP  DD  SYSOUT=*
//SYSIN     DD  *
  CPK      TYPE=RLSE,VOL=volser,HI=NO
  SELECT   DSN=temp.pds,RLSE=ALL
//*
//CLEANUP  EXEC PGM=IDCAMS
//SYSPRINT  DD  SYSOUT=*
//SYSIN     DD  *
  DELETE  temp.pds
      

UPSTREAM Reservoir provides the highest degree in flexibility by allowing tapes on compatible media to be interchanged with the FDR/UPSTREAM Product. IBM Magstar and StorageTek 9840 tapes on the UPSTREAM Reservoir system can be imported and read on the FDR/UPSTREAM mainframe system and vice versa.

For more information or to order a FREE NO-OBLIGATION Trial please contact us.