The Makers of FDR®

May 1, 2003 FDRPAS Announcements

FDRPAS V5.4/24 is required for support of the new EMC Symmetrix
DMX disk subsystem (DMX systems run the 5x69 microcode).

SUPPORTED FDRPAS RELEASES:

Versions 5.4 level 20 of FDRPAS, and higher, are supported.

REQUIRED IBM 2105 ESS MAINTANENCE

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.

REQUIRED AND RECOMMENDED IBM MAINTENANCE FOR ALL SYSTEMS:

The only changes from the December 17, 2002 APAR list are that APAR OW54976 is changed from recommended to critical, and that we have added APAR OW57711.

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.

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

IBM     |--------- OS/390 ---------| |----z/OS-----| 
APAR 2.4 2.5 2.6 2.7 2.8 2.9 2.10 1.1 1.2 1.3 1.4
OW30926 R R
OW31942 C
OW41858 C C C C C
OW44548 R R R R R R
OW45683 R R R R R
OW46101 R R R R R R R R
OW46459 C C C C C
OW46936 R R R R R R R
OW48166 R R R R R
OW49672 C C
OW49783 R R R
OW51248 R
OW51461 C C C C C C C C C
IBM |--------- OS/390 ---------| |----z/OS-----|
APAR 2.7 2.8 2.9 2.10 1.1 1.2 1.3 1.4
OW51840 C C C C C C
OW52127 R R R R
OW52422 C C C C C C
OW52631 C C C C C C
OW53222 R R R R
OW53761 R R R R R R R R
OW54200 C C
OW54976 C C C C C C C
OW55469 C C C C C C C C
OW55980 R R R R R
OW56156 R R R R R
OW57711 R R R 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 IBM APAR descriptions follow:

OW5771: 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.
An IPL is required to implement this fix.

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.
An IPL is required to implement this fix.

OW55980: this recommended APAR fixes a S0C4 abend during a console ACTIVATE command after a swap.
An IPL is required to implement this fix.

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.
An IPL is required to implement this fix.

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

An IPL is required to implement this fix.

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.
An IPL is required to implement this fix.

OW5376: 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.
An IPL is required to implement this fix.

OW53222/OW52127: these APARs are recommended to prevent accidentally
IPLing from the old SYSRES and IODF volumes which have been swapped.
No IPL is required to implement these fixes.

OW5263: 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.
An IPL is required to implement this fix.

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 datasets 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.
An IPL is required to implement this fix.

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/OW51248: apply this recommended APAR if you plan to do dynamic
I/O configuration of swapped devices before the next IPL.
An IPL is required to implement this fix.

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

OW48166: this critical APAR MUST be applied if you are using ECS (Enhanced
Catalog Sharing) in a parallel sysplex, and you plan to swap volumes
containing catalogs. The fix will automatically remove a catalog from ECS if it is on a volume that is swapped. You must also apply the PTF for APAR OW51840. To determine if you are using ECS, issue this console command on any system:

F CATALOG,ECSHR(STATUS)

If all catalogs displayed have a status of "inactive", ECS is not in use.
No IPL is required to implement this fix, simply issue F CATALOG,RESTART
Circumvention: If you have not applied the PTF, or you wish to avoid the
catalog messages, IBM's recommendation is to remove
catalogs from ECS before you swap the volumes on which
those catalogs reside. Read the IBM APAR text for details.

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.
An IPL is required to activate this fix.

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.
An IPL is required to activate this fix.

OW4610: this recommended APAR resolves performance problems on
LLA-managed datasets after a swap.
An IPL is required to activate this fix.

OW45683: this recommended APAR resolves performance problems after
swapping to a device with PAV (Parallel Access Volumes).
An IPL is required to activate this fix.

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.
An IPL is required to activate this fix.
Circumvention: delete/define and reload the clusters before or after
the swap.

OW41858: This critical APAR MUST be applied before attempting to swap to or
from a device with PAV (Parallel Access Volumes). This PTF adds a PAV interface
routine that is invoked by FDRPAS. No IPL is required to activate this fix.

OW31942: this critical APAR MUST be applied before attempting to swap a volume
from a device with a 3-digit device address to one with a 4-digit address.
An IPL is required to activate this fix.

OW30926: if you plan to swap volumes containing system couple datasets (CDS) it is recommended, but not required, that you apply this APAR. This fix allows the coupling facility to better tolerate short delays in I/O to the datasets, which may occurring during the swap. Without the fix, there is a possibility that a coupling facility failure may occur. See
Section 320.02 of the FDRPAS manual for more information.
An IPL is required to activate this fix.

REQUIRED 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.4 2.5 2.6 2.7 2.8 2.9 2.10 1.1 1.2 1.3 1.4
OW28455 C
OW28457 C
OW35913 C C C
OW37639 R R R R R
OW39622 R R R R R
OW47245 R R R R R
OW51565 C C
OW55435 C
C = Critical R = Recommended

Brief JES3 APAR descriptions follow:

OW55435/OW51565: these critical JES3 APARs prevent a S0C1 abend in JES3 after
a swap. This APAR can be installed without an IPL using dynamic LPA and JES3 hotstart.

OW47245/OW39622: These recommended JES3 APARs address 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.

OW37639: This recommended JES3 APAR prevents job failures if a JES3 hotstart is done during a swap. You do not need to IPL but a hotstart of JES3 is required to activate this fix.

OW35913: This critical JES3 APAR prevents a hang if a JES3 spool volume is swapped.
You do not need to IPL but a hotstart of JES3 is required to activate this fix.

OW28457/OW28455: These critical JES3 APARs are required to successfully swap volumes on a JES3 system. You must IPL to activate this fix.

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.