USP/NSC

MICROCODE VERSION 50-09-98-00/12

RELEASED 02/21/2012
Newly supported features and functions for Version 50-09-98-00/12
1. Mainframe & OPEN System
NONE

2. Mainframe System
NONE

3. Open System
NONE

The change of contents for Version 50-09-98-00/12

1 Shadow Image L3 configuration is invalidly configured, and L3
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
pair cannot be deleted
Phenomenon 1:
A pair using an S-VOL of SI pair as a P-VOL and a P-VOL of another SI
pair as S-VOL could be created and 3-level cascading configuration was
wrongly created. (The pair of the 3rd level is called L3 pair below)
Phenomenon 2:
Deletion of the L3 pair failed. In this case, SSB=2328 and Storage
Navigator message 7005-1007 might be output.
Medium
Phenomenon 1:
The problem occurs when all the following conditions are met.
(1) An S-VOL of an SI pair (MU#0, 1, or 2) is specified as a P-VOL.
(2) A P-VOL of another SI pair (MU#1 or 2) is specified as an S-VOL.
(3) Pair creation is performed. (MU#1 or 2)

Phenomenon 2:
The problem occurs when pair deletion is performed for the L3 pair.
Affected Products/Version DKCMAIN: All
SVP: All
Fixed Product/Version DKCMAIN: 50-09-98-00/12
SVP: 50-09-94/00
Category Shadow Image
Changed Part DKCMAIN, SVP

HDS Confidential 1 of 3
2 PDEV blockage due to misjudgment of threshold over
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
3 SSBs output at UR pair creation
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
4 Invalid UR pair status at pair deletion after failure of resync
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
Even though the counter of PDEV read error (recovered) did not exceed
the threshold, SIM=502XYY for media error was output, dynamic sparing
activated, and the PDEV was blocked.
Medium
The problem may occur when all the following conditions are met.
(1) 400 Gbyte or larger HDDs are used.
(2) 100 or more read errors (recovered) are detected in ORM.
SVP: All
SVP: 50-09-94/00
Open or Mainframe
SVP
When a UR pair was created using R500 on MCU and R700 on RCU,
SSB=A443, A44D and 3289 were output.
Low
The problem occurs when all the following conditions are met.
(1) UR MCU is R500.
(2) A UR pair creation or resync operation is performed.
(3) Pair volume size is either (a) or (b)
(a) OPEN-V: The size is equal to the size of slots whose number leaves a
remainder of 1 when divided by 8.
(b) Other than OPEN-V: The size is equal to the size of slots whose
number leaves a remainder of 1 when divided by 32.
(4) The last LDEV number of an ECC group.
DKCMAIN: 50-03-30-00/00 and higher
DKCMAIN: 50-09-98-00/12
Universal Replicator
DKCMAIN
operation
Immediately after a resync operation for UR/UR for z/OS failed due to a
failure suspend, when pair deletion was executed for all pairs, a pair in a
JNLG of UR to which the deletion was performed remained in Deleting
status.
Medium
The problem may occur when all the following conditions are met.
(1) Universal Replicator and Universal Replicator for z/OS
(2) A resync operation is executed for UR pairs.
(3) During the resync operation, a failure (JNL VOL blockage) occurs
before P-VOL changes to COPY status.
(4) Because of the above failure, JNLG status becomes Stopping.
(5) Pair deletion from BCM, or LU specified pair deletion for all pairs in a
JNLG from SVP or CCI is performed.
DKCMAIN: 50-03-30-00/00 and higher
DKCMAIN: 50-09-98-00/12
Universal Replicator, Universal Replicator for z/OS
DKCMAIN
2 of 3
5 Unperformed maintenance for some LDEVs
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
6 DRR failure due to CHK2 threshold over
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Causes and Updates
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
When Format, Restore or Block was performed with multiple LDEVs
specified on Logical Device window of Maintenance, the maintenance
might not be performed for some LDEVs and SVP message 3031W was
output.
Low
The problem occurs when all the following conditions are met.
(1) Select several LDEVs and perform a Format, Restore or Block via the
SVP - Maintenance - Logical Device window.
(2) Among the selected LDEVs in (1), there are 2 or more LDEVs in a
same LUSE#A (including the top LDEV of the LUSE#A).
(3) There is another LUSE#B whose top LDEV is not selected in (1) and
the LUSE#B has one or more LDEVs selected in (1) (not the top LDEV).
(4) The LDEV# of LUSE#B selected within the range of (1) is larger than
the LDEV# of LUSE#A.
SVP: All
SVP: 50-09-94/00
Open or Mainframe
SVP
When a logical inconsistency reset was performed, CHK2 (SSB=D286)
occurred in a CHA because slot resources were still remaining
(SSB=D02F). After that, a DRR failure (SIM-RC：cf82) occurred in a
DKA by threshold over of CHK2 (SSB=A8AA). Pinned slots occurred,
too.
Medium
The problem may occur when all the following conditions are met.
(1) A read or write command is executed.
(2) A logical contradiction reset occurs. (SSB=1612)
The micro-program has been modified to fix the problem.
DKCMAIN: 50-03-93-00/00 and higher
DKCMAIN: 50-09-98-00/12
Open
DKCMAIN
3 of 3