FDRPAS ANNOUNCEMENTS

Recommended maintenance to be applied before running FDRPAS:
Recommended IBM and other maintenance to be applied before running FDRPAS Last updated: 1/14/05

CHANGES SINCE UPDATE ON 11/2004:
Warning on ECS catalog sharing updated.
Critical APAR OA10139 for ECS added, other ECS APARs removed

CHANGES SINCE UPDATE ON 07/2004:
Warning on ECS catalog sharing added.
Critical APAR OA09675 added.
Recommended APAR OW52614 added.

CHANGES SINCE UPDATE ON 03/2004:
Critical APAR OW57552 added - affects all FDRPAS V5.4/4x customers
Recommended APARS OA07006, OA07355 and OA08398 added.
JES3 recommended APARS OW47252 and OA06935 added.
APAR OA06158 notes updated.

SUPPORTED FDRPAS RELEASES:

Versions 5.4 level 30 of FDRPAS, and higher, are supported. You should not run earlier releases of FDRPAS.

Customers who have installed IBM FlashCopy V2 (data set flash) should use
FDRPAS V5.4/40 or above.

The current release, as of 01/13/05, is V5.4 level 43.

IMPORTANT WARNING ON ECS CATALOG SHARING

ECS (Enhanced Catalog Sharing) is a catalog sharing protocol for 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)

Until IBM resolves this problem, you MUST disable ECS for all catalogs on volumes being swapped, using the console command:

F CATALOG,ECSHR(REMOVE,catname)
or F CATALOG,ECSHR(DISCONNECT) - disables ECS globally

After the swaps, you can reenable ECS with

<F CATALOG,ECSHR(ADD,catname)
or f CATLAOG,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.

IBM       |OS/390| |-------z/OS-----------| 
APAR        2.10   |1.1 1.2 1.3 1.4 1.5 1.6
OW44548*      R    | 
OW45683*      R    |
OW46101*      R    |R
OW46459*      C    |C
OW46936*      R    |
OW49672       C    |C
OW49783*      R    |R   R
OW51461       C    |C   C
OW51840       C    |C   C
OW52127       R    |R   R   R
OW52422*      C    |C   C   C
OW52614*      R    |R   R   R
OW52631*      C    |C   C   C
OW53222       R    |R   R   R 
OW53761*      R    |R   R   R   R
OW54200*           |        C   C
OW54976*      C    |C   C   C   C 
OW55469*      C    |C   C   C   C
OW56156*      R    |R   R   R   R
OW57552*      C    |C   C   C   C
OW57711*      R    |R   R   R   R
OA05403*      R    |R   R   R   R   R
OA05722*      R    |R   R   R   R   R
OA07006*           |    R   R   R   R
OA07355*           |    R   R   R   R
OA09675*           |C   C   C   C   C   C
OA10139*           |        C   C   C   C

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:

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 systemlevel, 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.

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 2105 ESS (Shark) 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 swap. **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.

JES3   |OS/390| |-------z/OS-----------| 
APAR     2.10    1.1 1.2 1.3 1.4 1.5 1.6
OW47245   R
OW47252   R
OW51565   C       C
OA06935                   R    R   R

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 1.5.2.114 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.