9900V

MICROCODE VERSION 21-14-23-00/00

RELEASED 06/01/06
Newly supported features and functions for Version 21-14-23-00/00

NONE

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

(1) Support for Command Device Protection Feature

Item Description
Contents When a horcmstart.sh command executes, a RAID Manager message "HORCM inst XX has
failed to start." appears, and the RAID Manager startup fails. SSB: B9c0 occurs.
Conditions This problem occurs with all the conditions met 4096 times (Multiple accesses counted as one
access as long as their HOST WWN, LBA, and Port# are the same).
1. The target device is a command device.
2. LBA: F000-FFFF
3. TL=1 Read command
Category RAID Manager API
Changed DKCMAIN

(2) An LDEV Failed to be displayed on VLL Panel of Storage Navigator

Item Description
Contents On the VLL panel of Storage Navigator, a specific LDEV failed to display on the list of LDEV
information.
Conditions The problem occurs with all the conditions met:
1. The OPEN-V LDEV mounted at the top of the VDEV is a LUSE volume
2. The LUSE volume in #1 consists of the LDEV in the same VDEV
3. Displaying the LDEV in the VDEV in #2 on the VLL panel of Storage Navigator
Category Open Volume Management
Changed SVP

(3) No LDEV List Displayed on the VLL Panel of Storage Navigator

Item Description
Contents LDEV list not displayed on the VLL panel of Storage Navigator
Conditions The problem occurs with all the conditions met:
1. Select the top LDEV of the LUSE volume
2. Right click the LDEV and display a menu
3. Select the LDEV List from the menu
Category Volume Manager
Changed SVP

HDS Confidential 1of 3

(4) SI390 Pair Status Change Failure
Item Description
Contents Phenomenon 1:
The Shadow Image for S/390 pairs in the copy group did not change the status though
performing Split or Resync with specifying the copy group with Consistency Group defined
from the Business Continuity Manager.
Phenomenon 2:
The YKEWAIT command with a timeout value specified was timeout when monitoring whether
the pair status change was complete in Phenomenon 1.
Conditions Phenomenon 1 occurs when the following (1) (2) (3), or (1) (2) (4) or (1) (2) (5) or (1) (2) (6)
are met.
Phenomenon 2 occurs when the following (1)(2)(3)(7), or (1)(2)(4)(7) or (1)(2)(5)(7) or (1)(2)
(6)(7) are met.

1. Perform Split or Resync with specifying a copy group on which Consistency Group was
defined from the BCM
2. 17 or more CUs are mounted
3. An error occurs in the status change progress by performing Split with a copy group
specified, and performing Split with the copy group specified again before all the pairs
(including the pair where an error occurs) in the copy group complete their status change
4. An error occurs in the status change progress by performing Resync with a copy group
specified, and performing Resync with the copy group specified again before all the pairs
(including the pair where an error occurs) in the copy group complete their status change
5. Perform Split with a copy group specified, and perform Resync with the copy group specified
before all the pairs in the copy group complete their status change
6. Perform Resync with a copy group specified, and perform Split with the copy group specified
before all the pairs in the copy group complete their status change
7. Perform the YKEWAIT command with a timeout value specified
Category Shadow Image for S/390
Changed DKCMAIN

(5) SVP Memory Leak Problem

Item Description
Contents Phenomenon 1:
When using the export tool or the Storage Navigator, an error message displayed asking to call
the support center.
Phenomenon 2:
The operation from Hi-Command failed.
Conditions This problem may occur when the memory of SVP is full.
Phenomenon 1:
The switching operations between View and Modify on the Storage Navigator exceeds 10,000
times without rebooting the SVP.
Phenomenon 2:
The SVP connected to Hi-Command has not rebooted for more than one month.
Category RMI
Changed SVP

HDS Confidential 2of 3

(6) Failure on a Shadow Image pair of LUSE volumes causes data inconsistency
Item Description
Contents When a Shadow Image or Hi Copy pair of LUSE volumes suspends with failure, any one of the
following Contents happens on one or two pairs other than the suspended pair:
[P1] A Shadow Image pair suspends with failure upon the Split operation
[P2] Data inconsistency occurs on a target volume of a pair of Shadow Image Volume
Migration, Flash Copy V1, Flash Copy V2, or Hi Copy
[P3] Volume Migration fails
[P4] A Hi Copy pair suspends with failure
When a Shadow Image or Hi Copy pair of LUSE volume suspends, an internal table of MU#0
of the source volume corrupts, because the use of the corrupted information, when a host writes
data to the source volume, a wrong differential bitmap is to be set.
Conditions This problem occurs with A or B met.
A. A Shadow Image pair of LUSE volumes suspends with failure (RAID300, 400 or 450). SIM
47Dxyy is reported
B. A Hi Copy pair using MU#1 or 2 of LUSE volumes suspends with failure (RAID450). SIM
4B1xyy is reported
The followings are the trigger to make above A or B suspend.
1. The Cache ECC/LRC error occurs (Hardware failure)
2. 2 PDEV blocked
3. A LDEV on an external storage system is blocked (in case of Hi Copy)
Category Shadow Image/ Shadow Image - S/390,
Changed DKCMAIN

HDS Confidential 3of 3