USP

MICROCODE VERSION 50-05-26-00/00

RELEASED 02/21/06

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

NONE

The change of contents for Version 50-05-26-00/00

1 Unable to open Storage Navigator Shadow Image for z/OS panel

Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
The following two phenomena may occur.
Phenomenon 1: The Storage Navigator Shadow Image for z/OS panel
cannot be opened due to timeout.
Phenomenon 2: When the operation in Phenomenon 1 is performed
repeatedly (4 times or more), Channel Adapter (CHA) MP is blocked.
High
The Shadow Image for z/OS panel is opened in Storage Navigator when
either of the conditions (A) or (B) is met.
A. All the following conditions (1-5) are met
1. USP
2. Number of CUs is four or less (The number of LDEV is 1024 or less)
3. No HUR JNL Group Extension, and Flash Copy V2/CoW Snapshot is
not used (In the Install Function section of the Shared Memory Size
Configuration dialog box in the SVP, HUR JNL Group Extension and
Flash Copy v2/CoW Snapshot are not selected)
4. 512 MB DIMM Shared Memory, and the Shared Memory configuration
is the High Performance mode (4 SM PK configuration)
5. The cache size (both sides) is 256 GB or smaller

B. All the following conditions (1-5) are met

Affected Products/Version
Fixed Product/Version
Category
Changed Part
1. USP
2. The number of CUs is four or less (The number of LDEV is 1024 or
less)
3. No HUR JNL Group Extension, Flash Copy V2/CoW Snapshot is not
used, and no TC/UR/SI Extension
(In the Install Function section of the Shared Memory Size Configuration
dialog box in the SVP, HUR JNLG Extension, Flash Copy V2/CoW
Snapshot, and HMRCF/ HOMRCF/HRC/HORC/HUR/HIHSM/Hi-Copy
Extension are not selected)
4. 1 GB DIMM Shared Memory, and the Shared Memory configuration is
the High Performance mode (4 SM PK configuration)
5. The cache size (both sides) is 256 GB or smaller
DKCMAIN: 50-04-06-00/00 and higher
DKCMAIN: 50-05-26-00/00
Shadow Image for z/OS
DKCMAIN

HDS Confidential 1 of 5
2 EQC when SIz/FCv1 S-VOL Used as TCZ M-VOL
Phenomena
Severity (High, Medium, Low)
Affected Products/Version
Fixed Product/Version
Category
Changed Part
3 Two Ports Blocked due to WCHK1
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
4 Data Inconsistency due to dummy JNCB during SM replace
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
5 Performance Degraded when Power De-stage Mode ON at RCU
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
Phenomenon 1: In case an SIZ source volume was also used as a TCZ
main volume, EQC was reported to the host when starting up Shadow
Image for z/OS Split
Phenomenon 2: In case an FCv1 source volume was also used as a TCZ
main volume, EQC was reported to the host when creating an FCv1 pair.
Medium
DKCMAIN: 50-04-22-00/00 and higher
DKCMAIN: 50-05-26-00/00
FICON
DKCMAIN
When receiving I/Os, two ports in the DKC were reported of WCHK1
(SSB=B405) and were blocked as a result.
High
When invalid data frames are received.
DKCMAIN: All
DKCMAIN: 50-05-26-00/00
OPEN
DKCMAIN
When comparing the HUR P-VOL data with the HUR S-VOL one after
SM replacement, the data was not consistent.
High
This problem occurs when all the following conditions are met.
1. The MP timer lags behind others during SM replacement or online
micro program exchange.
2. An update I/O is issued to the HUR pair.
3. The HUR pair status is PAIR/Pending
DKCMAIN: 50-05-22-00/00 and higher
DKCMAIN: 50-05-26-00/00
Universal Replicator/ Universal Replicator for z/OS
DKCMAIN
In case of power de-stage mode ON at the RCU of TC (Sync/Async)/ TCZ
(Sync/Async), if the cache was overloaded at the RCU, the copy
performance degraded. In the worst case, the pair suspends or host MIH
(or host reset) might occur.
Medium
This problem occurs when all the conditions are met.
(1) TC (Sync/Async)/ TCZ (Sync/Async) pairs,
(2) Power de-stage mode ON at RCU,
(3) Parity group where TC S-VOL of RCU belongs is in heavy workload.
DKCMAIN: 50-04-20-00/00 and higher
DKCMAIN: 50-05-26-00/00
True Copy (Sync/Async)/ True Copy for z/OS (Sync/Async)
DKCMAIN
2 of 5
6 Drive copy ABEND or ECC/LRC error PIN
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
7 Failed to Detect LAN IP Address
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
When a Write error PIN occurs due to a failure in the target HDD during a
correction copy or drive copy*1, if another drive copy is performed again
after the first correction copy or drive copy, the following problem will
occur.
- Mode22=OFF: The drive copy ends abnormally. (SSB=9b1f, SIM=463x)
The drive copy will end abnormally again even if the target HDD is
replaced.
- Mode22=ON: the Write error PIN is changed to an ECC/LRC error PIN,
However, the drive copy continues.
*1: Using the SVP to copy data from one HDD to another like the dynamic
sparing or the copy back.
High
This problem may occur when all the following conditions are met.
A. RAID500
B. A Write error PIN occurred in the target HDD due to a failure during a
correction copy or drive copy (SSB=9fa1/9fb1, SIM=EF4xxx occurred).
C. The second drive copy is performed after the above B (correction copy
or drive copy).
D. Micro program versions are 50-03-76-00/00 and later or 50-03-99-
00/02 and later or 50-04-06-00/00 and later.
DKCMAIN: 50-03-76-00/00 and later or 50-03-99-00/02 and later or 50-
04-06-00/00 and later.
DKCMAIN: 50-05-26-00/00
HDD
DKCMAIN
When logging into the Web Console, an error (10 6027: Network Error)
was reported.
Medium
A. This problem occurs when all the conditions are met.
(1) Plug off the external LAN cable or power off the external LAN HUB,
(2) Open Property and change the IP address,
(3) Connect the external LAN by plugging in the external LAN cable or
powering on the external LAN HUB.
B. This problem occurs when all the conditions are met.
(1) The IP address of the external LAN is not defined,
(2) Open Property and change the IP address,
(3) Set a valid IP address to the external LAN,
(4) If the external LAN is not connected, plug in the external LAN cable or
power on the external LAN HUB.
SVP: All
SVP: 50-05-22/00
RMI
SVP
3 of 5
8 Cache Temporary Error
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
9 Performance degradation on Flash Copy Version 2 volume
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
10
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
11
Phenomena
HDS Confidential
When performing DB2, SIM=FFF1 (Cache Temporary Error) occurred.
Medium
This problem occurs when all the conditions are met.
1. DKC emulation type = 2105,
2. RAID1 (including external connection),
3. Compatible PAV for z/OS is in use or multiple hosts access the same
LDEV simultaneously (Multiple Allegiance environment),
4. An environment of issuing the A5 command (write track data).
DKCMAIN: All
DKCMAIN: 50-05-26-00/00
Mainframe
DKCMAIN
The performance of sequential read using Flash Copy Version2 source and
target volumes may be degraded (About two to three times, depends on the
condition).
Medium
This problem occurs when A or B is met.
A. A sequential read is performed using a RDTRK command to the Flash
Copy Version2 source volume (Example: DUMP job is performed to the
source volume)
B. A sequential read is performed using a RDTRK command to the copied
area in the Flash Copy Version2 target volume (Example: DUMP job is
performed to the source volume)
DKCMAIN: 50-05-06-00/00 and later
DKCMAIN: 50-05-26-00/00
Flash Copy Version 2
DKCMAIN
Invalid Sleep State after Setting VMA attributes in Power De-
stage Mode
After having set VMA attributes in the power de-stage mode, if performing
Read/Write, the operation might go into sleep state temporarily.
Low
This problem occurs when all the conditions are met.
1. Power de-stage mode,
2. Setting VMA,
3. Setting VMA attributes,
4. Performing Read/Write operations.
DKCMAIN: All
DKCMAIN: 50-05-26-00/00
Data Retention Utility
DKCMAIN
IPL Failure with SSB=7A11/7A13
In case IPL failed to end, SSB=7A11 (issuing I/Os on the volume with
4 of 5

Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
12
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
13
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Causes and Updates
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
Volume Security set up) or SSB=7A13 (4A retry with host node invalid)
occurred.
High
This problem occurs when all the conditions are met.
1. FICON connection,
2. Setting the program product of Volume Security with version V04 or
higher or using Volume Security with version V03+1 or lower.
3. Starting up ELP (PS-ON/ cable plugging off/in/ PCB replacement/ CHP
ON),
4. Sending LBY to CHL with ELP processing.
HTP: All
HTP: 50-05-21
Mainframe (FICON)
HTP
Pair Suspends or Data Inconsistencies after TC Resync
After performing the TC Resync, the pairs were suspended (EC=0xc9b2)
or data inconsistencies between MCU and RCU occurred.
High
This problem occurs when all the conditions are met.
1. True Copy (Sync/Async)/ True Copy for z/OS (Sync/Async) pairs,
2. Resync after suspend,
3. Update I/O from the host.
DKCMAIN: All
DKCMAIN: 50-05-26-00/00
True Copy (Sync/Async)/ True Copy for z/OS (Sync/Async)
DKCMAIN
Data Inconsistencies of URZ Pairs
After issuing update I/Os to the URZ pairs in the Duplex status, data
inconsistencies between the source volume and the target volume occurred.
High
The problem occurs in rare cases when creating the Universal Replicator
for z/OS pairs.
The micro-program has been modified to fix the problem.
DKCMAIN: 50-03-22-00/00 and higher
DKCMAIN: 50-05-26-00/00
Universal Replicator for z/OS
DKCMAIN
5 of 5