9960

MICROCODE VERSION 01-19-99-00/10

RELEASED 2/29/2008
Newly supported features and functions for Version 01-19-99-00/10

NONE

The change of contents for Version 01-19-99-00/10

1 Running SVP/Storage Navigator operation etc. and Volume Migration/Quick

Restore operation in parallel causes data inconsistency
Phenomena When one of the following operations performed by the SVP or the Storage Navigator,
-ECC group installation/de-installation, -CVS configuration operation, -System Option setting
operation and one of the following operations
-Volume Migration operation, -Quick Restore operation -Cache Residency setting (Placing
specific data to cache memory) by the mainframe host　run in parallel, the configuration
information becomes invalid, and one of the following phenomena (1 to 4) occurs.
Phenomenon 1: When an I/O is in progress in the LDEV to which a Volume Migration or Quick
Restore operation is performed, an LA error (CHK2) occurs. Alternatively, because the threshold
of CHK2 is exceeded, the CHA is blocked due to WCHK1, or the FCA in the DKA is blocked.
Phenomenon 2: An I/O is issued to the VDEV to which a Volume Migration or Quick Restore
operation is not performed yet, and a data inconsistency occurs.
Phenomenon 3: According to the specifications, 4096 Cache Residency cache extents can be set in
the entire system. Before 4096 cache extents are set, however, no more cache extent can be set.
Phenomenon 4: The Cache Residency setting made by the mainframe host (performed by Cache
Manager Utility, hereinafter referred to as CMG) does not make the configuration as set. In
addition, the I/O performance may be degraded as a result.

HDS Confidential 1of 3

Contents 1. When each of the following operations are performed from the SVP or the Storage Navigator,
(a) ECC group installation/de-installation
(b) CVS configuration operation
(c) System Option setting operation and
(d) Volume Migration operation
(e) Quick Restore operation
(f) Cache residency setting by the mainframe host is performed; the LDEV-VDEV mapping table
and the LDEV attribute information need to be updated.
At the time of the operations (a), (b), and (c), the SVP or the Storage Navigator reads these tables
from the DKC and reflects the results of updates in the entire tables to the DKC.

When the operations (d), (e), and (f) end, the DKCMAIN micro-program updates the LDEV-
VDEV mapping table or the LDEV attribute information.

In the case one of the operations (a), (b), or (c) and one of the operations (d), (e), or (f) run in
parallel, though the LDEV-VDEV mapping table or the LDEV attribute information is updated by
(d), (e), or (f), the SVP or the Storage Navigator reflects the change made by (a), (b), or (c) to the
DKC. As a result, the change made by (d), (e), or (f) is overwritten, and the information is restored
to the old one.

2. Cause of each phenomenon

Phenomenon 1: When an I/O is issued to the LDEV to which Volume Migration or Quick Restore
is performed, if this problem occurs, the VDEV# of before the Volume Migration or Quick
Restore operation is performed is obtained at the time of LDEV-VDEV conversion. Since an I/O
is processed for a different VDEV, an LA error occurs.
Phenomenon 2: Due to the same reason as Phenomenon 1, an I/O is processed for the VDEV to
which the Volume Migration or Quick Restore operation is not performed yet. As a result, a data
inconsistency occurs.
Phenomenon 3: The Cache Residency setting information consists of two types of information:
the information that shows the LDEV attribute and the information that manages the cache
residency areas (hereinafter referred to as residency management information). When this
problem occurs at the time of Cache Residency setting, the LDEV attribute information is restored
to the old one, and unusable areas exist in the Cache Residency management information.
Therefore, before 4096 Cache Residency cache extents are set, the Cache Residency management
information runs out.
Phenomenon 4: The Cache Residency setting information consists of two types of information:
the information that shows the LDEV attribute and the Cache Residency management
information. When this problem occurs at the time of Cache Residency setting, the LDEV
attribute information is restored to the old one, and the association with the Cache Residency
management information becomes invalid. As a result, the residency configuration becomes
different from the one that was set. This may lead to performance degradation.

The micro-program has been modified to fix the problem

HDS Confidential 2of 3

Conditions When either of the conditions A or B is met, the problem of invalid configuration information
described in “Phenomena” occurs in all current versions.

A. Either of the following processing performed by the SVP or the Storage Navigator,
-ECC group installation/de-installation
-CVS configuration operation
and either of the following processing,
-Volume Migration or Quick Restore
-Cache Residency setting (Placing specific data to cache memory) by the mainframe host runs in
parallel.

B. When one of the following processing performed by the SVP or the Storage Navigator,
-ECC group installation/ de-installation
-CVS configuration operation
and one of the following processing,
-Volume Migration or Quick Restore
-Cache Residency setting (Placing specific data to cache memory) by the mainframe host run in
parallel, and during the processing performed by the SVP or the Storage Navigator (from the start
to the end), one of the following operations is performed.
-Open the Maintenance window
-Refresh the Maintenance window
-Refresh the Storage Navigator

Category Open or mainframe

Changed DKCMAIN /SVP

HDS Confidential 3of 3