VSP MICROCODE VERSION 70-04-54-00/00-M128 RELEASED 09/25/2012 New Supported Features and Functions For Version 70-04-54-00/00-M128

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 13

VSP

MICROCODE VERSION 70-04-54-00/00-M128


RELEASED 09/25/2012
New supported features and functions for Version 70-04-54-00/00-M128
1. Mainframe & OPEN System- NONE
2. Mainframe System- NONE
3. OPEN System- NONE

The change of contents for Version 70-04-54-00/00-M128


1 Data inconsistency on S-Vol of CoW in cascade configuration
Phenomena In a cascade configuration of Shadow Image (hereinafter referred to as
“SI”) and Copy-on-Write Snapshot (hereinafter referred to as “CoW”),
when data is read from CoW S-Vol, data updated after pair split is read
instead of data at the time of the pair split operation. As a result, a file
system problem occurs, or applications detect errors.
Severity (High, Medium, Low) High
Conditions of Occurrence When Conditions of occurrence 1 or Conditions of occurrence 2 are met,
the phenomenon may occur.
Conditions of occurrence 1
The phenomenon occurs when all the following conditions are met.
A. RAID700 70-03-01-00/00 and later
B. Cascade configuration of SI and CoW (SI S-VOL and CoW P-VOL
are shared)
C. System Option Mode791 is set to ON
D. SI pair status is PSUS or PSUS (SP)
E. CoW pair status is PSUS
F. SI pairresync operation (Normal Resync) is performed
Note) It does not occur with QuickResync

Conditions of occurrence 2
The phenomenon occurs when all the following conditions are met.
A. All the current versions of RAID700
B. Cascade configuration of SI and CoW (SI S-VOL and CoW P-VOL
are shared)
C. SI pair status is PSUE
D. CoW pair status is PSUS
E. SI pairresync operation (Normal Resync) is performed
Note) It does not occur with QuickResync
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Shadow Image, Copy-on-Write Snapshot
Changed Part DKCMAIN

HDS Confidential 1 of 13
2 Data inconsistency with Flash Drive configured as RAID1
Phenomena Phenomenon1:
At Flash Drive (Drive Type: SDT5X, SDT2X, SLR5X) configured as
RAID1, during Dynamic Sparing or Drive Copy (*1) or Copy Back is
performed, data inconsistency may occur because host data isn't written to
exact LBA.

Phenomenon2:
At Flash Drive (drive type: SDT5X, SDT2X, SLR5X) configured as
RAID1, during Dynamic Sparing or Drive Copy or Copy Back is
performed, SSB EC=A443 (CHK2 failure) may be reported.

*1: Copying the data to the spare disk.


Severity (High, Medium, Low) High
Conditions of Occurrence Phenomenon1:
The problem may occur when the condition F is performed under the
conditions A, B, C and D are met or under the conditions A, B, C and E
are met.

A. RAID700 All current versions


B. Flash Drive (Drive Type: SDT5X, SDT2X, SLR5X) are installed.
C. RAID Group composed of the condition B is configured as RAID1.
D. DP (Dynamic Provisioning) or DT (Dynamic Tiering) Pool is installed
at RAID Group composed of the condition B.
E. Base emulation type of RAID Group composed of the condition B is
3390-A.
F. Dynamic Sparing or Drive Copy or Copy Back is performed at RAID
Group composed of the condition B. (SIM RC=4610-xx)

Phenomenon2:
The problem may occur when the condition F is performed under the
conditions A, B, C, D and E are met.

A. RAID700 All current versions


B. Flash Drive (Drive Type: SDT5X, SDT2X, SLR5X) are installed.
C. RAID Group composed of the condition B is configured as RAID1.
D. DP (Dynamic Provisioning) or DT (Dynamic Tiering) Pool is not
installed at RAID Group composed of the condition B.
E. Base emulation type of RAID Group composed of the condition B is
not 3390-A
F. Dynamic Sparing or Drive Copy or Copy Back is performed at RAID
Group composed of the condition B. (SIM RC=4610-xx).
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-54-00/00
Category Hitachi Dynamic Provisioning, Hitachi Dynamic Tiering, Dynamic
Provisioning for Mainframe, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

HDS Confidential 2 of 13
3 WCHK1 with SIM=3080XY
Phenomena When a failure inside an ESW PSB was detected, SSB=3250 was
continuously output, leading to WCHK1 (SIM=3080XY).
Severity (High, Medium, Low) High
Conditions of Occurrence The problem may occur when a failure inside an ESW PCB is detected
and SSB=3250 is continuously output.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Open or Mainframe
Changed Part DKCMAIN

4 Update of SSD micro-program


Phenomena When an SSD receives an LU reset during IO, a command time-out
occurs in IO after the reset processing of SSD.
LED may not light up after IO in rare cases.
Severity (High, Medium, Low) Low
Conditions of Occurrence The phenomenon occurs on SDT5A-S/SDT2A-S with SSD micro-
program before Rev.00-00-4L.
Affected Products/Version SDT5A-S/SDT2A-S: 00-00-4L and lower
Fixed Product/Version SDT5A-S/SDT2A-S: 00-00-4M
Category HDD
Changed Part HDD

5 Failure of WWN performance data collection and SVP reboot


Phenomena When there were 256 or more channels registered as monitoring targets
between ports and WWNs, if Export Tool with "PPCGWWN" specified
was executed or the WWN tab on SPM window of Storage Navigator was
displayed, Storage Navigator message 4-6001 was output, WWN
performance data was not obtained and SVP was rebooted.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when the following conditions (1) and (2), or (3) and
(4) are met.
(1) There are 256 or more channels registered as monitoring targets
between ports and WWNs in DKC.
(2) Export Tool is executed with group PPCGWWN specified in a
parameter (command.txt).
(3) There are 256 or more channels registered as monitoring targets
between ports and WWNs for an SPM group.
(4) The WWN tab on SPM window is opened and information of the
above SPM group is displayed.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-04-52/00
Category Performance Monitor
Changed Part SVP

HDS Confidential 3 of 13
6 Failure of PDEV replacement during heavy I/O load
Phenomena When PDEV replacement was performed with heavy I/O load, HDD
micro-program exchange ended abnormally as expected, but the PDEV
replacement failed with SVP message ONL2412E output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) A PDEV of SLR5B-MxxxSS is replaced or installed.
(2) Write pending rate is 50% or higher.
Affected Products/Version DKCMAIN: 70-03-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Open or Mainframe
Changed Part DKCMAIN

7 Invalid normal end of FCWITHDRAW


Phenomena When a Flash Copy relationship was established with FULLVOL and
CHRCD and without INCREMENTAL specified, and then
FCWITHDRAW with EXTENT specified was executed to the
relationship, the command was not rejected but ended normally.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) A Flash Copy relationship is established with FULLVOL and
CHRCD and without INCREMENTAL specified.
(2) FCWITHDRAW with EXTENT specified is executed to the
relationship.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Flash Copy V2, Flash Copy SE
Changed Part DKCMAIN

8 CHA or DKA blockage due to correctable error


Phenomena SSB=3480 and 34E4 were output and CHA or DKA was blocked.
If CHA was blocked, SIM=2120XX was output.
If DKA was blocked, SIM=CF10XX was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when a correctable error (single error correction)
occurs due to a hardware failure while reading memory stored in LRP in
CHA or DKA.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Open or Mainframe
Changed Part DKCMAIN

HDS Confidential 4 of 13
9 Update of HDD micro-program 1
Phenomena Unexpected command timeout was reported after DKC power outage
with continuous DKU power supply.
Severity (High, Medium, Low) Medium
Conditions of Occurrence This phenomenon occurs on following products and versions
DKS5B-J with HDD micro-program Rev. 00-4F-0C.
DKS5B-K with HDD micro-program Rev. 00-4F-5C.
DKS5C-J with HDD micro-program Rev. 00-5F-09.
DKS5A-H with HDD micro-program Rev. 00-5F-03.
DKS5B-H with HDD micro-program Rev. 00-5F-08.
DKS5D-J with HDD micro-program Rev. 00-5F-09.
DKS2C-H with HDD micro-program Rev. 00-4F-03.
Affected Products/Version Same as Conditions of Occurrence
Fixed Product/Version DKS5B-J: 00-4F-0D
DKS5B-K: 00-4F-5D
DKS5C-J: 00-5F-0A
DKS5A-H: 00-5F-07
DKS5B-H: 00-5F-0A
DKS5D-J: 00-5F-0B
DKS2C-H: 00-4F-06
Category HDD
Changed Part HDD

10 Update of HDD micro-program 2


Phenomena In RAID600, Sense Key/Sense Code = 04/44F6, 04/1501 occurred
frequently and a replacement rate of DKS2E-K300FC degraded after
upgrading the HDD micro-program to Rev. 00-4E-5B. Therefore HDD
micro-program of DKS2E-K is modified to fix the problem and the
function of head self diagnostics is imporved.

In RAID700, feedback of the above quality improvement is applied to


HDD micro-programs of DKS5A-H, DKS5B-H, DKS5D-J, and DKS2C-
H.
Severity (High, Medium, Low) Low
Conditions of Occurrence This phenomenon occurred on the following products/versions
DKS5A-H with HDD micro-program Rev. 00-5F-03.
DKS5B-H with HDD micro-program Rev. 00-5F-08.
DKS5D-J with HDD micro-program Rev. 00-5F-09.
DKS2C-H with HDD micro-program Rev. 00-4F-03.
Affected Products/Version Same as Conditions of Occurrence
Fixed Product/Version DKS5A-H: 00-5F-07
DKS5B-H: 00-5F-0A
DKS5D-J: 00-5F-0B
DKS2C-H: 00-4F-06
Category HDD
Changed Part HDD

HDS Confidential 5 of 13
11 Update of HDD micro-program 3
Phenomena LDEV format may take too long time due to an HDD internal error.
Severity (High, Medium, Low) Low
Conditions of Occurrence This phenomenon occurs on DKS2D-H with HDD micro-program Rev.
00-4F-07.
Affected Products/Version DKS2D-H: 00-4F-07
Fixed Product/Version DKS2D-H: 00-4F-09
Category HDD
Changed Part HDD

12 Invalid pair status when Group Resync is performed


Phenomena Phenomenon1
While Group Resync was being performed from BCM for a Mainframe
Sync CTG or general CTG, when Group Resync was performed for a
different CTG, pair status remained in Suspend.

Phenomenon2
While Group Resync was being performed from CCI for a CTG across
multiple DKCs, when Group Resync was performed for a different CTG,
pair status remained in Suspend.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Phenomenon1
The problem may occur when all the following conditions are met.
(1) TC for Mainframe, UR for Mainframe
(2) Mainframe Sync CTGs or general CTGs.
(3) Pair creation or Resync is performed to 1025 or more TCz pairs or
URz pairs in a storage system.
(4) In processing of (3), Group Resync (including Swap Resync) is
performed from BCM for a CTG.
(5) Group Resync (including Swap Resync) is performed from BCM for a
CTG different from the above CTG in (4).

Phenomenon2
The problem may occur when all the following conditions are met.
(1) TC or TC for Mainframe, UR or UR for Mainframe
(2) CTGs across multiple DKCs.
(3) Pair creation or Resync is performed to 1025 or more TC/TCz pairs or
UR/URz pairs in a storage system.
(4) In processing of (3), Group Resync is performed from CCI for a CTG.
(5) Group Resync is performed from CCI for a CTG different from the
above CTG in (4).
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category True Copy, True Copy for Mainframe, Universal Replicator , Universal
Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 6 of 13
13 CHK2 detection when time-out occurs in DRR transfer
Phenomena When time-out occurred in DRR transfer, CHK2 might be detected and
SSB=B21B and A8A6 were output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when an I/O is issued to an LDEV that is not in
RAID1 in rare cases.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Open or Mainframe
Changed Part DKCMAIN

14 WCHK1 when I/O is issued to LDEV in quick format


Phenomena When a read I/O was issued to an LDEV in quick format processing,
WCHK1 occurred and SSB=32FE was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) An LDEV in quick format or an LDEV of DP/DPz or DT/DTz VOL
(2) There is an unformatted area.
(3) Read and write I/Os are issued.
(4) I/O overload.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Open or Mainframe
Changed Part DKCMAIN

15 Storage Navigator operation unavailable


Phenomena If a wizard and a dialog of Storage Navigator were maximized, any
operation was disabled on the windows.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) A Storage Navigator wizard or dialog that contains a table is
displayed.
(2) There is an empty column displayed on rightmost side of the table.
(3) A vertical scroll bar is displayed and a user scrolls the window
downward.
(4) The button to maximize the wizard or dialog is clicked.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-04-52/00
Category Storage Navigator
Changed Part SVP

HDS Confidential 7 of 13
16 SSB output at read I/O or ABEND of read I/O
Phenomena Phenomenon1
When a read I/O was issued to a CoW Snapshot S-VOL, SSB=1548,
1588, D20C, and 13FB were output.
Phenomenon2
A read I/O to a CoW Snapshot S-VOL ended abnormally.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Phenomenon1
The problem may occur when all the following conditions are met.
(1) LDEV size of a CoW Snapshot pair is 3,145,716 MB or larger.
(2) The Snapshot P-VOL is a DP-VOL.
(3) Sequential read I/Os are issued to S-VOL of the CoW Snapshot pair in
PSUS status.
(4) The read area does not obtain Snapshot.
Phenomenon2
(1) LDEV size of a CoW Snapshot pair is 3,145,716 MB or larger.
(2) The Snapshot P-VOL is a DP-VOL.
(3) A read I/O is issued to an area containing 3,145,716 MB boundary in
S-VOL of the Snapshot pair in PSUS status.
(4) The read area does not obtain Snapshot.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Copy-on-Write Snapshot
Changed Part DKCMAIN

17 WCHI1 during MPB replacement


Phenomena WCHK1 occurs with SSB=1637 in the following sequence:
- Microcode Exchange fails with SVP message 3759W due to high MP
usage (over 50%).
- Afterwards, the operator replaces the MPB and WCHK1 occurs
(SSB=1637).
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Online micro-program exchange from a version earlier than 70-03-32-
00/00 to version 70-03-32-00/00 or higher.
(2) Code exchange aborted due to high load (MP usage exceeding 50%).
<SVP operation>
SVP message [SMT3759W] is displayed and [Cancel] is clicked.
<FC Wizard (V03+1 and earlier versions)>
Micro-program exchange fails with Error Message "SVP internal error".
Note that the above message implies several meanings including the
high MP usage.
<FC Wizard (V04 and higher versions)>
Micro-program exchange fails with Error Message "MP Reboot stop,
Due to heavy I/O load".
(3) MPB replacement or MPB installation is performed in the situation of
(2).
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Open or Mainframe
Changed Part DKCMAIN

HDS Confidential 8 of 13
18 Unable to change the parameters of HDT Pool
Phenomena When a pool was expanded while a pool parameter was changed, “0” that
was an unacceptable value might be set to the buffer space for tier
relocation. In this case, the parameter change failed with Storage
Navigator message 3005-007060 and SSB=E761 output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Problem may occur when a pool parameter change and pool expansion
that causes an increase in number of tiers are performed at the same time.

In particular, the pool parameter change refers to the case when one of the
following items is changed on Edit Pools window.
- Multi-Tier Pool (Enable/Disable)
- Tier Management (Auto/Manual)
- Cycle Time
- Monitoring Period
- Buffer Space for New page assignment
- Buffer Space for Tier relocation
- External LDEV Tier Rank (supported from V04 and higher versions)
- Monitoring Mode
Affected Products/Version DKCMAIN: 70-02-03-00/00 and higher (DT), 70-03-01-00/00 and higher
(DTz)
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Dynamic Tiering, Dynamic Tiering for Mainframe
Changed Part DKCMAIN

19 Failure of pair creation, pair resync, and I/O operation


Phenomena (1) UR/URz pair creation or UR/URz pair resync failed and SSB=8F04
and 370C, and BCM message 8F04 and 370C were output.
(2) In TC-UR delta configuration, the following occurred.
(a) After delta pair creation, when an I/O was issued to a S-VOL, the
delta pair became HLDE status and SSB=EDD8 and CDE6 were output.
(b) After delta pair creation, when S-VOL status was changed to SSWS
and then an I/O was issued to the S-VOL, the I/O stopped and
SSB=EDD8 was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) One of the following journal group is used.
(a) A journal group that is registered with micro-program version earlier
than 70-03-32-00/00.
(b) A journal group that is registered with micro-program version 70-03-
32-00/00 and higher while UR 3DC is disabled.
(2) One of the following operations is performed.
(a) UR/URz pair creation or pair resync operation is performed.
(b) After TC-UR delta pair is created, an I/O is issued to P-VOL in TC-
UR delta configuration.
(c) After TC-UR delta pair is created, S-VOL status is changed to SSWS
and then an I/O is issued to the S-VOL in TC-UR delta configuration.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

HDS Confidential 9 of 13
20 No SSW/Expander micro-program exchange
Phenomena When DKU was installed, SSW and Expander micro-programs were not
exchanged for the installation target SSW.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) DKU installation without DKA is performed.
(2) SSW/Expander micro-program versions stored on the HDD of SVP
are higher than those of the installation target SSW.
Affected Products/Version SVP: 70-04-01/00 and higher
Fixed Product/Version SVP: 70-04-52/00
Category Open or Mainframe
Changed Part SVP

21 Incorrect PG usage rate display


Phenomena When random read I/Os were issued to a DP or DT VOL while Flash
Acceleration was ON, parity group usage rate was not displayed
correctly.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Flash Acceleration is ON.
(2) DP or DT VOL.
(3) Performance Monitor is ON.
(4) Random read I/Os.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Dynamic Provisioning
Changed Part DKCMAIN

22 Continuous Check Condition


Phenomena When a read I/O was issued to CoW Snapshot S-VOL, SSB=D3B4 was
output and Check Condition was continuously reported.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) HMO63 is set to ON.
(2) CoW Snapshot P-VOL is a DP-VOL.
(3) The used capacity of a DP-VOL pool exceeds the warning threshold.
(4) A read I/O is issued to S-VOL of the CoW Snapshot pair in PSUS
status.
(5) For the read range, snapshot is not yet obtained.
Affected Products/Version DKCMAIN: 70-02-54-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Copy-on-Write Snapshot
Changed Part DKCMAIN

HDS Confidential 10 of 13
23 Start Pending during Mainframe host I/O processing
Phenomena After Start Pending might occur during Mainframe host I/O processing.
- SSB=1603
- HOST message: IOS071I (START PENDING)
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) A Mainframe host I/O is being processed.
(2) Reserve is received from the host.

Affected Products/Version DKCMAIN: All


Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Mainframe
Changed Part DKCMAIN

24 Mirror status causing failure of delta resync pair deletion


Phenomena The following occurred in TC-UR 3DC multi-target delta configuration.
(1) When a UR/URz pair was deleted, the mirror status of JNLG where
the delta resync pair belonged to remained in Stopping status and the
delta pair could not be deleted.
(2) When a delta resync pair was deleted from the S-VOL site, the mirror
status of JNLG where the delta resync pair belonged to remained in
Stopping status and the delta pair could not be deleted.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) TC-UR 3DC multi-target delta configuration
(2) Pair deletion is performed for a UR/URz pair or pair deletion is
performed while specifying a delta resync pair S-VOL.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Universal Replicator, Universal Replicator for Mainframe
Changed Part DKCMAIN

25 Failed to reach the Maximum Initial Copies


Phenomena When "Maximum Initial Copy Activities (CU)" option was enabled on
System Option window and then an initial copy or resync operation was
performed, the number of copy tasks did not reach the maximum.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) True Copy or True Copy for Mainframe
(2) Maximum Initial Copy Activities (CU) is enabled.
(3) 2 or more CUs are used.
(4) The number of pairs exceeding the number of Maximum Initial
Copies is used in at least one of the CUs.
(5) For the above pairs, all data copy pair creation or a resync operation
(including swap resync) is performed.
Affected Products/Version DKCMAIN: 70-03-32-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category True Copy, True Copy for Mainframe
Changed Part DKCMAIN

HDS Confidential 11 of 13
26 DRR blockage after frequent CHK2
Phenomena CHK2 (SSB=3288 and B2FF) frequently occurs and DRR blockage
occurs when the SI S-VOL is an External Volume - with more than 3TB
capacity - and SI paircreate is performed.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Shadow Image and Volume Migration.
(2) P-VOL is an internal DP-VOL of 3 TB or larger in capacity.
(3) S-VOL conditions:
- An external VOL or a DP-VOL associated with an external pool
only. (Created with the micro-program V02 or earlier).
- 3 TB or larger in capacity.
(4) OPEN-V.
Affected Products/Version DKCMAIN: 70-04-01-00/00 and higher
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Shadow Image, Volume Migration
Changed Part DKCMAIN

27 Insufficient SSB information for SSD failure analysis


Phenomena During SSD online diagnosis, if an error occurred 4 times in a day,
SIM=FFFB and SSB=35E1 were output, but the information of SSB was
not enough for SSD failure analysis.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when CMSSD periodical diagnosis while DKC is in
operation fails.
Affected Products/Version CMBK: All
Fixed Product/Version CMBK: 70-75-55
Category Open or Mainframe
Changed Part CMBK

28 Command timeout at CMSSD activation


Phenomena At CMSSD activation, SSD-specific information is obtained, but the
timeout time of response from the SSD was not long enough.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when the response time of a command to obtain
SSD-specific information is 1 msec or longer.
Affected Products/Version CMBK: All
Fixed Product/Version CMBK: 70-75-55
Category Open or Mainframe
Changed Part CMBK

HDS Confidential 12 of 13
29 Link-down with SSBs output during MPB replacement
Phenomena At MPB replacement, link-down occurred and SSB=B6F1, B67F, B60B,
and B6FB were output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when an MPB is replaced during I/O processing.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category Open or Mainframe
Changed Part DKCMAIN

30 Continuous display of HDVM message KAIC 15056-W


Phenomena When the following operations were performed, KAIC 15056-W (HDVM
message) was continuously displayed.
(1) An update I/O was issued to TC/TCz S-VOL with write-enable
specified.
(2) Quick Restore or Reverse Resync was performed for an SI/SIz pair
that used TC/TCz S-VOL.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) True Copy or True Copy for Mainframe
(2) HDVM GUI
(3) One of the following operations is performed.
(a) An update I/O to TC/TCz S-VOL with write-enable specified
(b) Quick Restore or Reverse Resync for SI/SIz pair that uses TC/TCz S-
VOL.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-04-54-00/00
Category True Copy, True Copy for Mainframe
Changed Part DKCMAIN

HDS Confidential 13 of 13

You might also like