FDR 5.3 l40 is now available

FDR 5.3/40 or above must be installed if you plan to use non-SMS PDSE or HFS data sets.

Summary of Modifications for Version 5.3 LEVEL 40

SUPPORT FOR THE HSDM OPTION FROM STORAGETEK

V5.3/40 and above supports the HSDM (High Speed Data Mover) option of the SVA (Shared Virtual Array) disk subsystem from StorageTek; HSDM is also available on some models of the IBM RVA (Ramac Virtual Array). Contact StorageTek for information on the requirements and pricing on HSDM or visit their web site at:

www.storagetek.com

In an SVA/RVA, all data is compressed, even in cache. It is uncompressed only when it must be sent to the host. When backing up data in an SVA/RVA, it must be decompressed by the control unit, and recompressed when it is restored.

HSDM allows FDR to directly read the compressed track images, avoiding the decompression overhead. The amount of data that must be read from disk and written to the backup is reduced by 3:1 or more, which reduces the elapsed time of the FDR backup up to 60%. When restoring the same data to an SVA/RVA with the HSDM option, HSDM allows FDR to write the compressed track images directly, avoiding compression overhead and providing similar reductions in restore elapsed time. When data dumped with HSDM must be restored to a non-HSDM disk, FDR calls a software decompression subroutine provided by StorageTek, and restores the uncompressed data to the output disk normally.

HSDM is supported by all FDR backup/restore functions in programs FDR, FDRDSF, and FDRABR as well as restore functions in FDRCLONE and FDRDRP. To invoke HSDM during a backup, add the operand DCT=YES (DUMPCOMPRESSEDTRACK=YES) to the DUMP statement under any of the programs listed above; HSDM will be invoked for all volumes with HSDM enabled and will be ignored for other disks which will be dumped normally. No special parameters are required to restore a HSDM- created backup; FDR (including SAR) will automatically recognize the HSDM format and restore it properly.

You can use any of your existing FDR, FDRDSF, or FDRABR jobstreams, or any of the examples in the FDR manual, and simply add DCT=YES, for example,

DUMP TYPE=FDR,DCT=YES

DUMP TYPE=ARC,ADAYS=15,DSNENQ=USE,DCT=YES

In a test run at Innovation, dumping one 3390-3 volume from a SVA to a StorageTek 9840 tape, HSDM reduced elapsed time by 54%.

In order to use HSDM, you must be licensed for FDRINSTANT and you must have the HSDM feature installed on your SVA or RVA. More details on HSDM support can be found in Section 80.33 and in the sections for each FDR function.

WARNING: if you use DCT=YES and have one of these IBM PTFs applied to your system

UW90591

UW90593

UW61573

UW90595

UW61575

Then, you must apply the PTF which fixes IBM APAR OW42799 to avoid a problem which may cause backups to fail. Read the description of APAR OW42799 for details.

ABR now supports the ExHPDM (Extended High Performance Data Mover) software product from StorageTek; in 5.3/30 it was supported only for FDR and FDRDSF, but that support is extended to ABR Volume Backups and Application Backups (FDRAPPL) in V5.3/40. It is not supported for ABR Archive Backups. ExHPDM interleaves several concurrent output data streams (such as concurrent FDR backups) onto one tape to improve performance and reduce the number of tape volume required.

ExHPDM is invoked by the SUBSYS= JCL parameter on TAPEx and TAPExx DD statements in FDR jobsteps, e.g.,

//TAPE1    DD   DSN=BACKUP.VPROD01(+1),UNIT=TAPE,
        //         SUBSYS=(SOV,'CLASS(FDRBKUP)'),DISP=(,CATLG)

More details on ExHPDM support can be found in Section 80.33 and in the sections for each FDR function. You must be licensed for FDRINSTANT to use ExHPDM with ABR. You must be running at least ExHPDM V1.1 plus PTF L1P013W (for FDR support) and PTF L1P015A (for ABR support).

In previous releases, a backup to a sequential disk data set or to disk and tape concurrently would take much longer than a backup to tape alone, due to the disk I/O technique used on the input when outputting to disk. Backup to disk is most commonly used with ABR Archive (DUMP TYPE=ARC) to create COPY 1 on disk for rapid recall.

Also, each concurrent backup executing in an FDR step required about 1M of memory below the 16MB line, limiting the number of such concurrent backups to the size of the available below the line private area in each installation (usually 6-10MB).

In V5.3/40 and above, these limitations are removed. On any DUMP statement in FDR, FDRDSF or FDRABR, add the operand RTC=YES (READTRACKCCW=YES). With RTC=YES, most of the FDR buffers are moved above the 16MB line, allowing more concurrent backups to run, up to the limit of 9 in one address space. FDR will read up to 1 cylinder (15 tracks) of data in one I/O, compared to 1/2 cylinder without RTC=YES. Backups to disk will run much faster, and backups to tape will see some improvement depending on the data rate of your tapes and disks.

The backup produced by RTC=YES will have the same format as backups from previous releases and can be restored by any FDR release. Note: in V5.3/40, COMPRESS= will be ignored if RTC=YES is specified, so RTC backups to disk will not be compressed. They may occupy more disk space than compressed backups without RTC=YES. Innovation intends to lift this restriction in a future release.

WARNING: if you use RTC=YES and have one of these IBM PTFs applied to your system

then you must apply the PTF which fixes IBM APAR OW42799 to avoid a problem which may cause backups to fail. Read the description of APAR OW42799 for details.

When previous releases of FDR were used to do a full-volume restore or copy, and the IBM product DFSMSdss was later run on the volume, DFSMSdss might generate message ADR299E indicating that the volume size in the VTOC index was incorrect. FDR will now correct the VTOC index volume size during the restore/copy; the correction will occur only if both the backup and restore are done with V5.3/40 or above.

In order to insure that FDR can get consistent, usable backups of HFS (Hierarchical File System for Unix System Services, USS) data sets, all FDR, FDRDSF, and FDRABR backups now support the operand HFS=QUIESCE. If specified, and FDR is unable to get a SYSDSN ENQ on the HFS data set (which usually means that the file system is mounted to USS), FDR will issue a USS "quiesce" function which will suspend all access to the file system until the backup is complete. This applies to most FDR and FDRABR backups as well as FDRCOPY COPY and FDRINSTANT SNAP and SPLIT; it does not apply to COMPAKTOR, Archive Backups or FDRCOPY MOVE.

FDR can backup and restore entire HFS data sets. If you need the ability to backup and/or recover individual HFS files within the data sets, this is provided by UPSTREAM/USS, a separately-priced product from Innovation.

SUPPORT FOR NON-SMS PDSE AND HFS DATA SETS

IBM has released PTFs UW65973 (DFSMS 1.4) and UW65974 (DFSMS1.5) for (OS/390 2.4 and above to support PDSE (PDS Extended) and HFS (Hierarchical File System for Unix) data sets on non-SMS volumes. Previously they were supported only on SMS-managed volumes.

FDR 5.3/40 or above must be installed if you plan to use non-SMS PDSE or HFS data sets.

Toleration zaps are available for previous releases but they do not support allocation of these data sets.

The NVOL= operand, used in DSF and ABR data set restores and FDRCOPY copy/move, has been enhanced. For multi-volume data sets it now allows you to more closely control the order in which the volumes specified by NVOL= will be used when allocating the data set. For details see the NVOL= description in various sections of this manual.

The technique used to allocate multi-volume VSAM clusters has been changed to improve the chance of a successful allocation when the target volumes are fragmented. Previously it was possible that FDR could allocate the first extent of a multi-volume cluster on a volume but would fail when trying to extend the cluster to additional extents (usually due to lack of free space). Now it will retry the allocation on another volume and report the error only if the allocation fails on all target volumes.

Many FDR backups and restores now support a FDRSUMM DD statement. This is usually a SYSOUT data set, and will contain a one line summary for each disk volume processed, showing result codes and statistics, such as elapsed time, track counts, and byte counts. When FDR gives an abend or return code indicating that a problem occurred, this is a convenient way to find the failing volume quickly.

It is supported on all backups but only if RTC=YES or DTC=YES is specified on the DUMP statement.

It is supported only for FDR, ABR, and FDRDRP full-volume restores.

FDREPORT contains a new catalog processor. It makes all catalog fields available for reporting. Previously, some fields (such as creation/expiration date and SMS classes) were taken only from the VTOC/VVDS, not the catalog. Now they will be taken from the catalog as well. It is invoked for DATATYPE=CATALOG, CATVTOC, or CATARCH.

FDREPORT EXTENDED FORMAT VSAM SUPPORT

FDREPORT now supports Extended Format (EF) VSAM clusters. The size of clusters over 4GB are properly reported. For compressed clusters, the size of the cluster before and after compression can be reported.

IBM 2105 SHARK

All versions of FDR support the IBM 2105 SHARK disk subsystem without modifications. Support for Flashcopy on the 2105 ESS will be available in FDRINSTANT shortly after IBM makes Flashcopy generally available. IBM 3590E CARTRIDGE DRIVES All releases of FDR support the IBM Magstar 3590E drives, as well as the new extended length cartridges.

IBM BookManager format for online viewing and searching. These can be viewed on your workstation or uploaded to MVS for viewing with BookManager READ/MVS (included in OS/390). If you don't have a licensed copy of BookManager READ on your workstation, the IBM Library Reader (a limited copy of BookManager READ), is also on the CD or you can use the Library Reader from the IBM documentation CD-ROMs.

ADOBE PDF files for printing. Using ADOBE ACROBAT READER on your workstation (also included on the CD), you can view and print manuals that look exactly like Innovation's printed manuals.

One copy of the CD-ROM is available to each licensed installation at no additional charge.

You can now receive news, announcements, new product information, latest versions and technical bulletins via E-mail. You can subscribe to this mailing list at our web site.

Subscribe to Mailing List

PRODUCT NEWS

Member NEWS in the ICL (Installation Control Library, loaded as part of FDR installation) contains the latest news and notes about the FDR family of products. It may contain details on changes made too late to be included in this manual.

All users should review the NEWS member after installation.

This table shows, for each current release of OS/390, the minimum and recommended levels of each Innovation product that should be installed. Use the table when upgrading your OS/390 system to verify that you have the correct Innovation software in use. If you already have the minimum level installed, you need do nothing. If you must upgrade, you should install the latest version.

Notes: 1) SUPPORT FOR NON-SMS PDSE AND HFS DATA SETS. IBM has released PTFs UW65973 (DFSMS 1.4) and UW65974 (DFSMS 1.5) for OS/390 2.4 and above to support PDSE (PDS Extended) and HFS (Hierarchical File System for Unix) data sets on non-SMS volumes. Previously they were supported only on SMS-managed volumes. FDR 5.3/40 or above must be installed if you plan to use non-SMS PDSE or HFS data sets. Toleration zaps are available for previous releases but they do not support allocation of these data sets. For further information see IBM's Washington System Center flag 10007.