FDR Support for Non-SMS PDSE and HFS data sets

On January 9, 2000 IBM released PTFs for APAR OW35441, which adds support for PDSE and HFS data sets allocated on non-SMS volumes. Prior to this fix, PDSE and HFS data sets had to be on SMS-managed volumes.

Full support for non-SMS PDSE and HFS data sets is in FDR V5.3 level 40, which will be generally available in February 2000. This includes support for allocation and restore of these data sets as well as conversion between SMS and non-SMS.

Users of FDR V5.3 level 3x should apply toleration zaps which will avoid possible data loss on these data sets. The toleration zaps do not provide full support and do not provide the ability to do data set restores of non-SMS HFS/PDSE data sets, but they do insure that these data sets will be handled correctly by backups, full-volume restores and copies, COMPAKTOR, FDRREORG and FDREPORT.

Warning: you must install either the toleration zaps or V5.3 level 40 before you create your first non-SMS HFS or PDSE data set. Toleration zaps are not available for releases of FDR prior to V5.3 level 30; you must install at least that level if you plan to use these data sets.

The following two toleration zaps apply to V5.3 levels 30 through 33; they are included in level 34 and above:

P-53.3032 - insure that all FDR and ABR backups select all tracks in non-SMS HFS and PDSE data sets. Full-volume restores of volumes containing these datasets will work, but data set restores are not supported prior to V5.3 level 40.

P-53.3040 - allows FDREPORT to properly report and select on the used space within non-SMS HFS and PDSE data sets. This zap applies only to customers licensed for ABR or FDREPORT.

The following toleration zap (P-53.3039) applies to V5.3 levels 30 through 37. It should be applied by all customers licensed for COMPAKTOR and/or FDRREORG:

P-53.3039 (for V5.3 levels 30 to 37) - insure that COMPAKTOR will move all tracks in non-SMS HFS and PDSE data sets. Prevent FDRREORG from attempting to reorganize these data sets.

These zaps are available on Innovation's FTP site in directory /Download/FDR_V53; or email Innovation at support@fdrinnovation.com to receive them by return email.

99365/99366 Alert for all FDR customers

When FDRDSF or FDRABR is used to restore to a pre-allocated data set, it checks the expiration date of the output data set. If it is not expired, message FDRW03 is issued to the operator console, requesting the operator to approve or deny the restore. FDR was not properly testing for expiration dates of 99365 and 99366 (permanent retention) under certain conditions, so it would allow such data sets to be overlaid by a restore without requesting operator permission.

When FDRABR Archive (DUMP TYPE=ARC) or Superscratch (DUMP TYPE=SCR) selects a non-VSAM data set, it checks the expiration date of the output data set before it is scratched. If it is not expired, message FDRW23 is issued to the operator console, requesting the operator to approve or deny the scratch. Many installations add EXPD=NONE to the ABR DUMP statement, which suppresses this check and the message.ABR was not properly testing for expiration dates of 99365 and 99366 (permanent retention), so it would allow such data sets to be archived and scratched without requesting operator permission

These problems are fixed by the following zaps:

For V5.2 levels 60 through 66: P-52.1346
For V5.3 levels 20 through 25: P-53.2158
For V5.3 levels 30 through 37: P-53.3133
For V5.3 levels 20 through 37: P-53.3134 (for ABR customers only)

These zaps are available on Innovation's FTP site in directory /Download/FDR_V5x ("x" is 2 for V5.2 or 3 for V5.3); or email Innovation at support@fdrinnovation.com to receive them by return email (indicate the level of FDR you are running).