USP/NSC

MICROCODE VERSION 50-09-82-00/00

RELEASED 01/07/2009
Newly supported features and functions for Version 50-09-82-00/00
1. Mainframe & OPEN System

1-1 Support for DKS2F-K HDD

Description DKS2F-K72FC/K146FC/K300FC HDD of 15-krpm type has been supported as follows.
- DKS2F-K72FC supports the same RAID level, emulation type, and the number of settable
LDEV that DKS2C/2D-K72FC/2E-K72FC supports. These DKU are mutually compatible.
- DKS2F-K146FC supports the same RAID level, emulation type, and the number of
settable LDEV that DKS2D-K146FC/ DKS2E-K146FC supports. These DKU are mutually
compatible.
DKS2F-K300FC supports the same RAID level, emulation type, and the number of settable
LDEV that DKS2E-K300FC supports. These DKU are mutually compatible.

Changed Part CONFIG, DKU

Note None
Documented INSTALLATION, THORY OF OPERATION, OPEN, and ACC (ACTION CODE) of
Maintenance Manual

1-2 Support for Windows Vista for Console PC (Maintenance PC)

Description Window Vista has been newly added as an OS of a console PC (Maintenance PC).

Changed Part None

Note ESC/CTSC LOG#: R600-21834
Documented None

2. Mainframe System

2-1 New button in Pair Operation window to delete registered command devices
Description To delete all the command devices registered via BCM, a button has been added in the Pair
Operation window of True Copy for z/OS of Storage Navigator that is started from an SVP
launcher. Clicking the button can delete all the registered command devices.

To use this function, both the DKCMAN and SVP must use the modified micro-programs.

Changed Part DKCMAIN, SVP

Note ESC/CTSC LOG# R500-80626
Documented True Copy z/OS in WEB CONSOLE Section of Maintenance Manual

3. OPEN System
NONE

HDS Confidential 1 of 5
The change of contents for Version 50-09-82-00/00
1 Failure of SM un-installation without SM for E-Copy mounted
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
2 Maintenance operation failure on HUR MCU side
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
3 ISCSI PC start failure after PS OFF and SM volatile PS ON
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
Un-installing SM failed.
Medium
The problem occurs when all the following conditions are met.
1. Server less Backup Enabler (E-Copy) is ON
2. SM for E-Copy is not mounted In Shared Memory Size Configuration
window, the E-Copy/TPF checkbox for the Install function is not checked
3. SM un-installation is performed as a maintenance operation
DKCMAIN: 50-03-99-00/08 and higher
DKCMAIN: 50-09-82-00/00
Server less Backup Enabler
DKCMAIN
On HUR MCU side, any of the following operations might fail.
Cache exchange, Shared memory exchange, PS OFF, or Offline micro-
program exchange
Low
The problem may occur when all the following conditions are met.
1. In a JNL group, multiple pairs in the Duplex and Suspend states coexist
2. All the pairs in the Duplex state in #1 are deleted by pair operation
without Group range but LU range specified
3. When the pairs in #2 are in Deleting state (while the status is changing
from Duplex to Simplex), Failure-suspend occurs on the RCU side. At this
time, the pair deletion processing ends normally and the status of the pairs
with LU range specified changes into Simplex. The Storage Navigator
window displayed "STOP" as the status of the JNL group
4. On the HUR MCU side, any of the following maintenance operations is
performed: Cache exchange, Shared memory exchange, PS OFF, or
Offline micro-program exchange
DKCMAIN: All
DKCMAIN: 50-09-82-00/00
Universal Replicator for z/OS or Open
DKCMAIN
1. After scheduled PS OFF and PS ON, iSCSI PC start-up failed
2. When an LU in #1 was copied by using Shadow Image, the operation
failed with Cash Slot Busy
Medium
The problem occurs when all the following conditions are met.
1. iSCSI PCB is installed
2. SM volatile PS ON after scheduled PS OFF
3. Initialization is in progress at the odd numbers of MPs
DKCMAIN: 50-06-11-00/00 and higher
DKCMAIN: 50-09-82-00/00
Open
DKCMAIN
2 of 5
4 Failure of CoW pool creation after MP replacement
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
5 Unable to map external volume
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
6 Inaccessible LU due to a DKA MP failure
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
Creating a CoW pool failed with a Storage Navigator error message output
(3005 58474: The capacity of shared memory is insufficient or an error
occurred during SVP processing.).
Medium
The problem occurs when all the following conditions are met.
1. During CoW pool creation, WCHK1 occurs
2. The error in #1 is recovered by MP replacement
3. After the recovery, SI is not initialized
4. A CoW pool is created
DKCMAIN: 50-04-06-00/00 and higher
DKCMAIN: 50-09-82-00/00
Copy-on-Write Snapshot
DKCMAIN
An external volume could not be mapped.
Medium
The problem may occur when all the following conditions are met.
1. Attributes of two or more ports are set to External Port, and all External
Port attribute settings are changed to settings other than External Port
2. Some of the ports in #1 are again set to External Port attribute
3. Between the operations in #1 (the attributes of two or more ports are set
to External Port) and #2, the MP that processes the External Port in #1 is
not rebooted for maintenance processing as follows: CHT Replacement
(including dummy replacement), microcode exchange, and power cycle
DKCMAIN: All
DKCMAIN: 50-09-82-00/00
Universal Volume Manager
DKCMAIN
During a usual operation, a failure with CHK1B occurred at the DKA
PCB, and then LU became inaccessible.
Medium
The problem may occur when all the following conditions are met.
1. Any of the following conditions is met.
1-1. LDEV format is in progress
1-2. CM or SM maintenance is in progress
1-3. PS OFF is in progress
1-4. Non-volatile PS ON is in progress after power outage
1-5. Volume Migration is in operation
1-6. An I/O needs to wait for Cache resource to be available
2. In the processor on the DKA side, any of the following failures occurs:
CHK3, CHK1B, or hang-up
DKCMAIN: All
DKCMAIN: 50-09-82-00/00
Open or mainframe
DKCMAIN
3 of 5
7 Pair failure suspend at MIH or server timeout
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
8 Write Pending rate 70% if write to unavailable external volume
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Affected Products/Version
Fixed Product/Version
Category
Changed Part
9 Core dump wrongly generated when pair split command
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
Pairs of TC/TCA/TCz/TCzA/UR/URz/SI/SIz/Snapshot were suspended
when MIH or server timeout occurred.
Medium
The problem may occur when all the following conditions are met.
1. Pairs of TC/TCA/TCz/TCzA/UR/URz/SI/SIz/Snapshot
2. Either of the following:
An MIH occurs or Server timeout occurs
DKCMAIN: All
DKCMAIN: 50-09-82-00/00
TC/TCA/TCz/TCzA/UR/URz/SI/SIz/Snapshot
DKCMAIN
Write to a mapped external volume where neither Read nor Write was
available. In this case, because no data could be written on the external
volume, Write Pending rate reached 70%, causing cache overload.
Medium
The problem occurs when all the following conditions are met.
1. Read or Write cannot be performed for an external volume though the
volume is in the normal state
2. Write is performed for the external volume
DKCMAIN: All
DKCMAIN: 50-09-82-00/00
Universal Volume Manager
DKCMAIN
When the command, .pair split -g XXXX (variable) -d YYYY (variable),
was issued, invalid memory access occurred, and command was aborted
Low
The problem occurs when the following condition is met. When the
command, .pair split -g XXXX -d YYYY, is issued from RAID Manager,
the device name YYYY does not exist in the defined group XXXX.
RAID Manager: 01-23-03/06
RAID Manager: 01-23-03/07
Open
RAID Manager
LOGREC dataset full due to many error logs
With Withdraw with EXTENT issued to FCv2 pair using the Incremental
FCv2 function, an error was logged in the LOGREC dataset. With many
Withdraw commands issued, the LOGREC dataset exceeded its capacity.
Low
The problem occurs when Withdraw with EXTENT specified is issued to
an FCv2 pair using the Incremental FCv2 function.
DKCMAIN: 50-09-01-00/00 and higher
DKCMAIN: 50-09-82-00/00
Compatible Flash Copy V2
DKCMAIN
4 of 5
11
Phenomena
Severity (High, Medium, Low)
Conditions of Occurrence
Causes and Updates
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
Affected Products/Version
Fixed Product/Version
Category
Changed Part
HDS Confidential
Invalid error code at FC Establish execution
When FC Establish was executed with a PAV alias volume specified as a
target volume, the command was rejected with F/M=0x04 output instead
of F/M=0x0F and RC=0x64, which were output from the IBM storage.
Low
The problem occurs when FC Establish is executed with a PAV alias
volume specified as a target volume.
Microcode modified so that F/M=0x0F and RC=0x64 are output when the
command above is rejected, which is the same case as an IBM storage
DKCMAIN: 50-09-01-00/00 and higher
DKCMAIN: 50-09-82-00/00
Compatible Flash Copy V2
DKCMAIN
No display of synchronized CT group number
In Detailed Information dialog box, when Previous or Next button clicked
to display the information of a TC pair that belonged to the synchronized
CT group, the synchronized CT group number was not displayed.
Low
The problem occurs when the following condition is met. In the Detailed
Information dialog box, the Previous or Next button is clicked to switch
the displayed information from the details of a TC pair that does not
belong to synchronized CT group to the details of the pair that does
belong.
SVP: 50-09-74/00 and higher
SVP: 50-09-78/00
True Copy for z/OS or Open
SVP
HDD ports blockade at DKU un-installation
After DKU frame un-installation was completed, the maintenance window
showed that the DKU frame was in the uninstalled status. With this status,
when the FC cable between R1 and R2 was plugged off, the status became
Link Failure, and many HDD ports were blocked.
Medium
The problem occurs when all the following conditions are met.
1. FSW or DKP that connects to a DKU to be uninstalled is blocked
2. The DKU where HDD are mounted is uninstalled
3. The cable between this DKU and another DKU is plugged off
SVP: All
SVP: 50-09-78/00
SVP
SVP
5 of 5