USP/NSC

MICROCODE VERSION 50-09-17-00/00

RELEASED 07/30/2007

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

NONE

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

1 Failure of SI pairresync -restore
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
In the configuration where HUR and SI share a volume or the
configuration where TC and SI share a volume, the pairresync -restore
command issued from RAID Manager failed.
Low
The problem occurs with all the following conditions met.
1. System Option 80 is set to ON
2. Perform pairresync -restore command from Raid Manager
3. Perform the command in #2 without the environment variable,
$HORCC_REST, set
4. Perform the command in #2 without the -fq parameter used
5. In the configuration where HUR and SI share a volume, or the
configuration where TC and SI share a volume, SI uses external
volumes
DKCMAIN: All
DKCMAIN: 50-09-17-00/00
Shadow Image
DKCMAIN

2 Inappropriate Parameter Change UA at Non Stop SCSI

Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
micro-program FC
When the MP rebooted at Non Stop SCSI micro-program exchange, the
current value of ModePage was initialized to the default value. In that
case, the host set the current value again with the Mode Select
command, and Parameter Change UA was returned to another host.
Low
Problem occurs when performing Non Stop SCSI microcode exchange.
DKCMAIN: All
DKCMAIN: 50-09-17-00/00
Open
DKCMAIN

HDS Confidential 1 of 4
3 Data inconsistency occurs in S-VOL of Copy-on-Write
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Causes and Updates
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
(C.O.W) Snapshot pair
When snapshot data cannot be stored at the time of a copy operation of
a C.O.W Snapshot pair (Restoration of C.O.W. Snapshot pair or
Shadow Image (SI) Resync/Restore in the case the volumes are used
also for SI) because the pool is full, the Snapshot pair does not suspend
with a failure. In addition, a data problem occurs in the secondary
volume (S-VOL).
<Note>
When snapshot data cannot be stored because the pool is full, the
C.O.W Snapshot pair suspends due to a failure.
High
(A) Conditions A occurs with all the following conditions (i) to (v) met.
(1) RAID500:50-04-06-00/00 and later
(2) C.O.W Snapshot P-VOL paired with multiple S-VOLS [1:n (n≧2)]
(3) No host I/O is issued to the P-VOL
(4) The pool used by the C.O.W Snapshot pair is FULL (SIM=6000xx
(xx: Pool ID) occurs)
(5) The C.O.W Snapshot pair is restored
(B) Conditions B occurs with all the following conditions (i) to (v) met.
(1.) RAID500:50-04-06-00/00 and later
(2) A Shadow Image P-VOL is also a C.O.W Snapshot P-VOL
(3) No host I/O is issued to the P-VOL
(4) The pool used by the C.O.W Snapshot pair is FULL (SIM=6000xx
(xx: Pool ID) occurs)
(5) Reverse Copy is performed for the Shadow Image pair
(C) Conditions C occurs with the following conditions (i) to (iv) met.
(1) RAID500:50-04-06-00/00 and later
(2) A Shadow Image S-VOL is also a C.O.W Snapshot P-VOL
(3) The pool used by the C.O.W Snapshot pair is FULL (SIM=6000xx
(xx: Pool ID) occurs)
(4) Normal Copy is performed to the Shadow Image pair/Update I/O is
issued to the paired SI P-VOL
When the old data copied from the primary volume (P-VOL) to the
pool, if the pool full state is detected, the copy operation is skipped.
However, the pair does not suspend with a failure. Because the C.O.W.
Snapshot pair whose snapshot data is not stored does not suspend with a
failure, the S-VOL data is referable even though snapshot data is un-
restored. As a result, since the updated P-VOL data is referred, a data
problem occurs in the S-VOL.
DKCMAIN: 50-04-06-00/00 and higher
DKCMAIN: 50-09-17-00/00
Copy-on-Write Snapshot
DKCMAIN
2 of 4
4 All LCP blockade at power cycle
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
5 Failure of SI pairresync –restore
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
6 Improper state of UR for z/OS P-VOL after Purge-Suspend
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
7 HUR pair remained Suspending at UR Flush Suspend
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
When a power cycle performed, all the LCP blocked.
Medium
The problem occurs when the data becomes invalid due to an
unnecessary bit added in reading LCP micro-program from SVP HDD.
SVP: All
SVP: 50-09-08/00
SVP
SVP
In the configuration where HUR, SI, and TC share the same volume,
the pairresync -restore command failed.
Low
The problem occurs with all the following conditions met.
1. System Option 80 is set to ON
2. Perform pairresync -restore command from Raid Manager
3. Perform the command in #2 without the environment variable,
$HORCC_REST, set
4. Perform the command in #2 without the -fq parameter used
5. Use the configuration where SI, HUR, TC share the same volume
DKCMAIN: 50-08-00-00/00 and higher
DKCMAIN: 50-09-17-00/00
Shadow Image
DKCMAIN
When Purge-Suspend performed during update I/O, status of P-VOL
sometime remained Suspending. (MCU: Suspending, RCU: Suspend)
Medium
The problem occurs with all the following conditions met.
1. UR for z/OS pair in Duplex or Duplex Pending state
2. Issue an update I/O to the UR pair
3. Perform Purge-Suspend, or failure suspend occurs
DKCMAIN: 50-04-20-00/00 and higher
DKCMAIN: 50-09-17-00/00
Universal Replicator for z/OS
DKCMAIN
When an HUR pair is suspended with the Flush specification, all the
pairs in the JNL group remained in the Suspending state.
Medium
The problem may occur with all the following conditions met.
1. HUR for z/OS or Open
2. Perform Flush Suspend or Delete to the M-VOL or P-VOL per group
DKCMAIN: All
DKCMAIN: 50-09-17-00/00
Universal Replicator for z/OS or Open
DKCMAIN
3 of 4
8 Unable to release relation by specifying XTNTLST
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
9 Pair split unavailable at differential resync failure
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
HDS Confidential
A relation created by using Incremental Flash Copy v2 might not able
to be released with the error message ANTF0480E displayed.
Low
The problem may occur with all the following conditions met.
1. Create a relation of FCv2 with the CHRCD (YES) specification
2. Change the specification to CHRCD (NO)
3. When performing #2, specify NOCOPY for the copy mode
4. Release the relation with the XTNTLST specification
DKCMAIN: 50-09-00-00/00 and higher
DKCMAIN: 50-09-17-00/00
Mainframe
DKCMAIN
When differential resync was performed with the path definition that
was not the one used for the UR initial copy, if the differential resync
operation failed, which required all data copy, the pair split operation
became unavailable after the failure.
Medium
The problem may occur with all the following conditions met.
1. UR for Open
2. Delete the path definition used for the initial copy from all the pairs
in a JNL group
3. Perform resync when the data to be copied has changed from
differential data to all data (all data becomes differential). For details of
the case where all data is to be copied as differential data, see Universal
Replicator User's Guide
DKCMAIN: 50-07-50-00/00 and higher
DKCMAIN: 50-09-17-00/00
Universal Replicator for Open
DKCMAIN
Invalid HUR pair state after Suspend/Delete operation during
initial copy
During the initial copy operation to an HUR pair, when performing
Suspend (Delete) to the pair, the status of the pair on MCU remained
Suspending (Deleting).
Medium
The problem occurs with all the following conditions met.
1. UR pair for z/OS or Open
2. During UR initial copy (pair status = COPY)
3. An I/O to the UR pair is in progress
4. Perform Suspend or Delete to the UR pair in the JNLG, or failure
suspend occurs
DKCMAIN: 50-03-80-00/00 and higher
DKCMAIN: 50-09-17-00/00
Universal Replicator for z/OS or Open
DKCMAIN
4 of 4