1-3 Name of Storage used on the other side available on Storage Navigator
Description For TC, TC for z/OS, UR, and UR for z/OS, the window of Storage Navigator displays the
name of the storage used on the other side as follows.
1. RAID600 is used on the other side:
HDS: USP V/ USP VM
HP: XP24000/XP20000
2. RAID500 is used on the other side:
HDS: USP/ NSC
HP: XP12000/XP10000
3. RAID450 is used on the other side:
HDS: 9900V
HP: XP1024/XP128
Display based on the configuration of the model itself. For example, if USP V connected to
with XP12000, as the storage used on the other side, USP displayed on the USP V side while
XP24000 displayed on the XP12000 side.
Changed Part JAVA
Documented Chapter 4 to 6 in True Copy/ True Copy for z/OS User’s Guide
Chapter 4 to 7 in Universal Replicator/ Universal Replicator for z/OS User’s Guide
HDS Confidential 1 of 42
1-5 Support for disaster recovery use of TC/TCZ Async
Description Disaster recovery function of TC Async or TC for z/OS Async now supported.
Changed Part DKCMAIN
Note The available micro-program versions for RAID450 are 21-14-37-00/00 and higher.
The available micro-program versions for RAID500 are 50-09-37-00/02 and higher.
Documented True Copy for z/OS User’s Guide, True Copy User’s Guide
2. Mainframe System
HDS Confidential 2 of 42
3. OPEN System
3-1 Improvement of the drag and drop operation for adding WWN
Description LUN Manager has a feature that a user can add a WWN with the drag and drop operation.
When a user performs the drag and drop operation by using the left button of a mouse, a
newly available confirmation message displays to warn the user if he really wants to add the
WWN.
HDS Confidential 3 of 42
The change of contents for Version 60-01-68-00/00
HDS Confidential 4 of 42
4 Inappropriate error message for CHT un-installation failure
Phenomena CHT installation without CSW mounted failed. After that, for un-
installation of the CHT to recover the error, when selecting Install-
Change Configuration, an error message INS2231E, which indicates that
a logical error occurred, and could not execute the un-installation.
Performing SVP reboot made no difference.
Then, after recovering the CHT by using the Maintenance window, re-
executed the un-installation, and the message INS2213E did not occur.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when performing Install-Change Configuration with
CHT blocked.
Causes and Updates Micro-program modified so that the error message displayed for the issue
above has been changed from INS2231E (Logical error has occurred.) to
INS2788I (Error response from DKC.)
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-01-67/00
Category JAVA, Storage Navigator
Changed Part SVP
6 CM correctable error
Phenomena PS Off was performed, and immediately after the power was turned off,
the power was turned On. After the startup, a CM correctable error was
detected, and SIM=FFF0xx and SSB=32E4 were reported.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur with all the following conditions met.
1. The PS Off operation ends normally
2. Time period between power off and the next startup is within 1 hour
3. Perform PS On
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Cache memory
Changed Part DKCMAIN
HDS Confidential 6 of 42
Conditions of Occurrence The problem may occur with all the following conditions met.
1. An SI pair using DP-VOL
2. Perform PS Off
3. After #2, perform volatile PS On
4. Mode 460 is set to Off
Affected Products/Version DKCMAIN: 60-01-30-00/00 and higher
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Shadow Image, Dynamic Provisioning
Changed Part DKCMAIN
HDS Confidential 7 of 42
Conditions of Occurrence The problem may occur with all the following conditions met.
1. Write command
2. Sequential access
3. Data transfer length is less than 256K
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Open
Changed Part DKCMAIN
HDS Confidential 8 of 42
Conditions of Occurrence The problem may occur with all the following conditions met.
1. Any of the following products is in use:
- TC Sync for z/OS or Open
- TC Async for z/OS or Open
- UR for z/OS or Open
2. Reset occurs due to such as hardware failure
Affected Products/Version DKCMAIN: 60-01-01-00/00 and higher
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category True Copy Sync/Async and Universal Replicator for z/OS or Open
Changed Part DKCMAIN
17 SSB=0x2115 at Resync
Phenomena When an SI pair in pair split operation used DP-VOL as its P-VOL and S-
VOL, if Resync performs to pair, the log, SSB=0x2115, was output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur with all the following conditions met.
1. An SI pair uses DP-VOL for its P-VOL and S-VOL
2. When the pair status is COPY(SP) or PSUS(SP) for the par split
operation, perform Resync to the pair
Affected Products/Version DKCMAIN: 60-01-30-00/00 and higher
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Shadow Image for Open, Dynamic Provisioning
Changed Part DKCMAIN
HDS Confidential 9 of 42
20 Slow display of performance management monitor
Phenomena If the configuration of Parity Group and LDEV was large, when any of
the nodes shown below was selected in the Performance Management
window, the Waiting dialog window was displayed and it took long,
sometimes more than 50 minutes, to complete the display of the monitor
window.
Node to be selected:
- In the LDEV tab the Subsystem or Parity Group folder
- In the Physical tab, the Subsystem, Parity Group, External folder, or
each tree node of Parity Group or External Group.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs with either of the following condition #1 or #2 met,
and when displaying the monitoring data by selecting any of the folder or
tree nodes shown in #3.
1.The configuration where a virtual volume group exists, and the
maximum number of Parity Groups is created in the group
2. A configuration where the maximum number of LDEV is created in the
Parity Group
3. Folder or tree node to be selected in the following tabs of Performance
Management window:
- In the LDEV tab the Subsystem or Parity Group folder
- In the Physical tab, the Subsystem, Parity Group, External folder, or
each tree node of Parity Group or External Group.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-01-67/00
Category Performance Manager
Changed Part SVP
HDS Confidential 10 of 42
22 Check Condition without Sense Data during I/O to TC pair
Phenomena During an I/O operation to a TC Sync pair, the reported Check Condition
did not contain Sense Data.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs with all the following conditions met.
1. TC Sync for Open pair in the COPY or PAIR state
2. Issue an I/O to the OPEN volumes
3. The TC pair reports the OPEN host Check Condition with the
following SSB:
SSB EC= 0xb819, 0xb839, 0xb83a, 0xb848
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category True Copy for Open
Changed Part DKCMAIN
HDS Confidential 11 of 42
25 COW pair deletion failure
Phenomena The deletion of a COW pair failed with WCHK1 reported.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when a hardware failure occurs (CHK1 or CHK3)
during the deletion of a COW pair.
Affected Products/Version DKCMAIN: 60-01-30-00/00 and higher
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Copy-on-Write Snapshot
Changed Part DKCMAIN
HDS Confidential 13 of 42
31 TC pair suspend at S-VOL read during update or initial copy
Phenomena 1. During the copy operation using TC Sync/Async for z/OS or Open, if
the S-VOL was read, SSB logs indicating CHK2 detection were
sometimes output, including EC=0xB2FF, 0x3570, or 0xD30D
2. In the case of #1, if CHK2 exceeded the threshold, which is 128 times
per day per MP, the MP was blocked
3. In the case of #2, if all the MPs on the path used for TC were blocked,
the TC pair was suspended
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs with all the following conditions met.
1. TC Sync/Async for z/OS or Open
2. The configuration of the ECCG where the TC secondary volume
belongs is RAID1
3. Update copy or initial copy to the TC S-VOL is in progress
4. Issue a read I/O to the TC S-VOL from the host
5. The commands of #3 and #4 are issued to the same slot of the TC S-
VOL at the same time
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category True Copy for z/OS or Open
Changed Part DKCMAIN
HDS Confidential 14 of 42
33 Endless read or write operation to SI pair
Phenomena When an SI pair was using an external VOL with data copied from and a
DP-VOL with data copied to, the read or write operation to the pair did
not end.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur with all the following conditions met.
1. An SI pair uses an external VOL where the data is copied from and a
DP-VOL where the data is copied to
2. The SPLIT copy operation is in progress with the SI pair
3. The size of the external volume is not dividable by 256 Kbyte (when
creating CVS with block specified)
4. A host I/O is issued to the SI pair (only to the last slot)
Affected Products/Version DKCMAIN: 60-01-30-00/00 and higher
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Universal Volume Manager, Shadow Image for Open
Changed Part DKCMAIN
HDS Confidential 15 of 42
36 Unable to detect failure of JNL restoration
Phenomena With JNL restored on the secondary DKC in the HUR and TC Async
configuration, failure of the restoration not detected.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs with all the following conditions met.
1. On the secondary DKC where HUR or TC Async is in operation
2. CHP is connected to a port that has the Target attribute
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Universal Replicator, True Copy Async for z/OS or Open
Changed Part DKCMAIN
HDS Confidential 16 of 42
40 SSB=12f6 at CHP failure
Phenomena When CHP failed (ABEND), SSB=12f6 was reported.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when CHP fails (ABEND).
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Open or Mainframe
Changed Part DKCMAIN
HDS Confidential 17 of 42
44 SSB=23FF at pair status display during SI Initialize
Phenomena During the Initialize operation of Shadow Image, when the pair display
command issued from RAID Manager, SSB=23FF was reported,
indicating that there was a logical inconsistency.
In addition, when pair operation of TC or UR performed during its
Initialize operation, an error of the pair operation sometimes wrongly
occurred.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs with all the following conditions met.
1. Perform Initialize from the window of SI for z/OS or Open
2. Perform any of the following before the Initialize is completed:
-Pair display command
-TC pair operation
-UR pair operation
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Shadow Image for z/OS or Open
Changed Part DKCMAIN
47 WCHK1 at PS ON
Phenomena WCHK1 reported at PS ON.
HDS Confidential 18 of 42
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs with all the following conditions met.
1. SM for DP is installed
2. Mode 460 is set to ON
3. After PS Off, perform SM volatile PS ON
4. SVP cannot be accessed (PS is Off or SVP is unavailable)
Affected Products/Version DKCMAIN: 60-01-30-00/00 and higher
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Copy-on-Write Snapshot
Changed Part DKCMAIN
HDS Confidential 19 of 42
Conditions of Occurrence The problem occurs with all the following conditions met.
1. A PDEV failure occurs anywhere between PDEV mount start and end
2. Automatic Correction Copy or Dynamic Sparing does not start when
the PDEV failure occurs
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category HDD
Changed Part DKCMAIN
HDS Confidential 21 of 42
57 No forwarding of path watch time to RCU of UR
Phenomena In the JNL Operation window of UR or UR for z/OS on the Storage
Navigator computer, Change JNL Option executed when the JNL was in
the Initial state. At that time, in the Change JNL Option window, although
Forward Path Watch Time was set to Yes, the path watch time was not
forwarded to the RCU.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs with all the following conditions met.
1. The status of JNL is Initial
2. In Change JNL Option box set Forward Path Watch Time to Yes.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-01-67/00
Category Universal Replicator for z/OS or Open
Changed Part SVP
HDS Confidential 22 of 42
60 Host path port blockade with SIM=213E at SVOL group
operation
Phenomena In the configuration where 1 JNLG had 4,096 pairs, when performing a
group operation with S-VOL specification, SIM=231E (LCM
HARDWARE ERROR) occurred, and the port for the host path was
blocked.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs with all the following conditions met.
1. UR for z/OS
2. 1 JNLG has 2,000 pairs or more
3. Perform a group operation (Suspend, Delete, or Swap-Suspend) with
S-VOL specification
4. Host ESCON
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Universal Replicator for z/OS
Changed Part DKCMAIN
HDS Confidential 23 of 42
63 Invalid performance value displayed on Performance Monitor
Phenomena When displaying the performance value of (1) and (2) below, the amount
of data transfer to/from an externally connected LDEV and the value of
the response time did not include the value for the write commands, but
included the values only for the read commands:
(1) Under the External node in the Physical tab in the Performance
Monitor of Storage Navigator
(2) The acquired data by using Export Tool with the group PhyExG/
group PhyExLDEV option
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when issuing an I/O to an external volume.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-01-67/00
Category Performance Monitor
Changed Part SVP
HDS Confidential 24 of 42
overwritten.
71 MP restoration failure
Phenomena MP restoration sometimes failed.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur with all the following conditions met.
1. MP restoration is performed
2. Pre-reading is performed by the OS program in MP
3. Processing of hardware WCHK1 conflicts with the processing in #2
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Micro Processor
Changed Part DKCMAIN
HDS Confidential 29 of 42
Category True Copy for z/OS or Open/ Universal Replicator for z/OS or Open
Changed Part DKCMAIN
HDS Confidential 30 of 42
Affected Products/Version DKCMAIN: 60-01-30-00/00 and higher
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Universal Volume Manager
Changed Part DKCMAIN
HDS Confidential 32 of 42
95 Query operation from BCM failure with SSB=eba9
Phenomena The Query operation from BCM failed with SSB=eba9 output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs with all the following conditions met.
1. Perform remote operation using BCM
2. RCU Target MP on remote operation path is highly loaded (A timeout
error due to many I/Os in R-DKC causes a host reset, for example.)
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Mainframe
Changed Part DKCMAIN
HDS Confidential 35 of 42
106 Multiple cache PCB addition failure
Phenomena After failing to install cache PCBs, though trying to replace the blocked
PCBs by following the procedure described in section 2.6.3 in
INSTALLATION SECTION of Maintenance Manual, the attempt always
failed.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when any of the following conditions is met after
installing two or more cache PCBs per cluster.
1. INLINE CUDG of cache PCB installed for cluster 1, SVP reboots
2. INLINE CUDG of cache PCB installed for cluster 2, SVP reboots
3. After the normal end of the INLINE CUDG operation of cache PCB
that is installed for cluster 1, the cache PCB recovery processing for
cluster 1 ends abnormally
4. After the normal end of the INLINE CUDG operation of cache PCB
that is installed for cluster 2, the cache PCB recovery processing for
cluster 2 ends abnormally
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-01-67/00
Category Open or mainframe
Changed Part SVP
HDS Confidential 36 of 42
109 Correction access after PS recovery
Phenomena If DKU PS failed, it was expected that PDEV ports blocked and then
automatically recovered when power supply was back to normal
condition. However, at some timing, PDEV blocked in one of the Fiber
loops, and blockade caused correction access when power was back.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when a failure occurs in the DKU PS box, or power
supply to the DKU is stopped due to power outage.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category DKU
Changed Part DKCMAIN
HDS Confidential 37 of 42
112 Data inconsistency due to miscalculation for data erasing range
Phenomena When WR FULLTRK(95) command was issued to the URZ pair, the
range of data to be erased on the S-VOL was miscalculated, which led the
inconsistency between P-VOL and S-VOL.
Severity (High, Medium, Low) High
Conditions of Occurrence The problem occurs with all the following conditions met.
1. UR for z/OS
2. Issue the WR FULLTRK(95) command or the command that performs
WRITE from R0D; DX/LOC/WRD(R0)/WRCKD(R1)
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Universal Replicator for z/OS
Changed Part DKCMAIN
HDS Confidential 38 of 42
115 PIN with highly loaded DRR
Phenomena When DRR was highly loaded, data might become PIN together with its
corresponding parity.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur with all the following conditions met.
1. RAID5/6
2. DRR is loaded so high that many SSB=a8ac, for example, are output
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Open or mainframe
Changed Part DKCMAIN
HDS Confidential 40 of 42
selected, the pairs supposed to be displayed were not displayed.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs with all the following conditions met.
1. Root volumes with multiple SI pairs are defined on the same port.
2. Nine or more pairs, with configuration 1:1 or 1:2 for the root volumes
3. In Shadow Image, specify port on which root volume is defined.
4. Open Display Filter dialog box, select Cascade and L1-L2, and then
close the dialog box
Affected Products/Version DKCMAIN: 60-01-30-00/00 and higher
Fixed Product/Version DKCMAIN: 60-01-68-00/00
Category Shadow Image for Open
Changed Part DKCMAIN
HDS Confidential 42 of 42