9960

MICROCODE VERSION 01-19-99-00/08

RELEASED 9/28/2007
Newly supported features and functions for Version 01-19-99-00/08

NONE

The change of contents for Version 01-19-99-00/08

1 Suspend at earlier timing than time set with at Time

Phenomena The time to perform Suspend had been set with the At Time function. However, the Suspend
occurred earlier than the set time due to timeout with SSB=49d5 output.
Note if Suspend occurred according to the time set with At Time, SSB=49d3 was output.
Conditions The problem occurs with all the following conditions met.
1. TC Async for S/390
2. Set At Time with the YKSUSPEN command or Nanocopy
3. Wraparound occurs to the DKC internal timer of MP during the monitor for timeout between
when At Time is received and when the set time is passed. (One round takes approx. 9 hours.)
Category True Copy Async for S/390
Changed DKCMAIN

2 Unable to display PIN information from Maintenance with SSB=5480 output

Phenomena When a WR PIN existed, if displaying the PIN DETAIL from the Maintenance window, the DKC
could not show the PIN information with SSB=5480 output.
Conditions The problem occurs when trying to view the information of the PIN that occurs at the end of
VDEV or at the boundary of HDEV in the LUSE configuration.
Category Open or mainframe
Changed DKCMAIN

3 Failure of SNMP service startup or EC=3005 in response to Refresh request

Phenomena 1. SNMP start failed after SVP reboot due to error during initialization because the startup
operation did not end
2. In response to Refresh request of the SNMP service, the 3005 error Trap was always returned
Conditions The problem occurs when the result of the calculation, a-b, exceeds 4,096, where:
“a” represents the total number of the creatable Normal Volumes# of all the parity groups,
“b” represents the number of Normal Volumes actually mounted.
#: Not the number of Normal Volumes actually mounted, but the possible maximum number of
volumes to be mounted that is calculated from the size of a parity group.
Category SNMP
Changed SVP

HDS Confidential 1of 2

4 Unable to change settings of CVS
Phenomena After performing the following operation of Virtual LVI/LUN of from Remote Console, the
settings of CVS could not be changed:
-Install CV
-Volume To Space
-Make Volume
-Volume Initialize
Conditions The problem may occur with all the following conditions met.
1. The MIB Extent option of SNMP Agent has been set regardless whether an SNMP Agent option
exists.
2. From Remote Console, change the settings on LUNM, such as addition or deletion of a LU
path, or command device definition change
3. After #2, from Remote Console, change the settings of CVS, such as Install CV, Volume To
Space, Volume Initialize, or Make Volume
4. After #3, during the message saying the configuration change in progress being displayed, the
communication line for the Remote Console goes down due to a communication failure between
the Remote Console and devices, or a forced end of the Remote Console
5. After all the above steps, perform the CVS operation (Install CV/ Volume To Space/ Volume
Initialize/ Make Volume) from Remote Console, SVP, or SNMP Manager.
Category CVS
Changed SVP

5 When TC and SI share a volume, a data inconsistency occurs on TC S-VOL

Phenomena In such a configuration where a secondary volume (S-VOL) of True Copy-Sync (TC-Sync) and a
primary volume (P-VOL) of Shadow Image (SI) share the same volume, when a SI reverse copy
or quick restore operation is performed and then a TC pair resync is performed, a data
inconsistency may occur on the TC-Sync S-VOL.
Contents The micro-program has been modified to prevent the Reverse Copy or Quick Restore operation of
SI in the configuration where TC Sync/Async S-VOL and SI P-VOL share the same volume.

Note that in the above configuration, it is recommended to perform Swap-Resync of TC before

Reverse Copy of Quick Restore of SI. However, for the case when a pair operation on SI must
first be performed, system option mode 353 is available to cancel the prevention.

Public Mode - No Permission Required to Use

Conditions The phenomenon occurs when the following conditions A, B, C, and D are met.
A. Configuration in which a TC-Sync S-VOL and SI P-VOL are the same volume
B. Host write is not performed to the TC-Sync S-VOL
C. Host write is performed to the SI S-VOL
D. After C, a SI reverse copy or quick restore operation is performed, and then a TC-Sync pair
resync is performed (*1)

(*1) In the case of Swap-Resync that reverses the primary and secondary volumes of the TC-Sync
pair, the problem does not occur.
There is no point of performing a SI reverse copy/quick restore operation in condition D because
of overwritten data with TC P-VOL data. Therefore, the operation (condition D.) ends generally.

Category Shadow Image for S/390 or Open

Changed DKCMAIN

HDS Confidential 2of 2