ABR CUSTOMERS: ABR/CATALOG INTERLOCK

A problem has been discovered with ABR running on OS/390 2.10 or z/OS. It only affects ABR customers who have implemented the ABR scratch catalog and installed the ABR DADSM pre-exit (option ABRPRE on ISPF panel A.I.4.11.1). The interlock occurs when a VSAM cluster which was defined with the REUSE attribute is opened with the REUSE option; this allows a cluster to be reloaded without having to redefine it. If the cluster has expanded to secondary volumes, REUSE scratches the extents on the secondary volumes, causing the DADSM pre-exit to be entered. The exit does a catalog LOCATE on the cluster. In OS/390 2.10 and above, this causes an interlock because the catalog containing the cluster is already ENQed. The hung job must be cancelled to relieve the interlock and free the catalog. ABR customers can download a zap for this interlock from our FTP site.

For ABR V5.3 levels 50 through 57, download fix file p535105.txt
For ABR V5.3 levels 10 through 44, download fix file p534137.txt
ABR V5.3 level 58 and above will include the fix.

Note: To access our FTP site, go to www.innovationdp.fdr.com/ftp/ftp.cfm and enter your access code. If you don't have an access code, you can obtain one via e-mail: ftpid@fdrinnovation.com.

COMPAKTOR CUSTOMERS: ALLOCATION ERRORS AFTER VOLUME MOVES

A problem has been discovered where COMPAKTOR may leave a volume exposed to allocation problems after the volume has been moved to disk devices from various hardware vendors. The problem occurs when the volume is moved from a disk device which has no alternate tracks (such as an IBM Shark or RAMAC I/II/III) to a device with real or emulated alternate tracks (such as a IBM 3390 or RVA, or disks from EMC, StorageTek, Hitachi or Amdahl); the volume movement might be done with TDMF, or a hardware migration technique, or with full-volume copies. If the volume was COMPAKTed on the device with no alternates, then moved to the device with alternates, it may leave the space maps in the VTOCIX such that DADSM will attempt to allocate the alternate tracks to a dataset. This can result in allocation errors, or I/O errors. If the volume is COMPAKTed after it is moved to the volume with alternates, the problem will no longer occur. But if a COMPAKTion is not done, the errors can occur. COMPAKTOR customers can download a zap from our FTP site which will change COMPAKTOR so that it no longer leaves volumes exposed to this problem. For COMPAKTOR V5.3 levels 22 to 57, download fix file p535108.txt
COMPAKTOR V5.3 level 58 and above will contain the fix.

FDRINSTANT CUSTOMERS: BACKUP AND RESTORE OF OS/390 LINUX DISKS WITH FDR

Updated notes on the backup and restore of S/390 LINUX disks with FDR are now available on our FTP site. Download file linux.txt. These notes will also be in member LINUX of the FDR Installation Control Library (ICL) on the distribution tape for V5.3 level 58 and above.

Backup of Linux disks requires that you be licensed for FDRINSTANT and a zap must be applied to enable the Linux support. You can download the zap from our FTP site.

For FDRINSTANT V5.3 levels 50 to 58, download fix file p535090.txt

FDRSOS CUSTOMERS: EMC MICROCODE 5X67

FDRSOS customers who upgrade their EMC Symmetrix subsystems to microcode level 5x67 must apply a zap available on our FTP site. For FDRSOS V5.3 levels 50 to 56, download fix file p535095.txt

FDRSOS levels 57 and above will contain this fix.
If you are currently running a level of FDRSOS less than V5.3 level 50, you must order and install V5.3 level 57 or 58 before upgrading the microcode.