USP/NSC

MICROCODE VERSION 50-09-88-00/00

RELEASED 09/14/2009
Newly supported features and functions for Version 50-09-88-00/00
1. Mainframe & OPEN System
NONE

2. Mainframe System
NONE

3. OPEN System
NONE

The change of contents for Version 50-09-88-00/00

1 High cache write pending rate due to FCv2 pair T-VOL accesses
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Causes and Updates
Accesses to a target volume (T-VOL) of a Flash Copy Version2 (FCv2)
pair may cause cache write pending rate to exceed 70% (I/O inflow limit).
Worst case, the rate increases to nearly 100%, and systems may go down.
High
The failure may occur when all of the following conditions are met.
A. Code Versions: RAID500: All current versions
B. FCv2 configuration
C. A Read I/O operation from a host to a T-VOL of an FCv2 pair or 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 CLPR.
When FCv2 receives a read command for an un-copied area (*1) of T-VOL
from a host, the data is copied from a source volume (S-VOL) to the T-
VOL, and the copied data is reported to the host. 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

Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 50-09-88-00/00
Category Flash Copy Version 2
Changed Part DKCMAIN

2 FCA blockade failure resulted in time-out during data transfer

Phenomena When a failure occurred on a specific DKA PCB, an FCA was not blocked
HDS Confidential 1 of 3

Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
3 Failure during SI Pair Creation/Splitting and Volume Migration
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
4 (horctakeover) command took five minutes to complete
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
5 Data inconsistency occurs in FCv2 target volume
Phenomena
HDS Confidential
and many time-out errors occurred during drive data transfer.
Medium
Problem may occur when hardware-related failure occurs on a DKA PCB
DKCMAIN: All
DKCMAIN: 50-09-88-00/00
Open or mainframe
DKCMAIN
- When CVS volumes were created using OPEN-VOL other than OPEN-V
and an SI pair was created, data consistency rate did not reach 100%.
- When CVS volumes were created using OPEN-VOL other than OPEN-V
and an SI pair was split, failure suspend (PSUE) occurred.
- When CVS volumes were created using OPEN-VOL other than OPEN-V
and Volume Migration was performed, ABEND occurred.
Medium
The problem may occur when all the following conditions are met.
(1) Shadow Image or Volume Migration is used.
(2) OPEN-VOL other than OPEN-V is used.
(3) CVS volumes created with block number specified are used.
(4) At the time of the CVS volume creation, the number of blocks is
specified as follows.
Larger than (1440 x N - 1440) through smaller than (1440 x N - 95) (N:
integer number)
DKCMAIN: All
DKCMAIN: 50-09-88-00/00
Shadow Image, Volume Migration
DKCMAIN
When the horctakeover command of TCA Open was executed for RCU, it
took five minutes to complete.
In case of TCA for z/OS, when Suspend command of BCM with Reverse
option specified was executed, it might take five minutes to complete.
Low
The problem may occur when all the following conditions are met.
(1) MCU is RAID500 and RCU is RAID600.
(2) TCA for Open or z/OS pair is in DUPLEX status.
(3) MCU of RAID500 had been used as a RCU.
(4) The Suspend command of BCM with Reverse option specified is
executed for the RCU.
DKCMAIN: All
DKCMAIN: 50-09-88-00/00
True Copy Asynchronous for z/OS, True Copy Asynchronous
DKCMAIN
With a storage which uses Flash Copy Version2 (hereinafter refers to
FCv2), phenomenon A described below may occur. Besides, phenomenon
B may occur due to the occurrence of the phenomenon A.
2 of 3

Severity (High, Medium, Low)
Conditions of Occurrence
Causes and Updates
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
A. Data inconsistency occurs in an FCv2 target volume (T-VOL). (Data
inconsistency in the Data part of Record 0).
B. During access to the FCv2 T-VOL, I/O errors, such as No Record
Found, invalid record length, and track overrun, occur.
High
When all the following conditions are met, the failure may occur.
A. RAID500: 50-09-75-00/00 or higher.
B. System Option Mode 577 is OFF.
C. S-VOL and T-VOL of FCv2 are 3390-series drive simulation.
D. FCv2 S-VOL is updated.(*)
(*)Additional information:
In a dataset format like DAM or ISAM, job to update the Record 0, such as
restore job or dataset creation (FMTWR including Record 0), is executed.
During On-demand copy (*1) processing of FCv2, due to a failure of
micro-program, the copy to some HA/R0 slots (*2) may wrongly be
determined unnecessary so that some data copies of pre-update data (from
a source volume (S-VOL) to a T-VOL) are lost. Because of this, when
accessing to the FCv2 T-VOL, the post-update data can be read instead of
the pre-update data which is supposed to be read.
(*1) At the time of a host write operation to an un-copied area of FCv2 S-
VOL, the pre-update data is copied to the T-VOL.
(*2) HA/R0 slot: Slot where Record 0 and HA record of user track is
stored.
DKCMAIN: 50-09-75-00/00 and higher
DKCMAIN: 50-09-88-00/00
Flash Copy version2
DKCMAIN
3 of 3