October 7, 2005FDRPAS ANNOUNCEMENTS
Recommended maintenance to be applied before running FDRPAS
CHANGES SINCE UPDATE ON 08/2005:
Mandatory FDRPAS zap for MIDAW added
2107 (DS8000) problem updated
Critical SRM APAR OA13330 and Omegamon APAR OA13206 added
Recommended O/C/E APAR OA13458 added
CHANGES SINCE UPDATE ON 01/2005:
2107 (DS8000) problem added
ICKDSF APAR PQ92344 added
All OS/390 2.10 fixes also flagged for z/OS 1.1
ECS Catalog Sharing notes clarified
SUPPORTED FDRPAS RELEASES:
Version 5.4 level 40 of FDRPAS, and higher, are supported. You should not run earlier releases of FDRPAS. The current release, as of October 3, 2005, is V5.4 level 50.
IMPORTANT WARNING ON IBM 2107 (DS8000) DISK SUBSYSTEM
Because of a change in the IBM 2107 (DS8000) compared to the 2105 which IBM did not document, FDRPAS V5.4 level 43 and below may not properly identify the systems attached to a 2107 source disk.
If you are swapping to or from an IBM 2107, you should install FDRPAS V5.4 level 50 or above. This level contains the change to properly identify attached systems on a 2107.
If you wish to use a 2107 with a level of FDRPAS below V5.4/50, you should use the SWAP operand USE#SYSTEMS=nn to specify the number attached systems for a 2107 source disk (be sure you specify it properly). USE#SYSTEMS= should be used only to circumvent this problem; do not use it for other disk subsystems.
IMPORTANT WARNING ON MIDAW SUPPORT ON Z9-109 SYSTEMS
The new IBM z9-109 system supports MIDAWs (Modified Indirect Data Address Words) in I/O channel programs. MIDAWs are used only on the z9-109 and only if you have installed z/OS 1.6 with enabling PTFs or z/OS 1.7.
Because MIDAWs may not be properly supported on non-IBM disk equipment, IBM requested that we add a check to FDRPAS so that we will not attempt to swap between a disk which supports MIDAWs and one that does not.
FDRPAS V5.4 level 50 contains this change, and is recommended for z9- 109 systems. You may also use V5.4 level 42 or 43, but ONLY if you apply zap P-54.4389; this zap is MANDATORY on those levels on a z9-109 system. You must not use FDRPAS levels less than 42 on z9-109 systems.
If you must swap between disks which support MIDAWs (which includes all IBM disks) and those that do not (which includes most non-IBM disks), then you must disable MIDAW usage globally with the command:
- SETIOS MIDAW=NO (or YES to re-enable)
IMPORTANT WARNING ON ECS CATALOG SHARING
ECS (Enhanced Catalog Sharing) is a catalog sharing protocol for parallel sysplexes which uses the Coupling Facility to communicate catalog changes to all systems. You can determine which of your open catalogs are using ECS with the console command:
- F CATALOG,ECSHR(STATUS)
- F CATALOG,ECSHR(AUTOADD)
The ECS CF structure is sensitive to the device address of each ECS shared catalog, so the Catalog Address Space (CAS) is supposed to automatically disable ECS sharing for all catalogs on a volume which is swapped with FDRPAS. However, despite several earlier APARs on this issue, IBM has discovered a problem where this is not occurring, which can result in back-level catalog contents or catalog corruption. IBM APAR OA10139 resolves this problem but fixes are only available for z/OS 1.3 and above.
If you cannot apply the appropriate PTF or no PTF is available for your operating system level, you MUST disable ECS for all catalogs on volumes being swapped, before the swap, using the console command:
- F CATALOG,ECSHR(REMOVE,catname)
- F CATALOG,ECSHR(ENABLE,catname)
Alternately, you can disable ECS globally for all catalogs, before the swaps, using the console command:
- F CATALOG,ECSHR(DISCONNECT)
- F CATALOG,ECSHR(CONNECT)
CRITICAL AND RECOMMENDED IBM SOFTWARE MAINTENANCE FOR ALL SYSTEMS:
You may need to apply IBM maintenance in order to successfully swap disks with FDRPAS. Please check this matrix against your operating system level to see which IBM APARs may need to be applied to all of your systems before you attempt to use FDRPAS. APARs for JES3 only are listed later in this document.
Brief descriptions of the APARs follow the matrix. Please review the descriptions of the applicable APARs to see if they must be applied to your system. IBM can provide detailed APAR descriptions and assist you in determining if a given APAR must be applied. Please note that failure to apply some of these APARs may result in system failures, application failures, or data corruption.
Note: APARs that apply to OS/390 2.4-2.9 can be found in the May 2003 FDRPAS newsletter. Go to the Innovation web page at www.innovationdp.fdr.com and click on "News Via Email" to access the newsletter.
Note: the dots after some APAR numbers are just to improve readability.
C = Critical - will apply to most installations and may result in system outages or data loss if not applied. All FDRPAS users should apply.
R = Recommended - does not result in outage or data loss OR applies only to a limited number of installations with special circumstances. All FDRPAS users should review the descriptions and apply if they are critical for your environment.
* = an IPL is required to implement this fix.Brief IBM APAR descriptions follow:
PQ92344: this recommended APAR adds function to ICKDSF 1.7 to optionally bypass some ENQs when doing a BUILDIX. FDRPAS invokes BUILDIX when swapping to a larger disk. When zap P-54.4373 is applied to FDRPAS V5.4/43, these ENQs will be bypassed, which improves performance and may avoid some ENQ interlocks (the zap is included in FDRPAS V5.4/50).
OA13458: this recommended APAR fixes a S130 ABEND in a DEQ from CLOSE after swapping a volume from a device marked as SHARED to one marked as non-SHARED. This occurs only if you have EDI (Enhanced Dataset Integrity) enabled to prevent multiple updates to sequential (PS) data sets. FDRPAS will not allow you to swap to a non-shared target disk unless only one system is involved in the swap, so most customers will not be exposed to this error.
OA13330: this critical APAR should be applied to avoid S073 and S0C4 abends after you do a dynamic ACTIVATE to delete old FDRPAS source devices from your I/O configuration. Without the fix, some SRM control blocks may still point to the deleted UCBs. If the PTF is not yet available for this APAR, you must not delete source devices until after your next IPL.
OA13206: this critical APAR is for Omegamon V5.2 and fixes a S0C1 abend when FDRPAS swaps are run. Omegamon was originally from Candle but is now from Tivoli (IBM). V5.2 is an older release; newer releases of Omegamon have the fix integrated.
OA10139: this critical APAR should be applied if you are swapping volumes containing catalogs shared with ECS (Enhanced Catalog Sharing via a coupling facility). This problem can result in lost catalog entries and other catalog corruption. If you cannot apply the fix, or there is no fix for your operating system level, see the notes above on disabling ECS during the swap.
OA09675: this critical APAR should be applied if you are swapping volumes contain PLPA or COMMON paging data sets and you have PAV aliases assigned to the source disks. It fixes a problem where the paging I/O may get “lost” if it was active on an alias when FDRPAS starts to swap the volume. This will result in various types of hangs and usually requires a reIPL to resolve. You can circumvent the problem if you can disable PAV on the PLPA/COMMON volume before the swap.
OA07355: this recommended APAR must be applied if you are going to swap volumes to or from a StorageTek V2Xf disk subsystem. It fixes a problem in the Media Manager component which results in invalid CCW chains when the V2Xf is involved as a source or target disk in a FDRPAS swap.
OA07006: this recommended APAR fixes a S878 abend during IPL if a large number of IEA311 UNLABELED DASD messages are issued. This can occur if many FDRPAS source volumes are still connected and have not been relabeled.
OA05722: this recommended APAR fixes an error in module IECDINIT which may cause a swap to terminate if a Flashcopy from a FDRPAS source device is initiated during a swap. It only affects customers who have the FlashCopy V2 (data set flash) support installed on their disk and on their operating system. FlashCopy V1 customers do not need to install this fix. FDRPAS V5.4/40 inhibits FlashCopy during a swap so this problem is unlikely to occur if you are running level 40 or above.
OA05403: this recommended APAR suppresses a SVC dump which may occur when volumes with PAV aliases are swapped. The dump title will refer to IOS-DEVICE STATE TRANSITION FLUSHING and the symptoms in the dump will include abend SCOD reason 00000001. According to the APAR, this condition is automatically recovered and the dump is meaningless. Apply the PTF to suppress the dump, or just discard the dumps. The swap will be successful.
OW57711: this recommended APAR fixes a S0C4 in module IECDINIT during a swap. The abend causes no harm and the swap will complete successfully, but a SVC dump will be created. The problem seems to occur when the target device has never been online to the system since the last IPL.
OW57552: this critical APAR fixes a problem in DASD error recovery (ERP) which can result in I/O errors in some applications which are using a disk while FDRPAS is copying it. This may result in application or system failures depending on the component issuing the I/O. The error may be accompanied by a SVC dump with a title indicating S0C4 in DASD ERP (IECVDERP). This problem only occurs when running FDRPAS V5.4 level 4x; earlier levels of FDRPAS are not affected. If the PTF for this problem cannot be applied, contact Innovation for custom zap C-54.0925 to circumvent the problem.
OW56156: this recommended APAR fixes a problem in XCF where the device address of a couple dataset is incorrectly displayed after a swap of the disk.
OW55469: this critical APAR fixes Media Manager to avoid hangs and ABENDs in programs which use Media Manager. Without this fix, you may experience DB2 failures during a swap. It has also been implicated in a hang in CA-OPSMVS (from Computer Associates) during a swap.
OW54976: this critical APAR should be applied to avoid SQA overlays due to a problem in the IBM service IEEVARYD. You can avoid the problem without applying the fix by adding the undocumented operand "VARYON=NOAFTER" to all SWAP and MONITOR statements on every system; however, this leads to a rare case where concurrent copy and FlashCopy do not work after the swap; if this occurs, issue the console command V uuuu,ONLINE,UNCOND
OW54200: this critical APAR has been implicated in data corruption during FDRPAS swaps. The APAR mentions IEBCOPY but we have seen data corruption in DB2 databases. Other data set types may be exposed as well.
OW53761: this recommended APAR addresses problems when swapping from a device with new features (such as Flashcopy on a 2105 Shark) to another subsystem without those features. FDRPAS disables those features at the beginning of the swap, but without this fix they may be dynamically re-enabled before the swap ends.
OW53222/OW52127: these APARs are recommended to prevent accidentally IPLing from the old SYSRES and IODF volumes which have been swapped.
OW52631: this critical APAR must be applied if you swap to or from devices with PAV (Parallel Access Volumes), to avoid a S0C4 abend in IOS. The error may occur when trying to use the non-PAV device after the swap.
OW52614: this recommended APAR fixes a problem where an active Concurrent Copy session on a volume may cause a swap of that volume to fail. Since FDRPAS delays the final swap when Concurrent Copy activity is detected, this problem should be rare. But if it occurs, the volume may be swapped on some systems but not on others. If your installation does not use Concurrent Copy, this fix is not required.
OW52422: If you have applied the PTF for APAR OW51163 or are running z/OS 1.3, you must apply this critical APAR to avoid a S09A ABEND with reason code CB01 in GRS after a swap (even if you use CA-MIM). This abend will only occur if there is a RESERVE on the volume at the moment of the actual swap; FDRPAS will not complete the swap until there are no outstanding RESERVEs but it is possible for a RESERVE request to be issued after FDRPAS checks. z/OS systems should also apply the PTF for APAR OW54570 to avoid a S0C4 abend in GRS after the S09A abend. This problem is most likely on volumes with high RESERVE activity, such as JES checkpoint volumes and other volumes with shared system- type data sets such as catalogs, but it can affect any volume. In many cases, the abend will affect the task issuing the RESERVE but will not harm other tasks. If JES abends, you should be able to restart JES without affecting running jobs.
OW51840: if you have applied the PTF for IBM APAR OW48166 or one of the catalog level set PTFs UW81063/64/65, you MUST apply this critical APAR. This problem causes a loop in the catalog address space at the end of a swap if you are NOT using ECS (Enhanced Catalog Sharing) for any catalog. No IPL is required to implement this fix, simply issue F CATALOG,RESTART
OW51461: see OW54200 above.
OW49783: apply this recommended APAR if you plan to do dynamic I/O configuration of swapped devices before the next IPL.
OW49672: this critical APAR MUST be applied to avoid a hang when swapping a volume containing a shared catalog. The APAR describes a catalog performance problem, but it has resolved several hangs during swaps. No IPL is required to implement this fix, simply issue F CATALOG,RESTART
OW46936: you may want to apply this recommended APAR to avoid an occasional ABEND0C4 during a swap. The ABEND0C4 is not harmful and the swap will complete successfully but it causes an unnecessary SVC DUMP.
OW46459: this critical APAR MUST be applied if you are using WLM- managed dynamic PAV and you swap from one device with PAV to another with PAV.
OW46101: this recommended APAR resolves performance problems on LLA- managed datasets after a swap.
OW45683: this recommended APAR resolves performance problems after swapping to a device with PAV (Parallel Access Volumes).
OW44548: If you have ever used FDR to convert DB2 or other linear VSAM
clusters from 3380 disks to 3390 disks, and you are now swapping those
clusters to IBM 2105 Sharks, you should apply this recommended APAR to
avoid I/O errors when re-loading or extending those clusters after the
**Circumvention: DELETE/DEFINE and reload the clusters before or after the swap.
CRITICAL AND RECOMMENDED IBM MAINTENANCE FOR JES3 SYSTEMS:
You may need to apply IBM maintenance in order to successfully swap disks with FDRPAS under JES3. Please check this matrix against your JES3 level to see which IBM APARs may need to be applied to all of your systems before you attempt to use FDRPAS. APARs for all systems listed earlier in this document may also apply to your system.
Critical APARs must be applied before using FDRPAS (if they apply to your system). Recommended APARs may be optional, but read the details of each to be sure.
Brief descriptions of the APARs follow the matrix. Please review the descriptions of the applicable APARs to see if they must be applied to your system. IBM can provided detailed APAR descriptions and assist you in determining if a given APAR must be applied. Please note that failure to apply some of these APARs may result in system failures, application failures, or data corruption.
C = Critical - will apply to most installations and may result in system outages or data loss if not applied. All FDRPAS users should apply.
R = Recommended - does not result in outage or data loss OR applies only to a limited number of installations with special circumstances. All FDRPAS users should review the descriptions and apply if they are critical for your environment.Brief JES3 APAR descriptions follow:
OA06935: this recommended JES3 APAR addresses a problem where a swapped volume appears to return to its original device after a local system is started.
OW51565: this critical JES3 APAR prevents a S0C1 abend in JES3 after a swap. This APAR can be installed without an IPL using dynamic LPA and JES3 hotstart.
OW47252: this recommended JES3 APAR addresses a problem where a swapped volume appears to return to its original device after a local system is started.
OW47245: This recommended JES3 APAR addresses a hang after a swap of the IPL volume (containing the JES3LIB dataset). You do not need to IPL after applying this fix. You may also need to apply JES3 APAR OW37639.
REQUIRED HDS (Hitachi Data Systems) MICROCODE UPDATE:
Customers swapping to a HDS 9xxx Lightning disk subsystem must insure that the microcode level is 01-13-19/00 or higher. Without this microcode, FDRPAS monitor tasks may not recognize that a swap is starting.
REQUIRED STORAGETEK V2Xf MAINTENANCE
If you are swapping to or from a volume in a StorageTek V2Xf (FICON- attached) subsystem, you must be at microcode level G01.01.14.00 or above.
REQUIRED IBM 2105 ESS MAINTENANCE
If a source volume is in an IBM 2105 ESS (Shark) with FICON channels, you should be at microcode level 184.108.40.206 or above so that FDRPAS can properly identify the attached systems. This does not affect target volumes but this microcode level is recommended even for target systems.