HDS Confidential 1 of 2

USP/NSC
MICROCODE VERSION 50-09-98-00/05
RELEASED 01/28/2011

Newly supported features and functions for Version 50-09-98-00/05

1. Mainframe & OPEN System
NONE

2. Mainframe System
NONE

3. OPEN System
NONE

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

1 Failure of differential data storing and all data copy delta resync
Phenomena Phenomenon1
When a host I/O was issued to a P-VOL (JNLG# 0) in UR/URz 3DC delta
resync configuration where old and new models were connected (PDKC:
R700, LDKC: R500, PDKC: R600), the differential data (U% and Q-CNT
value) was not stored in LDKC (JNLG#0).
Phenomenon2
When delta resync was executed after executing a host I/O to a P-VOL
(JNLG# 0) in UR/URz 3DC delta resync configuration where old and new
models were connected (PDKC: R700, LDKC: R500, PDKC: R600), the
delta resync turned to all data copy delta resync.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) UR for Open or z/OS.
(2) Delta configuration (0 is specified for JNLG# on R side)
(3) A UR pair in a JNLG different from the above is created. (R site is
R500. The storage at P site is the same one at R site in the above delta
configuration)
(4) For the configuration in (3), a pair is added or deleted.
Causes and Updates The micro-program has been modified to fix the problem.
Affected Products/Version DKCMAIN: 50-07-64-00/00 and higher
Fixed Product/Version DKCMAIN: 50-09-98-00/05
Category Universal Replicator for Open or z/OS
Changed Part DKCMAIN








HDS Confidential 2 of 2


2 Mainframe host performance degradation
Phenomena After 3154 PAV Alias devices were added, performance of the Mainframe
host degraded.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Mainframe environment.
(2) Large number of devices is added.
(3) Because of the above (2) operation, IOS SQA area of the main storage
on host side becomes insufficient.
Causes and Updates The micro-program has been modified to output a Storage Navigator
message (9010-59341) to recommend the user to register Alias devices per
CU when attempting to add Alias devices to multiple CUs at a time.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 50-09-89/00
Category Mainframe
Changed Part SVP

3 Unable to connect to Storage Navigator
Phenomena When trying to use Storage Navigator, a message "An Error occurred
(8005 3)" appeared and the connection failed.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) One of the following is executed.
(a) SVP reboot
(b) Connecting and disconnecting a LAN cable connected to SVP
(c) Changing network setting of SVP
(2) Windows is activated while the process ID (*1) of java exe exceeds
65535 (*2).

*1: Executing unit of program allocated by Windows, which can be
confirmed by PID of Task Manager.
*2: Occurrence frequency, which depends on the control on Windows side,
is quite low.
Causes and Updates The micro-program has been modified to fix the problem.
Affected Products/Version SVP: 50-03-16/00 and higher
Fixed Product/Version SVP: 50-09-89/00
Category Storage Navigator
Changed Part SVP