Anda di halaman 1dari 25

VSP

MICROCODE VERSION 70-04-51-00/00-M122


RELEASED 08/10/2012

New supported features and functions for Version 70-04-51-00/00-M122


1. Mainframe & OPEN System

1-1 Improvement for Performance Utilization per tier


Description When the monitoring mode is set to Continuous Mode, the following items are displayed
with the values calculated by using monitoring values same as those used in Period Mode.
Performance Utilization (Storage Navigator, RAID Manager)
IOPH per tier (RAID Manager Lib)
Changed Part DKCMAIN

1-2 Enhancement for SMI-S


Description The following function enhancements are implemented for SMI-S.
Local Replication support and SMI-S1.5 support
Changed Part SVP

1-3 Support for System Option Mode784


Description System Option Mode 784 is available to reduce MIH time of RIO for TC/TCz pairs created
during SOM784 ON to 5 seconds so that, even though an RIO path failure occurs, update
I/O processing can be switched to an alternate path promptly, lowering the possibility of
host MIH occurrence. Public Mode – No Permission Required to Use

RIO MIH time can be changed from Storage Navigator within range from 10 to 100 sec, but
10 sec is the shortest to set. If RCU registration is performed from PPRC/BCM, the MIH
time is fixed at 15 sec. For True Copy, this mode is effective only when both MCU and
RCU are RAID700 and have the supported micro-program version.
For True Copy for Mainframe, this mode is effective when either MCU or RCU is RAID700
or RAID600 and has the supported micro-program version (supported RAID600 versions
are 60-07-53-00/00 and higher).
Changed Part DKCMAIN

1-4 Improvement for Encryption License Key function


Description The following are supported for the Encryption License Key function.

Generating encryption keys in a key management server that complies with KMIP.
Returning the setting of “Generate Encryption Keys on this server” back from key
generation on key management server to key generation on DKC can be disabled.
Changing the encryption logic when storing data encryption keys in DKC to AES KW
mode. Enabling to set an input policy for the password that needs to be entered at backup of
encryption keys in an external file.
Changed Part DKCMAIN, SVP, Storage Navigator

HDS Confidential 1 of 25
1-5 SOM class change
Description The class of System Option Mode 769 has changed from “RSD” to “Public” from
DKCMAIN version 70-04-51-00/00.

Public Mode – No Permission Required to Use

Changed Part Config

1-6 Improvement for 3 UR DC cascade configuration


Description In 3DC cascading configuration with three UR sites, when copying data from the remote
site to the local site via the intermediate site, the data volume at the intermediate site
becomes a secondary volume shared by two primary volumes and data copy is available via
the two pairs. However, the copy from the intermediate site to the local site becomes all data
copy.

Changed Part DKCMAIN

2. Mainframe System
NONE

3. OPEN System

3-1 Support for Flash Acceleration


Description The performance is improved at cache miss for Simplex VOL, DP-VOL and PP-VOL in
OPEN environment by reducing micro-program processing.

The PP license of Flash Acceleration must be installed to enable this function.


Changed Part DKCMAIN

The change of contents for Version 70-04-51-00/00-M122


1 Environment monitor disabled during HDD micro-program
exchange
Phenomena During HDD micro-program exchange, if WCHK1 or CHK3 occurred,
the environment monitor was disabled and malfunctions of FAN and
DKU PS could not be detected. SSB=A670 and 160X were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) HDD micro-program is being exchanged.
(2) WCHK1 or CHK3 occurs.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category HDD
Changed Part DKCMAIN

HDS Confidential 2 of 25
2 Data inconsistency occurs in True Copy secondary volume
Phenomena The following phenomena may occur in the secondary volume of True
Copy (hereinafter referred to as “TC”) pair.
OPEN volume: A data inconsistency occurs in the secondary volume of
TC pair.
Mainframe volume: When the host reads the secondary volume, EQC
(Equipment check) is reported to the host (SSB EC=5860).
Severity (High, Medium, Low) High
Conditions of Occurrence May occur with all the following conditions A, B, C, and D met, or all A,
B, C and E met.

A. RAID700 All current versions


B. TC configuration
C. In the line between MCU and RCU, a data transfer delay of 15 seconds
or more occurs
D. Initial copy or update copy is performed with HostModeOption 51
OFF (Round Trip Set Up Option)
E. Initial copy is performed with all the following conditions (a) to (c).
(a)HostModeOption 51 ON
(b)HostModeOption 65 ON (Round Trip Extended Set Up Option)
(c)Full installation of MPB (2Module (32MP)) in DKC of the RCU side
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category True Copy, True Copy for Mainframe
Changed Part DKCMAIN

3 Disk access error in zLinux environment


Phenomena When IPL (initial program loader) was performed for zLinux (SuSE or
RedHat) or zVM LPAR whose guest OS is zLinux(SuSE or RedHat)
connected to RAID700 through FICON, a disk access error occurred
(SSB EC=6DB2) and the operation (IPL) failed.
Also, a disk access error (SSB EC=6DB2) occurred with zLinux (SuSE or
RedHat) or zVM LPAR whose guest OS is zLinux(SuSE or RedHat)
connected to RAID700 through FICON during I/O processing and the
system goes down.
Severity (High, Medium, Low) High
Conditions of Occurrence The problem occurs when all the following conditions (A) to (C) are met.

A. RAID700 70-04-01-00/00 and higher


B. FICON connection (Mainframe connection)
C. zLinux (Suse11SP1 and later, or RedHat6 and later) is used.

(Supplementary explanation)
In zOS or zVM environment, if there is an application or an operating
system that issues x23 of extended operation code in Prefix (xE7)
command, a command reject is reported and the job may end abnormally.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Mainframe
Changed Part DKCMAIN

HDS Confidential 3 of 25
4 Data inconsistency occurs after DKC detects medium error of
3TB HDD
Phenomena Any of the following phenomenon (one or more) may occur after DKC
detects HDD medium error (SSB EC=A403) in the RAID system that
includes DKS2D-H3R0SS HDDs.

Phenomenon 1: In the case of Write I/O, old data in the HDD are left
without updating write data. After that if a read I/O to the LBA indicated
by medium error is performed and succeeded, the old data are read, which
results in data inconsistency.
Phenomenon 2: DKC detects CHK2 error (SSB EC=A443)
Phenomenon 3: The HDD may be blocked because of the threshold over
of the medium error.

In addition, as for this phenomenon1 and 2, the data of the HDD can be
restored with collection copying that is performed by HDD replacement
operation.
Severity (High, Medium, Low) High
Conditions of Occurrence The problem may occur when all the following conditions are met.

A. RAID700 Ver.70-03-36-00/00 or later


B. DKS2D-H3R0SS HDDs are installed
C. Medium error (SSB EC=A403) occurs in an HDD mentioned in B
Affected Products/Version DKCMAIN: 70-03-36-00/00 or later
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Open or Mainframe
Changed Part DKCMAIN

5 Storage Navigator message display error for pool VOLs


registration at pool creation
Phenomena In a case that pool VOLs registration failed due to exceedance of licensed
capacity at pool creation, Storage Navigator message 3005-58467 was
output on Tasks window for pool VOLs whose registration succeeded or
the message was not output for pool VOLs whose registration failed.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Pool creation is performed while multiple pool VOLs are specified.
(2) The above task fails due to exceedance of licensed capacity.
Affected Products/Version DKCMAIN for Open: All
DKCMAIN for Mainframe: 70-02-54-00/00 and higher (DPz), 70-03-01-
00/00 and higher (DTz)
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic
Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

HDS Confidential 4 of 25
6 Failure of DP pool initialization during zero data page reclaim
Phenomena When DP pool initialization was executed during zero data page
reclamation, the initialization might fail, and Storage Navigator message
3005-7310 and SSB=2B00 and AF53 were output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Zero data page reclaim or DP VOL capacity expansion is performed.
(2) During the above processing, DP pool initialization is performed.
Affected Products/Version DKCMAIN for Open: All
DKCMAIN for Mainframe: 70-02-54-00/00 and higher (DPz), 70-03-01-
00/00 and higher (DTz)
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic
Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

7 Failure of external VOL recovery from Storage Navigator


Phenomena When Reconnect External Volumes was executed from Storage
Navigator for an external VOL that was blocked at pool creation or
expansion while using the external VOL as a pool VOL, the operation
succeeded but external VOL remained blocked and was not recovered.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Pool creation or expansion is performed while using an external VOL
as a pool VOL.
(2) During the above processing, the external VOL is blocked. (An I/O to
the external VOL is disabled or a path to the external VOL is blocked.)
Affected Products/Version DKCMAIN for Open: All
DKCMAIN for Mainframe: 70-02-54-00/00 and higher (DPz), 70-03-01-
00/00 and higher (DTz)
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic
Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

8 Failures of de-staging and PS OFF


Phenomena Host I/O (write) issued to DP-VOL in zero data page reclaim or rebalance
(pool expansion, pool shrink, or tier relocation) processing, de-staging
was disabled and a PS OFF failure with SSB=9C89 & 2CF3 output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Zero data page reclamation or rebalance (pool expansion, pool shrink,
and tier relocation) is performed.
(2) A host I/O (write) is issued to a DP-VOL in the above processing.
(3) PS OFF is performed.
Affected Products/Version DKCMAIN for Open: All DKCMAIN for Mainframe: 70-02-54-00/00
and higher (DPz), 70-03-01-00/00 and higher (DTz)
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic
Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

HDS Confidential 5 of 25
9 Failure of TCz pair creation on FC target side after deletion
Phenomena In Preserve Mirror configuration, when a TCz pair volume on the FC T-
VOL side was deleted and then the pair was created again, the operation
failed with SSB=968F output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Preserve Mirror configuration
(2) A TCz pair volume on the FC T-VOL side is deleted and then the pair
is created again.
(regardless of whether it is a P-VOL or S-VOL of TCz )
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category True Copy for Mainframe, Flash Copy version2
Changed Part DKCMAIN

10 Failure of rebalance or zero data page reclamation


Phenomena If an MP or MPB was blocked during rebalance (pool expansion, pool
shrink, tier relocation) or zero data page reclamation processing, the
processing might fail and SSB=AFE1 was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Rebalance (pool expansion, pool shrink, and tier relocation) or zero
data page reclamation is performed.
(2) An MP or MPB is blocked during the above processing.
Affected Products/Version DKCMAIN for Open: All
DKCMAIN for Mainframe: 70-02-54-00/00 and higher (DPz), 70-03-01-
00/00 and higher (DTz)
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic
Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

11 Failure suspend of CoW Snapshot pair with SSB output


Phenomena Due to an MPB blockage during copy processing accompanied with pair
restore processing or a write I/O to P-VOL or S-VOL of a CoW Snapshot
pair, the CoW Snapshot pair might be suspended due to failure and
SSB=979D or 9713 was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions (1) and (4), (2)
and (4), or (2) to (4) are met.
(1) A write I/O is issued to P-VOL or S-VOL of a CoW Snapshot pair in
PSUS status.
(2) A restore operation is executed for a CoW Snapshot pair and the pair
status becomes COPY (RS-R).
(3) A write or read I/O is issued to P-VOL of a CoW Snapshot pair.
(4) An MPB is blocked.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Copy-on-Write Snapshot
Changed Part DKCMAIN

HDS Confidential 6 of 25
12 Copy pace slowdown in cascade configuration with 3 UR/URz
sites
Phenomena In cascade configuration with 3 UR/URz sites, when a resync operation
was performed for a pair or a pair was newly created between I site and R
site, and then a pair between P site and I site was suspended, copy pace of
the pair between I site and R site got slow.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Open or Mainframe
(2) Cascade configuration with 3 UR/URz sites
(3) I site
(4) A resync operation is performed for a pair or a pair is created between
I site and R site, and then a pair between P site and I site is suspended.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

13 Invalid increase in write pending rate by tier relocation when


the rate is 70% or higher
Phenomena When tier relocation was performed while write pending rate was 70% or
higher, the write pending rate might wrongly rise and SSB=14FF and
14DC were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Write pending rate is 70% or higher.
(2) Tier relocation is performed in the above condition.
Affected Products/Version DKCMAIN for Open: All
DKCMAIN for Mainframe: 70-02-54-00/00 and higher (DPz), 70-03-01-
00/00 and higher (DTz)
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic
Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

14 Failure of SSB Log# assignment


Phenomena Basically, SSB logs created by SVP are within the range from 61440 to
65535. But if log # exceeds 65535, a number out of the range (from 1 to
61439) is assigned. In this case, when the Refer button is clicked on
Content-SSB window of Information window, the related SSB may not
be displayed correctly.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when SVP creates an SSB while Log# reaches
65535.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-04-51/00
Category Open or Mainframe
Changed Part SVP

HDS Confidential 7 of 25
15 Failure of multiple pool deletion while background format is in
process
Phenomena When multiple pools were deleted at a time while background format was
working, time-out occurred (Storage Navigator message 3005-58491) and
the deletion of some pools failed (SSB=391A).
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Background format is in process. (SOM896 is set to ON.)
(2) Pool deletion with multiple pools selected is performed.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic
Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

16 Invalid copy status after initial copy with No copy or resync


operation
Phenomena When UR/URz initial copy with No copy specified was performed or a
resync operation was performed for a pair in suspend status without I/O,
the status remained in COPY but did not change to PAIR.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Universal Replicator or Universal Replicator for Mainframe
(2) Initial copy with No copy specified is performed or resync is
performed for a pair in suspend status without I/O.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator or Universal Replicator for Mainframe
Changed Part DKCMAIN

17 Failure suspend in pair between I site and R site with


SSB=EF91 output
Phenomena In cascade configuration with URz, after a pair between P site and I site
was suspended, a resync operation was performed and a pair between I
site and R site was automatically suspended.
After the above operation, when the pair between P site and I site was
suspended again during resync operation for the automatically-suspended
pair (between I site and R site), failure suspend occurred in the latter pair
(between I site and R site) and SSB=EF91 was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Cascade configuration with URz
(2) During a resync operation for a pair between I site and R site, a
suspend operation (Flush or Purge) or deletion (per mirror) is performed
for a pair between P site and I site.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 8 of 25
18 Failure suspend in P-I site pair with SSB=EF45
Phenomena In cascade configuration with UR/URz, when a resync operation was
performed for a pair between I site and R site during ownership migration
at I site, failure suspend occurred in a pair between P site and I site and
SSB=EF45 was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Cascade configuration with UR/URz
(2) Ownership migration occurs at I site
(3) During the above ownership migration, a resync operation was
performed for a pair between I site and R site.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

19 Failure of SSD recovery due to drive blockage


Phenomena In limit performance condition with 64 tags, the response time of SSD
when read/write ratio is 0:100 is double compared to that when the ratio
is 50:50. During drive recovery, as the ratio of the copy target drive may
be 0:100 while that of the copy source drive is 50:50, the performance of
copy target is worse than that of copy source. When a check for delay
works under the above condition, a copy target drive is determined as
delayed. In this case, if SOM144 is set to ON, the copy target drive is
blocked and the drive recovery fails.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) 2-module configuration.
(2) An SSD drive is being recovered.
(3) SOM144 is set to ON.
Affected Products/Version DKCMAIN: 70-01-62-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category HDD
Changed Part DKCMAIN

20 Invalid pair status when failure occurs between I site and R site
Phenomena Failure between I site and R site in 3DC cascade configuration with 3
UR/URz sites, the pair status remained in Suspending and
SIM=DC1XXX, DC2XXX, DC4XXX, or DC7XXX was output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Universal Replicator or Universal Replicator for Mainframe
(2) 3DC cascade configuration with 3 UR/URz sites
(3) Pair option error level between I site and R site is Lu.
(4) Mirror status between P site and I site is Active.
(5) Failure suspend occurs during initial copy between I site and R site.
Affected Products/Version DKCMAIN: 70-03-33-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator or Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 9 of 25
21 Invalid JNL usage rate display
Phenomena When a delta UR pair was deleted in 3DC multi-target or 3DC cascade
delta configuration with UR only, the JNL usage rate did not become 0%.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Open
(2) L site or R site of 3DC multi-target delta configuration with UR only,
or P site or R site of 3DC cascade delta configuration with UR only
(3) Remote command devices are assigned to all sites.
(4) JNL usage rate at the site of (2) is 1% or above.
(5) The assigned remote command devices are released.
(6) A delta UR pair is deleted.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator
Changed Part DKCMAIN

22 Failure suspend with SSBs output at resync operation after


cache failure recovery
Phenomena During UR/URz initial copy using DP VOLs for both P-VOL and S-
VOL, a one-side cache failure occurred, and failure suspend occurred in
accordance with the specification for cache failure during copy
processing. When the cache failure was solved and a resync operation
was performed for the pair, SSB=AF52, 140B, and 3784 or 37A0 were
output and failure suspend occurred.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Universal Replicator or Universal Replicator for Mainframe
(2) Initial copy using DP VOLs for both P-VOL and S-VOL
(3) A failure reset (other than WCHK1) occurs during the initial copy
processing.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator or Universal Replicator for Mainframe
Changed Part DKCMAIN

23 Response delay with SSB=DD08 output


Phenomena SSB=DD08 was output and a response was delayed.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Open host connection
(2) Multiple alternate paths (CHT PCBs are connected with different
ports) are connected to an LDEV.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Open
Changed Part DKCMAIN

HDS Confidential 10 of 25
24 Display failure on Universal Volume Manager Window
Phenomena Phenomenon1
After volume migration from an external VOL to a DP VOL by using
Volume Migration, when the volume migration result was confirmed on
Universal Volume Manager window of Storage Navigator, the LDEV ID
displayed was not that after migration but was the one before migration.

Phenomenon2
In each case of the following operations, the LDEVs added or removed
were not reflected on Universal Volume Manager window.
a. An LDEV is added to a parity group of an external storage to which
LDEVs have already been allocated.
b. LDEVs are removed from a parity group of an external storage,
however, the number of LDEVs left in the parity group is not zero.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met for each
phenomenon.
Conditions for Phenomenon1
(1) Volume migration including the processing for an external VOL is
performed.
(2) Universal Volume Manager window is displayed.

Conditions for Phenomenon2


(1) After LDEV addition or removal from number "n" to number "m",
the number of LDEVs left in the parity group of external storage is not
zero.
(2) Universal Volume Manager window is displayed.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-04-51/00
Category Volume Migration, Universal Volume Manager
Changed Part SVP

25 Failure suspend of UR/URz pair with SSB and SIM output


Phenomena When a UR/URz pair was suspended in 3DC multi-target delta
configuration, the suspend turned to failure suspend and SSB=EC01 and
SIM=DC1XXX were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) 3DC multi-target delta configuration
(2) A TC/TCz pair is in PAIR status.
(3) LDEV#0x0000 is not registered in the configuration.
(4) A host I/O is issued.
(5) A suspend operation is executed for a UR/URz pair.
Affected Products/Version DKCMAIN: 70-03-38-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 11 of 25
26 No progress for task status on Tasks window
Phenomena On Tasks window of Storage Navigator, display of progress status for a
task did not change after Apply was clicked. The task itself was
completed and ended normally.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when one of the following operations is executed for
a Mainframe volume on Storage Navigator.
- Format task
- Shredding task
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-04-51/00
Category Virtual LVI
Changed Part SVP

27 Receipt of incorrect information when sysObjectID in Standard


MIB is obtained
Phenomena When sysObjectID in Standard MIB was obtained, information different
from that described in SNMP Agent User Guide was received and
therefore an icon of RAID was not displayed on JP1.
In particular, described information and received information are as
follows.
Described: 1.3.6.1.4.1.116.3.11.4.1.1
Received: 1.3.6.1.4.1.116.3.11.4.1.1.0
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when sysObjectID in Standard MIB is obtained.
Affected Products/Version SVP: 70-02-77/00 and higher
Fixed Product/Version SVP: 70-04-51/00
Category Open or Mainframe
Changed Part SVP

28 Failure of DKC display at UR/URz pair creation


Phenomena At pair creation while selecting an S-VOL that had only one mirror from
a JNL with two mirrors registered, when a pair displayed in Preview was
selected and then Paircreate dialog box was opened again to modify a
parameter, the following phenomena occurred.
(1) A DKC with an already paired mirror was displayed. The DKC was
different from that of the mirror (displayed in Preview) used when
Paircreate dialog box was opened for the first time.
(2) The DKC of mirror was fixed to the above one and could not be
changed to another one to be paired.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) A UR/URz pair is created while selecting a pair that has only one
mirror from a JNL with 2 mirrors registered.
(2) The above pair is selected in Preview and the Paircreate dialog box is
opened again.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-04-51/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part SVP

HDS Confidential 12 of 25
29 Failure suspend of URz pair with SSB=EF91 output
Phenomena In delta configuration with TCz-URz, SSB=EF91 was output and a delta
pair was suspended due to failure.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) URz pair.
(2) Delta configuration with TCz-URz
(3) JNLG ownership and I/O target LDEV ownership do not belong to the
same MPB.
(4) While receiving an I/O, a URz pair is suspended (by failure or
operation), and then a delta resync operation is executed at L site.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator for Mainframe
Changed Part DKCMAIN

30 WCHK1 with SSB=1644 output during I/O processing


Phenomena During I/O processing in 3DC configuration with UR/URz , WCHK1
occurred and SSB=1644 was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when one of the following conditions is met.
(1) The number of JNL groups (total of MCU and RCU) is 49 or more in
UR Open or Mainframe environment.
(2) The number of JNL groups (total of MUC and RCU) is 48 or less in
UR Mainframe environment.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

31 ABEND of new data set creation on track without page


allocation
Phenomena When a new data set was created on a track without page allocation, the
job might end abnormally (abend code=614 or 314) and SSB=6709 was
output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) DP for Mainframe volume or FCSE target volume.
(2) A format write I/O is issued to a track without page allocation.
(3) A CCW chain that searches by a search ID command after positioning
by a set sector command.
(4) A sector number of the above set sector command is 0x06 or higher
and REC#0 is searched.

Note: An I/O that meets the above conditions (3) and (4) is not issued by
IBM host utilities.
Affected Products/Version DKCMAIN: 70-02-54-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning for Mainframe, Flash Copy SE
Changed Part DKCMAIN

HDS Confidential 13 of 25
32 SVP message 4093E when Offline SVP tool is executed
Phenomena When using the Offline SVP tool to read a spreadsheet, if only the top
RAID group was described to define a RAID configuration of 14D+2P,
an error occurred and SVP message 4093E was output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) All of 4 RAID groups constituting a 14D+2P configuration are not
defined in a spreadsheet.
(2) The Offline SVP tool is used to read the spreadsheet in (1).
Affected Products/Version SVP: 70-04-01/00 and higher
Fixed Product/Version SVP: 70-04-51/00
Category Open or Mainframe
Changed Part SVP

33 WCHK1 in MP during post processing for WCHK1 reset


Phenomena In URz configuration (including 3DC configuration), when WCHK1
occurred (SSB=1644) and then a post processing for the WCHK1 reset
was executed, WCHK1 occurred in an MP that processed the WCHK1
reset and SSB=1644 was output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Universal Replicator for Mainframe.
(2) In URz pair configuration (including 3DC configuration), P-VOL and
S-VOL of a URz pair are in the same storage.
(3) During I/O processing to the P-site, WCHK1 occurs.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator for Mainframe
Changed Part DKCMAIN

34 Failure suspend of UR/URz pair during data restoring


Phenomena After a PDEV in a parity group to which a JNL VOL belonged failed
during an update I/O to a UR/URz pair, failure suspend occurred in the
UR/URz pair during data restoring by copy back or correction copy and
SSB=EC81 and EC94 were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when a Universal Replicator or Universal
Replicator for Mainframe pair is used.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 14 of 25
35 Failure suspend of URz pair with SSB=EF47 output
Phenomena During URz initial copy, when MPB maintenance was performed on the
RCU side, the URz pair was suspended due to failure and SSB=EF47 was
output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Universal Replicator for Mainframe
(2) An MPB (all MPs) on the RCU side is blocked due to failure.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator for Mainframe
Changed Part DKCMAIN

36 Failure suspend of UR/URz pair between P site and I site


Phenomena In cascade configuration with UR/URz, when an MPB failure occurred at
I site during resync operation for a pair between I site and R site, a
UR/URz pair between P site and I site was suspended due to failure and
SSB=EF47 was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Cascade configuration with UR/URz
(2) An MPB failure blockage (all MPs blockage) occurs at I site.
Affected Products/Version DKCMAIN: 70-03-38-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

37 Disabled access from ESX server after sudden MP blockage


Phenomena An MP was suddenly blocked and access from an ESX server was
disabled.
The reason the access was disabled was due to MP blockage caused by
frequent LA errors.

When the above occurred, SIMs and an SSB below were output.
SIM for logical DMA blocking: CF6220, CF6203, CF6201, CF6221, and
CF6222
SIM for processor blocking: 307323, 307322, 307320, and 307321
SSB=D2ED
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur at an SCSI reset but the detail is unknown.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Open
Changed Part DKCMAIN

HDS Confidential 15 of 25
38 SSB=E7A0 output at cycle change
Phenomena During DT/DTz operation in Auto execution mode, SSB=E7A0 might be
output at cycle change.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) A target pool is DT/DTz pool and Auto execution mode is set.
(2) The previous relocation is not completed in the cycle.
Affected Products/Version DKCMAIN for Open: All
DKCMAIN for Mainframe: 70-03-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

39 WCHK1 with SSB=1644 in MP that is not in blocked MPB


Phenomena When an MPB was blocked in a UR/URz configuration, WCHK1
(SSB=1644) might occur in an MP that was not in the MPB.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) There is a UR/URz pair.
(2) An MPB is blocked.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Open or Mainframe
Changed Part DKCMAIN

40 Failure of UR/URz pair creation


Phenomena Phenomenon1
When a pair creation failed, the pair status was SMPL but licensed
capacity of the failed pair increased. (SSB=E883, Storage Navigator
message=6505-58088, CCI/BCM error code=E883). At that time, an
existing UR/URz pair was suspended due to failure.
Phenomenon2
After the phenomenon1, when an LDEV used for the failed pair creation
was selected and then a pair creation was performed again, a message
saying that UR had already been registered was output and the pair
creation failed. (SSB=EA01 or EA03, Storage Navigator message=6505-
58288 or 6505-58289, CCI/BCM error code=EA01 or EA03)
Severity (High, Medium, Low) Low
Conditions of Occurrence Phenomenon1 may occur with the following conditions (1) to (4) met.
The phenomenon2 may occur when all the following conditions are met.
(1) Universal Replicator or Universal Replicator for Mainframe
(2) A pair is registered in a mirror.
(3) A pair is created for the above mirror as its 2nd pair.
(4) The above pair creation fails.
(5) A pair creation is performed while specifying LDEV# and mirror#
which are specified in the pair creation of (3).
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 16 of 25
41 Failure suspend of UR/URz pair instead of JNL Meta data full
suspend
Phenomena In 3DC cascade configuration with UR/URz only or 3DC multi-target
delta configuration with UR only, a failure suspend occurred instead of a
JNL meta data full suspend, and SSB=EC01, EC59, EC5C and EDDF
and SIM=DC1XXX were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) I site in 3DC cascade configuration with UR/URz only, R site in 3DC
cascade delta configuration with UR only, or L or R site in 3DC multi-
target delta configuration with UR only
(2) A host I/O is issued.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

42 SSB output and performance degradation


Phenomena SSB=DD86, DE4E, DE4D, 13F3, 14DD, or 1315 was output and
performance might degrade (long response).
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Data CM capacity of the whole system is 128 GB or larger.
(2) A configuration where the value that data CM capacity is divided by
the number of mounted MPBs is large.
(3) I/Os are concentrated on a specific MPB.
(4) Immediately after the above, I/Os are concentrated on a different
MPB.
Affected Products/Version DKCMAIN: 70-02-54-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Open or Mainframe
Changed Part DKCMAIN

43 Failure of PS OFF with SIM=388F00


Phenomena When PS OFF was performed while cache was blocked, SIM=388F00
was output and PS OFF failed.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) A DP/DPz/DT/DTz pool.
(2) RAID1.
(3) Drive copy is performed.
(4) Cache is blocked.
Affected Products/Version DKCMAIN: 70-03-31-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic
Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

HDS Confidential 17 of 25
44 Invalid phy_PG data output by Performance Monitor or
Export tool
Phenomena All of the phy_PG data (PG Busy data) output by the Performance
Monitor or Export tool were 0.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when a storage system configured by DP/DPz is
used.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category HDD
Changed Part DKCMAIN

45 Host has access lost to LUN with SSB=B64A after CHA


replacement
Phenomena A host has access lost to LUN with SSB=B64A after CHA replacement.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) A host issues a ModeSelect command with QAM(*) specified to
CHA ports.
(2) CHA(s) included in the ports in (1) are replaced.

* QAM: It is specified in the ModeSelect command and guarantees IO


sequence at DKC side.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Open
Changed Part DKCMAIN

46 Invalid journal usage rate at I site


Phenomena In cascade configuration with UR/URz only, a journal usage rate
displayed for I site was invalid.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Open or Mainframe
(2) One of the following configurations
(a) 3DC multi-target delta configuration with UR only
(b) 3DC cascade delta configuration with UR only
(c) Cascade configuration with UR/URz only
(3) One of the following phenomena occurs.
(a) When a cache failure occurs at I site in cascade delta configuration or
P site in multi-target delta configuration, a delta mirror is being deleted.
(b) When a cache failure occurs at P site in cascade configuration, a
mirror between I site and R site is being deleted or suspended.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 18 of 25
47 LA error in pool VOL in background format processing
Phenomena An LA error occurred in a pool VOL in background format processing
and SSB=A443 and 3289 were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Background format is performed. (SOM896 is set to ON.)
(2) A pool whose pool VOLs are internal VOLs is used.
(3) RAID level of the pool VOLs is RAID5 or RAID6.
(4) One of the following occurs.
- I/O load is high.
- A drive failure occurs.
- A cache blockage occurs.
- WCHK1 or CHK1 occurs.
- SOM896 setting is changed.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe, Dynamic
Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

48 Invalid pair status after delta resync operation


Phenomena In 3DC multi-target delta configuration with TC-UR/TCz-URz, if a delta
resync operation was performed after performing PS OFF and then ON,
the pair status remained in HOLDING.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Open or Mainframe (Only Open if URxUR delta configuration)
(2) A JNLG* that can be used in URxUR multi-target configuration.
(3) One of the following configurations
(a) 3DC multi-target delta configuration with TC-UR/TCz-URz
(b) 3DC multi-target delta configuration with UR
(c) 3DC cascade delta configuration with UR
(4) A suspend operation is executed for a pair between P site and R site.
(For a pair between I site and R site in cascade delta configuration with
UR)
(5) PS OFF and then ON, or offline micro-program exchange is
performed at P site. (I site in URxUR cascade delta configuration)
(6) A delta resync is executed at L site. (At P site in URxUR cascade
delta configuration)

* A JNLG of JNLG# with (M) displayed on Journal Operation window of


Storage Navigator.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator or Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 19 of 25
49 Incorrect display of journal Meta data usage rate
Phenomena In 3DC cascade configuration with UR/URz only or 3DC multi-target
delta configuration with UR only, the displayed journal meta data usage
rate was lower than the actual usage rate.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) I site in 3DC cascade configuration with UR/URz only, R site in 3DC
cascade delta configuration with UR only, or L or R site in 3DC multi-
target delta configuration with UR only
(2) A host I/O is issued.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

50 MPB blockage after CM failure with SSBs output


Phenomena When a CM failure occurred, SSB=1688, 1355, and 1353 were output
and an MPB was blocked.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occurs in rare cases due to a cache failure.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Open or Mainframe
Changed Part DKCMAIN

51 Failure of CMD device allocation, delta resync, or copy/resync


Phenomena When a CHK3 failure (CM failure/SM failure) occurred, one of the
following phenomena occurred.
(1) Remote command device allocation to UR/URz mirror in time-out.
(2) A delta resync operation for a delta UR/URz (TC x UR/TCz x
URz/UR x UR) failed.
(3) Initial copy or resync operation between I site and R site in UR x
UR/URz x URz cascade configuration did not make progress.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Open or Mainframe
(2) CHK3 has occurred while a mirror with a remote command device
(excluding not USED one) allocated exists. But in the case of
phenomenon (3), if CHK3 has not occurred in DKC at P site, the problem
does not occur.
(3) The following operations are executed.
(a) (1): Remote command device allocation to UR/URz mirror
(b)(2): A delta resync operation
(c)(3) Initial copy or resync operation between I site and R site in UR x
UR/URz x URz cascade configuration
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 20 of 25
52 Failure suspend of UR/URz pair with SSBs output
Phenomena When a pair was created by using the secondary VOL of UR/URz as the
primary(source) VOL of SI/SIz or Snapshot, SSB=ECF1 and EF15 and
the UR/URz pair was suspended due to failure.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) UR/URz pair
(2) An SI/SIz or Snapshot pair is created by using the secondary VOL of
UR/URz as the primary(source) VOL of SI/SIz or Snapshot.
Affected Products/Version DKCMAIN: 70-02-54-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

53 Failure during initial copy between I and R sites of UR/URz


Phenomena During initial copy processing between I site and R site in cascade
configuration with UR/URz only, SSB=37A0 was output and the pair was
suspended due to failure.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Cascade configuration with UR/URz only
(2) An initial copy is performed between I site and R site while JNLG
status of a mirror between P site and I site is Active.
(3) A response of read JNL path between I site and R site is delayed due
to line malfunction, overload and so on.
Affected Products/Version DKCMAIN: 70-03-33-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

54 Write PIN occurrence in HDD


Phenomena When a DKA port was removed during I/O processing while SOM15 or
SOM862 was set to ON, write PIN occurred in an HDD under the DKA
port and the following messages were output.

SIM=EF4X-YY
SIM=CF12-XX
SSB=A4C3
SSB=A4CC
SSB=A4C2
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) SOM15 or SOM862 is set to ON.
(2) A write I/O is issued.
(3) A port failure occurs between DKA and SSW.
Affected Products/Version DKCMAIN: 70-02-03-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category HDD
Changed Part DKCMAIN

HDS Confidential 21 of 25
55 Failure suspend of EXCTG with SSB=ED62 output
Phenomena When a remote command device which was previously used by an
EXCTG was deleted, the EXCTG was suspended due to failure and
SSB=ED62 was output in some cases.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Mainframe
(2) URz MxN configuration (Micro-program version of supervisor DKC
is 70-01-62-00/00 or higher)
(3) LDEV ownership of remote command devices used by an EXCTG
belongs to the same MPB.
(4) All JNLs registered in a subordinate DKC are deleted from the
EXCTG by performing either (a) or (b))
(a) Deleting JNLs from the EXCTG
(b) Deleting all pairs in target JNLs (JNLs are automatically deleted from
the EXCTG while initialized)
(5) On the supervisor DKC, mapping of remote command devices used
for EXCTG registration of the subordinate DKC in (4) is released.
(External VOLs are deleted.)
Affected Products/Version DKCMAIN: 70-01-62-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator for Mainframe
Changed Part DKCMAIN

56 Failure of pair status change when external VOL is blocked


Phenomena When an external VOL that was an SI/SIz copy target was blocked during
SI/SIz Split copy processing while SOM459 was set to ON, the pair status
did not change correctly as follows.

SI: The pair status did not change to PSUE but SSB=2151 was output and
then the status changed to PSUS, or the status did not change but
remained copying in some cases.
SIz: The pair status did not change to Suspend but SSB=2151 was output
and then the status changed to Split, or the status did not change but
remained copying in some cases.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) SOM459 is set to ON.
(2) SI/SIz Split copy is performed using an external VOL as an SI/SIz
copy target.
(3) The external VOL is blocked when the SI pair status is COPY(SP) or
PSUS(SP), or the SIz pair status is SP-PEND or V-Split.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Shadow Image, Shadow Image for Mainframe
Changed Part DKCMAIN

HDS Confidential 22 of 25
57 Failure of micro-program downgrade
Phenomena Micro-program downgrade after deleting an Incremental Flash Copy pair
was disabled and SVP message SMT4002W was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Multiple relationships using Incremental Flash Copy are established.
(2) Only the Incremental Flash Copy pair is deleted.
(3) Micro-program is downgraded.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Flash Copy version2, Flash Copy SE
Changed Part DKCMAIN

58 UR/URz S-VOL becomes Suspend status after pair deletion


Phenomena Phenomenon1
In 3DC multi-target configuration with 3 UR/URz sites where a pair for
delta resync was registered, when a UR/URz pair between PDKC and
RDKC was deleted immediately after deleting a UR/URz pair between
PDKC and LDKC, UR/URz S-VOL on RDKC became Suspend status.
(SSB=EA78)
Phenomenon2
In 3DC cascade configuration with 3 UR/URz sites where a pair for delta
resync was registered, when a UR/URz pair between IDKC and RDKC
was deleted immediately after deleting a UR/URz pair between PDKC
and IDKC, UR/URz S-VOL on RDKC became Suspend status.
(SSB=EA78)
Phenomenon3
In TC-UR/TCz-URz 3DC multi-target configuration where a pair for
delta resync was registered, when a UR/URz pair between PDKC and
RDKC was deleted immediately after deleting a TC/TCz pair between
PDKC and LDKC, UR/URz S-VOL on RDKC became Suspend status.
(SSB=EA78)
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Open or Mainframe
(2) The following operation is performed in each configuration below.
(a) 3DC multi-target configuration with 3 UR/URz sites where a pair for
delta resync is registered (Phenomenon1): A UR/URz pair is deleted with
mirror specified at PDKC and then another UR/URz pair is deleted with
mirror specified.
(b) 3DC cascade configuration with 3 UR/URz sites where a pair for
delta resync is registered (Phenomenon2): A UR/URz pair is deleted with
mirror specified at PDKC and then a UR/URz pair is deleted with mirror
specified at IDKC.
(c) TC-UR/TCz-URz 3DC multi-target configuration where a pair for
delta resync is registered (Phenomenon3): A TC pair is deleted and then a
UR/URz pair is deleted with mirror specified.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 23 of 25
59 No reflection of port attribute change on Storage Navigator
Phenomena After a port attribute was changed, the changed attribute was not reflected
on Storage Navigator.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) An SVP hard-disk error occurs and opening an SVP configuration
information management file fails.
(2) After (1), a port attribute is changed.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-04-51/00
Category Open or Mainframe
Changed Part SVP

60 EQC report before completion of staging


Phenomena In staging processing of unallocated pages of DPz, EQC was reported
before the staging was completed.
(Basic sense byte=0x1000, F/M=8F)
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Dynamic Provisioning for Mainframe
(2) A read track command (command code=0XDE) is issued to an area
without page allocation.
(3) I/O load is high.
Affected Products/Version DKCMAIN: 70-02-53-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning for Mainframe
Changed Part DKCMAIN

61 Temporary pinned slots with SSBs output


Phenomena Due to a conflict of zero data page reclamation and correction copy, dirty
slots remained in an unallocated page and pinned slots might temporarily
occur.
SSB=9CB9, 9F01, 9F80, 9F85, 13AE and 9CF4
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Zero data page reclamation is performed.
(2) Correction Copy, Dynamic Sparing, or Copy Back is performed.
Affected Products/Version DKCMAIN: 70-02-03-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Dynamic Provisioning, Dynamic Tiering
Changed Part DKCMAIN

HDS Confidential 24 of 25
62 LDEV created with wrong capacity
Phenomena When multiple LDEVs were created by a single operation on Create
LDEVs window of Storage Navigator, an LDEV might be created with
the capacity that was specified for another LDEV.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) On Create LDEVs window, a wizard is activated, Basic or External is
selected for Provisioning Type, and multiple LDEVs are selected. (added
to the right table)
(2) Before the wizard is completed, LDEV ID is changed on Change
LDEV Setting window while meeting the following conditions.
(a) The number of LDEVs whose LDEV ID is changed at a time is 2 or
more.
(b) An LDEV ID that is specified as an initial LDEV ID before change is
entered.
(c) LDEVs to be changed are in the same parity group.
(d) Among LDEVs to be changed, there is an LDEV whose capacity is
different from others.
(3) Apply is clicked for LDEV creation.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-04-51/00
Category Open or Mainframe
Changed Part SVP

63 CHK2 with SSBs output at time-out in DRR transfer


Phenomena When time-out occurs in DRR transfer, CHK2 might occur and
SSB=B21B and A8A6 were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur in rare cases when all the following conditions
are met.
(1) An I/O is issued to an LDEV that is not in RAID1 configuration.
(2) DRR transfer turns to time-out.
(3) Overloaded environment.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-51-00/00
Category Open or Mainframe
Changed Part DKCMAIN

HDS Confidential 25 of 25