Professional Documents
Culture Documents
Uspv 60-01-44-00-00
Uspv 60-01-44-00-00
1. DKS2E-K72FC: The below shows the equivalent types in supported RAID level,
emulation, and the number of settable LDEV and these types are compatible among each
other. DKS2D-K72FC, DKR2F-K72FC
2. DKS2E-K146FC: The below shows the equivalent types in supported RAID level,
emulation, and the number of settable LDEV and these types are compatible among each
other. DKS2D-K146FC, DKR2F-K146FC
3. DKS2E-K300FC: The below shows equivalent types in supported RAID level, emulation,
and the number of settable LDEV and these types are not compatible among each other
because the rotation speed differs among each other. DKR2F-J300FC, DKS2D-J300FC
Changed Part HDD
1-2 Support for the alternate path configuration using different clusters of DS4800
Description Alternate path configuration using different clusters on IBM DS4800 now supported.
Setting port parameter (host type) of DS4800 to “Linux” is required to enable the function.
Changed Part DKCMAIN
1-3 RAID500 Support for TC/ TC for z/OS/ UR/ UR for z/OS
Description The RAID600 has supported the following connections with the RAID500:
True Copy connection with the RAID500
True Copy for z/OS connection with the RAID500
Universal Replicator connection with the RAID500
Universal Replicator for z/OS with the RAID500
Function only available for RAID500 with DKCMAIN version 50-09-15-00/00 and higher.
Changed Part DKCMAIN
HDS Confidential 1 of 28
2. Mainframe System
2-1 UR for z/OS 3DC Multi Target Support
Description RAID600 supports the 3DC Multi Target connection of TC for z/OS and UR for z/OS.
RAID600 has also supported the 3DC Multi Target connection of TC for z/OS and UR for
z/OS with the RAID500.
Function only available for RAID500 with DKCMAIN version 50-09-15-00/00 and higher.
Changed Part DKCMAIN
3. OPEN System
3-1 RAID Manager 01-20-03/06
Description RAID Manager updated as follows:
- Supported the maximum values for RAID600
- Support LDKC per 64K LDEV
- Supported the option to display HDP information
- Added "-v aou" option for the raidvchkscan command
- Added "-v aou" option for the raidvchkdsp command
- Added "-v pida" option for the raidvchkscan command
- Added the identification for HDP to the inqraid command
- Supported "-pin" option for displaying PIN volumes to the inqraid command
- Changed behavior of the horc command
- Horctakeover command performs PVOL_takeover under condition
(MINAP=0) on Link-failure.
- Pairsplit command performs "-P" option using the purge for HORC_Async/UR.
- Supported command option for awaking delayed I/O for dismounting on Windows2003
- -x syncd, -x umountd, raidscan -find syncd
- Supported RAID Manager communication between 32bits and 64bits HORCM
- Supported "RM Shadow Copy provider(01-03-03/02)" using TC with HPtM
- Added two securities for raidcfg command, and avoided a problem that
"raidcfg -a set -o hgrp" bring on EX_CMDIOE
Changed Part RAID Manager
HDS Confidential 2 of 28
2 Inappropriate error message for EXG allocation failure
Phenomena 1. At the execution of ADD VOLUME with the maximum number of V-
VOL used, EXG# was allocated from the window for EXG# allocation,
however, the CU: LDEV setting window showed "0-0" for the allocated
EXG.
2. After #1, allocated CU: LDEV# (ADD VOLUME mapping), and then
returned to the previous window that showed "-" for the EXG#. In that
case, clicking the OK button displayed the message saying no parameter
was set.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem #1 occurs when all of the following operations are
performed with the Volume Operation window showing that the number
of external volumes has reached the limit:
1. Add volumes manually.
2. Enter ExG# in the window for setting an external volume parameter.
3. Click OK.
The problem #2 occurs when after performing #1; click OK in the volume
addition window.
Causes and Updates Microcode modified so that an error message showing EXG setting
failure will be displayed for problem #1, and the error message for
problem #2 will indicate the reason for the parameter setting.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-01-44/00
Category Universal Volume Manager
Changed Part SVP
HDS Confidential 3 of 28
5 SSB=D310 caused by reset command issued from RCU to MCU
Phenomena In UR for open or z/OS, if the MCU received the reset command from the
RCU since the processing on the MCU failed due to overload or any
failure, SSB=D310 was reported.
Severity (High, Medium, Low) Low
Conditions of Occurrence Problem occurs with all the following conditions met.
1. UR for open or z/OS
2. RCU issues the reset command to MCU where processing fails due to
overload or any failure.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-44-00/00
Category Universal Replicator for Open or z/OS
Changed Part DKCMAIN
HDS Confidential 4 of 28
8 Improper status of external device during Cache De-stage
Phenomena After executing Disconnect Volume or Disconnect Subsystem, if the
micro-program exchanged during Cache De-stage, the external device
showed in normal state even though the device had not yet completed
Disconnect.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur with the condition both #1 and #2 met and any of
the following condition #3 or #4 or #5 met.
1. Use external devices.
2. After executing the Disconnect Volume or Disconnect Subsystem
command to external devices, some external devices, on which the
command has not completed, are in the process of Cache De-stage.
3. Perform micro-program exchange.
4. Perform PCB exchange.
5. Recovery from a MP failure
DKCMAIN: 60-01-30-00/00 and higher
Affected Products/Version
Fixed Product/Version DKCMAIN: 60-01-44-00/00
Category Universal Volume Manager
Changed Part DKCMAIN
2. PRG-IN command
i. The registered Key was not reported by Read key, or the same Key
was reported twice, or a Key other than the intended Key for the LU was
reported
HDS Confidential 8 of 28
1. True Copy Sync or Async
2. True Copy for open or z/OS
3. When pairs are in Pending state and either the following is performed:
- MCU planned power cycle
- MCU PS Off and then non-volatile PS On (for Sync only)
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-44-00/00
Category True Copy for Open or z/OS
Changed Part DKCMAIN
HDS Confidential 13 of 28
35 PPRC command failure for changing port attribute
With the Mode 114 set to On, when creating a path to a port with the
Phenomena RCU Target attribute by using the PPRC command, the path creation
failed with SSB EC=B101 reported.
Severity (High, Medium, Low) Low
Problem may occur with all the following conditions met.
1. True Copy for z/OS
2. Create a path to a port with the RCU Target attribute by using the
PPRC command (including GDPS) when, for instance, performing SWAP
between MCU and RCU.
Conditions of Occurrence
3. In another MP in CHT PCB that includes the port where path creation
was attempted, there exists the Target/RCU Target port to which a HOST
I/O or a TC or UR I/O is issued. In that case, load balancing is performed,
and the load of I/O requests becomes high in the MP in the port where
path creation was attempted.
Affected Products/Version DKCMAIN: 60-01-31-00/00 and higher
Fixed Product/Version DKCMAIN: 60-01-44-00/00
Category True Copy for z/OS
Changed Part DKCMAIN
Notes:
1. The problem always occurs when the above conditions are met.
2. The problem occurs only with RAID600, not with RAID500 or earlier.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-01-44/00
Category JAVA, Storage Navigator
Changed Part SVP
HDS Confidential 15 of 28
41 Remained dirty slots after removing mapped external LU
1. After disconnecting the mapped external LU, the dirty slots were not
de-staged.
Phenomena
2. When performing DELETE LU to the mapped external LU, the dirty
slots remained.
Severity (High, Medium, Low) Medium
The problem occurs when the following condition #1 and #2, or #1 and
#3 are met.
1. Perform ADD LU to an external device that exceeds the maximum
Conditions of Occurrence
capacity for each emulation type, but OPEN-V.
2. To the external VOL #1, perform format.
3. To the external VOL in #1, accept an host I/O.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-44-00/00
Category Universal Volume Manager
Changed Part DKCMAIN
HDS Confidential 16 of 28
Changed Part DKCMAIN
HDS Confidential 17 of 28
Changed Part DKCMAIN
HDS Confidential 21 of 28
Changed Part DKCMAIN
HDS Confidential 24 of 28
Severity (High, Medium, Low) Medium
The problem occurs when ADD LU of UVM, or the addition of V-VOL of
Conditions of Occurrence Snapshot or DP fails, and when MF VOL is mounted in the range of
HDEV to which the same SSID given as that of VOL attempted to add.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-44-00/00
Category Mainframe or open
Changed Part DKCMAIN
HDS Confidential 28 of 28