USP/NSC

MICROCODE VERSION 50-09-87-00/00

RELEASED 08/07/2009
Newly supported features and functions for Version 50-09-87-00/00
1. Mainframe & OPEN System
1-1 Updated check box title for HDD micro-program exchange
Description On the Micro-program Exchange dialog box, the check box of “DKU” is changed to
“DKU/HDD” so that the type of HDD micro-program can be selected easily.

Changed Part SVP

2. Mainframe System
NONE

3. OPEN System
NONE

The change of contents for Version 50-09-87-00/00

1 I/O error while using S-VOL after HUR suspend
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Causes and Updates
Affected Products/Version
Fixed Product/Version
Category
Changed Part
After UR (Universal Replicator) pair suspends, an I/O error (No Record
Found) may occur while using an S-VOL.
High
May occur with all the following conditions A, B, C, D, and E met.
A. RAID500: 50-03-30-00/00 and higher/ RAID600: All versions
B. Mainframe connection
C. Suspend is executed while “Enable” is specified as S-VOL Write option
for UR pair
D. Write operation for UR S-VOL. (*1)
E. UR pair Resync (*2)
Additional information
*1: Write only R0 with WRFTK command or write with CCW using
LocOpe=WRTRK of LOCATE parameter
*2: Status becomes Data inconsistency by performing Resync, and then the
phenomenon occurs by the use of the S-VOL after the next Suspend
Due to code failure, when writing only R0 record, but not R1 and later
records, for a UR S-VOL using a WRFTK command or LocOpe of
LOCATE parameter which uses the WRTRK command, the difference of
the S-VOL cannot be set to ON. Therefore, the written track on S-VOL is
not copied from a P-VOL after UR pair Resync. As the result, an I/O error
(No Record Found) occurs while using an S-VOL after UR pair suspend.
DKCMAIN: 50-03-30-00/00 and higher
DKCMAIN: 50-09-87-00/00
Universal Replicator for z/OS
DKCMAIN

HDS Confidential 1 of 2
2 TCA pair status stuck in Suspending
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
3 Invalid SIM=21AA error level output at SFP hardware failure
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Causes and Updates
Affected Products/Version
Fixed Product/Version
Category
Changed Part
4 Communication failure between DKC and master SVP
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
During host I/O operations to a TCA pair, when suspend occurred due to
overflow of Side file, the pair status became Suspending and didn't transfer
after that.
Medium
The problem may occur when all the following conditions are met.
(1) OPEN-VOL
(2) P-VOL side is RAID500
(3) Host I/O is being executed to a TCA pair
(4) Multiple LUN are set to one CT group
(5) Suspend occurs due to Side file overflow
DKCMAIN: All
DKCMAIN: 50-09-87-00/00
True Copy for Open
DKCMAIN
When the SFP hardware failed, the link to the port went down and SIM
was output. In this case, the error level of the output SIM=21AA was
Service; however, the expected error level was Moderate.
Medium
While subsystem is in operation, periodic monitoring for SFP hardware
failure is performed, and a failure is detected by monitoring processing.
The micro-program has been modified so that the SIM error level names
are changed as follows:
1. The error level of SIM=21AA is changed from Service to Moderate
2. Name of SIM=21AA is changed from "SFP warning" to "SFP TxFault"
DKCMAIN: 50-03-30-00/00 and higher
SVP: 50-00-03/00 and higher
DKCMAIN: 50-09-87-00/00
SVP: 50-09-83/00
SFP
DKCMAIN, SVP
Performing expiration checking on a Program Product (PP) from a standby
SVP to a DKC, the communication from DKC to master SVP might fail.
Low
The problem occurs when the SVP is in duplicated configuration.
SVP: All
SVP: 50-09-83/00
SVP
SVP
2 of 2