9900V

MICROCODE VERSION 21-14-56-00/00

RELEASED 03/26/2010
Newly supported features and functions for Version 21-14-56-00/00
1. Mainframe & OPEN System

1-1 Communication error flag unset

Description With the previous versions, when an SVP with Hi-Track or C-Track installed is in reboot
progress, information fetching (Rmapi configuration reference function) of Hi-Track or C-
Track may be timeout and then causes a communication error so that when performing
Apply on the Storage Navigator, error message 2-58578 occurs and an All Refresh operation
is required to recover the problem.
With this version, the above timeout does not have the communication error flag set so that
the All Refresh operation on the Storage Navigator is no longer necessary.
Changed Part SVP

2. Mainframe System
None

3. OPEN System
None

The change of contents for Version 21-14-56-00/00

1 Correction copy at multiple parity groups due to HDDs blockade Description
Phenomena As multiple HDDs were blocked, multiple parity groups fell into the correction copy state.
Conditions The problem occurs when all the following conditions are met.
21-14-20-00/00 and higher
Read I/O.
An OXID among HDD response information becomes invalid.
Category HDD
Changed part DKCMAIN

2 During True Copy Async operation, WCHK1 occurs in RCU MP Description

Phenomena When a True Copy Async operation is performed, WCHK1 may occur in all CHPs in DKC in
which S-VOL exists, and all the CHPs may be blocked
Contents The settling processing in RCU has microcode bug that falsely releases side-file being used.
Because of this, the cache segment released falsely may be used in other processing, and an
LA error could occur.
Conditions When all the following conditions are met, the failure may occur.
A. All current versions
B. True Copy Async S-VOL exists
Category True Copy - S/390 or Open
Changed part DKCMAIN

HDS Confidential 1of 2

 3 High cache write pending rate due to accesses to FCv2 pair T-VOL Description
Phenomena The following cases may cause cache write pending rate to exceed 70% (I/O inflow limit). In
the worst case, the rate increases to nearly 100%, and systems may go down.
(1-1) Read I/O from a host to a target volume (T-VOL) of a Flash Copy Version2 (FCv2) pair
(1-2) A write I/O operation from a host to a source volume(S-VOL) of an FCv2 pair in a
configuration where the S-VOL and T-VOL are defined in different CLPRs
Contents Either the time when FCv2 receives a read command for an un-copied area (*1) of T-VOL
from a host or the time when the volume of an FCv2 pair combined with the volume of TC or
UR, the data is copied from an S-VOL to the T-VOL. During the copy operation from the S-
VOL to T-VOL, dirty data is generated in cache. At this time, due to a failure of micro-
program, the overload control is not performed for the cache and the aforementioned dirty
data is continuously generated without limitation, which results in the above phenomenon.
(*1) An area, where the data of S-VOL is not reflected to T-VOL
System Option Mode 364 is available to disable this fix.
Restricted Mode – RSD Permission Required to Use
Conditions (Phenomenon 1)
The failure may occur when all the following conditions (A) to (C) are met.
A. The following micro-program versions
RAID450: 21-10-08-00/00 and higher
B. FCv2 configuration
C. A Read I/O operation from a host to a T-VOL of an FCv2 pair

(Phenomenon 2)
The failure may occur when all the following conditions (A) to (C) are met.
A. The following micro-program versions
RAID450: 21-10-08-00/00 and higher
B. FCv2 configuration
C. A write I/O operation from a host to an S-VOL in a configuration where the S-VOL and T-
VOL are defined in different CLPRs.
Category Flash Copy Version 2, True Copy - S/390
Changed part DKCMAIN

4 Failure of DKA installation and de-installation

Phenomena Installing DKA for the installation of L1 frame failed. After that, when the DKA was de-
installed for recovery, the status of DKA became invalid, and then the maintenance operation
failed.
Conditions The problem occurs when all the following conditions are met.
(1) All current versions
(2) Despite the successful end of a DKA blockade, when the DKA is de-installed, it is in
recovery status due to a hardware problem of the DKA.
(The root cause of the DKA recovery status on the DKCMAIN side has not been identified.)
Category Open or mainframe
Changed part SVP

HDS Confidential 2of 2