Sie sind auf Seite 1von 6

USPV & USPVM

MICROCODE VERSION 60-07-61-00/00


RELEASED 04/27/2011
Newly supported features and functions for Version 60-07-61-00/00
1. Mainframe & OPEN System
NONE

2. Mainframe System
NONE

3. OPEN System
NONE

The change of contents for Version 60-07-61-00/00


1 Repeated SSB output and CHK1B/WCHK1
Phenomena Due to a hardware failure of microprocessor mounted on CHA PCB or
DKA PCB;
(1) SSB=131F output and CHK1B reset occurred repeatedly, or
(2) SSB=13F2/34E2 were repeatedly output and WCHK1 occurs in
multiple MPs.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when a hardware failure of microprocessor mounted
on CHA PCB or DKA PCB occurs.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category Open or Mainframe
Changed Part DKCMAIN

2 Failed to detect a failure of WCHK1 signal line


Phenomena A failure occurred at WCHK1 signal line in the CHA PCB, and all of 8
MPs in the PCB were blocked (EC=3207 or 1644). At almost the same
time, the data value in the SM control area was corrupted. Although the
CHA was replaced with a spare part, the corrupted value was read by the
processing of initial setting. As a result, WCHK1 (EC=1637) occurred
and maintenance operations could not be performed.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) A hardware failure occurs at WCHK1 signal line in the CHA or DKA
PCB.
(2) When performance of WCHK1 signal is not stable, a Read/Write I/O
is issued to the SM from the MP.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category Open or Mainframe
Changed Part DKCMAIN

HDS Confidential 1 of 6
3 Failure of data display or output
Phenomena After the time of clock on SVP was changed during Performance Monitor
data collection, when Performance Monitor data was displayed or output
using Export tool, a Storage Navigator error (5105, 55500) occurred and
the processing failed.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) The monitor switch is ON and sampling term is 2 minutes or longer.
(2) Immediately after the monitor switch is ON, SVP time is changed.
(3) The data sent immediately after the monitor switch is ON delays due
to overload of communication.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-07-56/00
Category Performance Manager
Changed Part SVP

4 Unable to define quorum disk to previously used LDEV#


Phenomena In a configuration where HAM was used, when Restore Configuration
was executed for storage recovery and then a quorum disk was defined
again, the disk could not be defined to the LDEV# used before recovery.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) A quorum disk is defined by HAM function.
(2) Restore Configuration is executed.
Affected Products/Version SVP: 60-05-06/00 and higher
Fixed Product/Version SVP: 60-07-56/00
Category Open or Mainframe
Changed Part SVP

5 Wrongly reported SIM=BFBCXX


Phenomena If an environmental failure in DKU was left unsolved, SIM=BFBCXX
(P/K Data disagreement) might be wrongly reported at around 04:00 AM.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) A failure occurs in DKU (AC/PS/SVR/FAN)
(2) The failure is left unsolved until 04:00 AM the next day.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category DKU
Changed Part DKCMAIN

HDS Confidential 2 of 6
6 All data copy after resync operation for suspended JNLG
Phenomena During I/O processing to a UR pair, SSB=EDCD was output due to a
delay in JNL creation, causing a failure suspension. When a resync
operation was executed for the JNLG where the failure suspension
occurred, all data copy occurred.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) An I/O is issued to a UR pair.
(2) SSB=EDCD is output due to a delay in JNL creation, which results in
failure suspension.
(3) A Resync operation is executed for the JNLG where the failure
suspension occurs.
Affected Products/Version DKCMAIN: 60-05-06-00/00 and higher
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category Universal Replicator for Open or z/OS
Changed Part DKCMAIN

7 WCHK1 occurrence
Phenomena When the following operations were executed in the configuration where
"16KLDEV/TC/UR/SI/VM/FC/HAM" of Install Function was not
installed, WCHK1 occurred.
(1) On Pair Operation window of TC/TC for z/OS of SVP Web Console
or Storage Navigator, pair deletion with Force specified was executed for
Simplex VOL.
(2) On Pair Operation window of TC for z/OS of SVP Web Console, a
Mainframe command device was removed.
(3) After pair deletion was executed for volumes previously used by a
Sync CTG pair (P-VOL or S-VOL) and then TC/UR was removed, a TC
pair was created using the volume as S-VOL.
(4) Asynchronous Operation window of SVP Web Console or Storage
Navigator was opened.
(5) Async CTG was registered using the 83/xA7 command.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) "16KLDEV/TC/UR/SI/VM/FC/HAM" of Install Function is not
installed.
(2) Any of the following operations is executed.
(a) Pair deletion with Force specified for Simplex VOL from SVP Web
Console or Storage Navigator. (Open/Mainframe)
(b) A Mainframe command device removal from SVP Web Console
(Mainframe)
(c) Following deletion of a volume previously used by a Sync CTG pair
(P-VOL or S-VOL) and then TC/UR removal, a TC pair is created using
the volume previously used by the Sync CTG pair as S-VOL.
(d) Async CTG registration using the 83/xA7 command.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category True Copy, True Copy for z/OS, True Copy Asynchronous, True Copy
Asynchronous for z/OS
Changed Part DKCMAIN

HDS Confidential 3 of 6
8 CHK3 occurrence with SSB=0x32FE output
Phenomena In the minimum SM installation configuration (1K LDEVs
configuration), when a command device was set from BCM, CHK3
occurred and SSB=0x32FE was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Minimum SM installation configuration (1K LDEVs).
(2) A command device is set or released from BCM.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category Business Continuity Manager
Changed Part DKCMAIN

9 MP blockade following WCHK1 with SSB/SIM output


Phenomena When any of the following operations was executed, WCHK1 occurred,
an MP was blocked in rare cases and SSB=32FE and SIM=3073-XY
were output.
(1) Disconnect Volumes or Disconnect Storage Systems.
(2) Power OFF.
Severity (High, Medium, Low) Medium
Conditions of Occurrence May occur in rare cases when the following condition (1) or (2) is met.
(1) The following operations are executed.
(a) UVM device mapping.
(b) Disconnect Volume or Disconnect Subsystem is executed for the
mapped device.
(2) The power is turned OFF.
Affected Products/Version DKCMAIN: 60-01-68-00/00 and higher
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category Universal Volume Manager (Open)
Changed Part DKCMAIN

10 Unable to display Battery Life SIM Warning window


Phenomena When trying to set Battery Life warning SIM, the Battery Life SIM
setting window could not be displayed.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when Remained Battery life value exceeding the year
of 2038 as SIM reporting date is set during Battery Life Sim setting.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-07-56/00
Category SVP
Changed Part SVP

HDS Confidential 4 of 6
11 Failure of Disconnect Volume or Disconnect Subsystem
Phenomena When Disconnect Volume or Disconnect Subsystem was executed, a
message stating that the processing was completed normally appeared,
but if Delete Volume was executed after that, a Storage Navigator error
(605-56515) might occur and SSB=AD4C was output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when Disconnect Volume or Disconnect
Subsystem is executed for a mapping device.
Affected Products/Version DKCMAIN: 60-01-68-00/00 and higher
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category Open
Changed Part DKCMAIN

12 PIN error and LDEV blockade


Phenomena During a TC pair resync operation, LDEV blockade and PIN errors
occurred in a raid-group consisting of SSDs (Solid State Disk).
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) P-VOL of True Copy for Open or z/OS.
(2) Temp drive failure and unreadable data even by correction read.
(3) Initial copy or resync is executed.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category True Copy, True Copy for z/OS
Changed Part DKCMAIN

13 Frequent SSB=AF51 output


Phenomena During sequential write processing, SSB=AF51 was frequently output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence May occur with one of the following condition (1), (2), or (3) met.
Condition (1)
(a) DP-VOLs for which Volume Migration or Shadow Image (Quick
Restore) is executed, and
(b) The DP-VOLs are over 700GB.

Condition (2)
(a) System Option Mode 460 and System Option Mode 727 set to OFF,
(b) SM volatile power ON is performed, and
(c) There is a DP-VOL of over 1TB.

Condition (3)
(a) Forcible power OFF and SM volatile power ON, or SI initialization
(b) Pool recovery is performed, and
(c) There is a DP-VOL of over 1TB.
Causes and Updates The micro-program has been modified to prevent the SM table from
being corrupted (SSB=AF51 is output if the SM table is corrupted).
Affected Products/Version DKCMAIN: 60-02-04-00/00 and higher
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category Dynamic Provisioning
Changed Part DKCMAIN

HDS Confidential 5 of 6
14 Frequent SSB=AF51 output (additional recovery fix)
Phenomena During sequential write processing, SSB=AF51 was frequently output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when one of the following condition (1), (2), or
(3) is met.
Condition (1)
(a) DP-VOLs for which Volume Migration or Shadow Image (Quick
Restore) is executed, and
(b) The DP-VOLs are over 700GB.

Condition (2)
(a) System Option Mode 460 and System Option Mode 727 are set to
OFF,
(b) SM volatile power ON is performed, and
(c) There is a DP-VOL of over 1TB.

Condition (3)
(a) Forcible power OFF and SM volatile power ON, or SI initialization is
performed,
(b) Pool recovery is performed, and
(c) There is a DP-VOL of over 1TB.
Causes and Updates The micro-program has been modified to detect and then recover the SM
table error.
This is an additional fix to RAID600-1784.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-07-61-00/00
Category Dynamic Provisioning
Changed Part DKCMAIN

15 DKU micro-program update


Phenomena Even after applying DKU Micro-code 00-4E-5B for DKS2F-K HDD,
HDD failure rate was not improved in several sites.
DKS2E-K/DKS2G-K Seagate drive models have the same risk.
Severity (High, Medium, Low) Medium
Conditions of Occurrence This phenomenon occurred on DKS2E-K with DKU micro-program Rev.
00-4E-61.
This phenomenon occurred on DKS2F-K with DKU micro-program Rev.
00-4E-5B.
This phenomenon occurred on DKS2G-K with DKU micro-program Rev.
00-5E-5A.
Causes and Updates The DKU micro-program is modified to improve the function of head self
diagnostics.
Affected Products/Version DKS2E-K: 00-4E-61
DKS2F-K: 00-4E-5B
DKS2G-K: 00-5E-5A
Fixed Product/Version DKS2E-K: 00-4E-62
DKS2F-K: 00-4E-5D
DKS2G-K: 00-5E-5B
Category HDD
Changed Part DKU

HDS Confidential 6 of 6

Das könnte Ihnen auch gefallen