Uspv & Uspvm MICROCODE VERSION 60-05-16-00/00 RELEASED 12/14/2009 Newly Supported Features and Functions For Version 60-05-16-00/00

USPV & USPVM
MICROCODE VERSION 60-05-16-00/00

RELEASED 12/14/2009
Newly supported features and functions for Version 60-05-16-00/00
1-1 Support for 400 GB Flash Drive (SSD)
Description Flash Drive (SSD) SDT2A-S400FC is supported as follows:
Storage model: USP V and USP VM
RAID level: RAID5(3D+1P,7D+1P(*1)),RAID1(2D+2D(*2)),RAID6(6D+2P)
Transfer speed: 2 Gbps/ 4 Gbps
*1: Two and four-parity group concatenations are supported.
*2: Two-parity group concatenation is supported.
Changed Part DKCMAIN, SVP, Config, Storage Navigator
1-2 Control update of configuration info during external volume disconnection

Description When disconnecting an external volume, as the status of progress is displayed on Storage
Navigator, the storage frequently receives updates of configuration information, which may
affect performance of host I/O operations for those other than the external volume to be
disconnected. By applying this micro-program, frequency of updates of configuration
information is reduced, which enables to avoid the effect on host I/O performance. In
addition, by setting System Option Mode 589 to ON, the update of configuration
information during disconnecting is completely stopped. This option is applied if an external
volume is disconnected while host I/O operations with severe performance requirement are
in progress. The default setting of the option is OFF.
Restricted Mode – RSD Permission Required to Use (within 60-05-xx range, Class = RSD)
Changed Part DKCMAIN, SVP, Config
2. Mainframe System
NONE
3. OPEN System
NONE
The change of contents for Version 60-05-16-00/00

1 I/O wait due to conflict between CU BUSY setting and host
Phenomena I/O waiting occurred when a journal I/O was issued.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
1. FICON
2. At the time of asynchronous processing start, CU BUSY setting
conflicts with a host I/O.
Causes and Updates System Option Mode 587 is available to fix this problem.
Restricted Mode - RSD Permission Required to Use.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-05-16-00/00
Category Mainframe
Changed Part DKCMAIN
HDS Confidential 1 of 11
2 SIM=7FF201 at Standby SVP reboot
Phenomena In a High Reliability Kit configuration, SIM=7FF201 occurred at the
time of rebooting of the Standby SVP.
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) SVP OS is Windows Vista.
(2) When DKC configuration is changed or during the scheduled
transfer performed once a day (at 13:00), the Standby SVP is rebooted.
(3) The default gateway address of "Local Area Connection" which is
for an external network of SVP is set.
Affected Products/Version SVP: 60-03-03/00 and higher
Fixed Product/Version SVP: 60-05-13/00
Category SVP
Changed Part SVP
3 Failure of Discovery of MSA Active/Standby device

Phenomena When Discovery was executed while a MSA is connected as an
external storage, the device might not be displayed.
Severity (High, Medium, Low) Medium
(1) Universal Volume Manager is used
(2) As an external storage, a MSA Active/Standby device is connected
(3) Discovery is performed
Note that the problem may not occur depending on the FW version of
MSA Active/Standby device.
Category Universal Volume Manager (Open)
4 Failure of SM capacity setting

Phenomena Although the customer wanted to increase SM capacity from the
Standard configuration (A) to a High Performance configuration (C)
below without SM de-installation, it couldn't be done due to the
operating restriction of SVP.
(A) 2x SM PCB. 8x 1GB DIMM installed in each PCB. (Standard)
(B) 2x SM PCB. 6x 1GB DIMM installed in each PCB. (Standard)
(C) 4x SM PCB. 6x 1GB DIMM installed in PCB. (High Performance)
According to the present specification, the Configuration cannot be
changed directly from (A) to (C) without passing through (B) above.
Conditions of Occurrence The phenomenon occurs when all the following conditions are met.
(1) The SM is in a Standard configuration.
(2) High Performance configuration for SM configuration change
(3) SM capacity per PCB PK will decrease, from 8GB/PK to 6GB/PK
for example
Affected Products/Version SVP: All
Category Shared Memory
Changed Part SVP
5 Suspended URz pair with EC=48E4
Phenomena In URz delta re-sync configuration, and an operation to create/delete
relations of FCv2 was executed, UR pair suspended with EC=48E4
(1) UR for z/OS delta re-sync configuration.
(2) A writer operation across multiple records.
Affected Products/Version DKCMAIN: 60-02-25-00/00 and higher
Category Universal Replicator for z/OS
6 E-mail cannot be sent during E-mail notification test

Phenomena As the connection to SMTP was not established during E-mail
notification, mails could not be sent.
(1) A mailer which regards blank as an error (Exchange Server 2003,
for example) is used as SMTP server.
(2) Test sending of e-mail notification from SVP is performed
Affected Products/Version SVP: 60-04-07/00 and higher
Category SVP
Changed Part SVP
7 CHA WCHK1 after UR pair creation

Phenomena After UR pair creation following the registration of a JNL VOL of 1
GB or less in a JNL group, an error, EC=1470, occurred on RCU side,
resulting in occurrence of WCHK1.
(1) UR for z/OS or Open.
(2) The capacity of JNL VOL is 1 GB or less.
Category Universal Replicator for z/OS or Open
8 Failed to report SIM due to SVP power off

Phenomena A SIM was not reported.
Conditions of Occurrence The problem occurs when the power of SVP is turned off while a SIM
is being reported.
Category Open or mainframe
Changed Part SVP
9 Incorrect output of warning SIM and SSB
Phenomena When a UR pair was created while setting the JNL VOL capacity of
the JNL group on RCU side to 9 GB, warning SIM and SSB, which
indicate that the metadata area of the JNL VOL on RCU side is full,
were wrongly output.
(2) The capacity of JNL VOL is less than 9 GB.
10 Delay in SIM reporting

Phenomena SIM reporting was delayed due to falling into wait state.
(1) Multiple SIM exist.
(2) While above SIM are created and reported (around two minutes),
SIM Log Complete is manually executed for one SIM.
(3) A reply from the message task of another uncompleted SIM other
than the one in (2) is received.
Changed Part SVP
11 Accumulation of residual transactions due to response delay

Phenomena Due to delay in response while accessing to a device, residual
transactions were accumulated. According to RMF, the DP BUSY
value became high. All the eight paths being used indicated the same
tendency.
(1) Mainframe environment.
(2) Multiple hosts are connected.
(3) A reserved device was recognized as "Device Busy" on a host.
Even though the reserved device is released and then the device returns
"Device Free" as a response, there is still no access from the host to
which "Device Busy" was reported.
(4) A status change report, DSB=0x85, occurs on the device.
Category Mainframe
12 Incorrect display of pair volume attribute

Phenomena In a configuration where multiple R-JNL groups were registered in a
copy group, when PERMIT option suspend was executed, some pair
volumes with PROTECT attribute were displayed. (There was
Read/Write operation right to the pair volumes. Only the window
display was incorrect)
(1) Universal Replicator for z/OS.
(2) Two or more R-JNLgroups are registered in a copy group
(ExCTG).
(3) Within the ExCTG, PERMIT option (write operation to S-VOL is
allowed) suspend is executed.

13 MIH during FCv2 copy

Phenomena After creating FCv2 pairs (NOCOPY mode) in the same volume in the
overloaded state, when a volume copy operation from the volume to
another was executed, MIH might occur.
(1) FCv2 pairs whose source LDEV (S-VOL) and target LDEV (T-
VOL) are in the same volume.
(2) S-VOL: T-VOL = 1: n (One S-VOL is paired with multiple T-
VOL).
(3) Read I/O is issued to an un-copied area on T-VOL.
(4) Overloaded state.
Category Flash Copy version 2
14 Failure suspend resulted from ABEND of copy processing

Phenomena During copy processing of Shadow Image for z/OS, SSB=13FA was
output and then the processing ended abnormally. Eventually, the
pair(s) was suspended due to the failure.
Conditions of Occurrence The problem occurs when an inconsistency in the management
information on the LM is detected during the directory research
processing.
15 Blockade of all DKA on CL2 side due to DRR error

Phenomena When a parity group was installed, all DKA on CL2 side were blocked
due to a DRR error.
(1) A reboot command is issued from SVP to DKP due to parity group
installation.
(2) Then SVP is busy because Hi-Track is trying to acquire the config
information repeatedly, for example. Thus, both receiving the reboot
command by DKCMAIN (DKP) and starting MP reboot delay
unexpectedly.
(3) IMPL Status, with SM information showing MP recovery status, is
still rebooting, even after the 4 seconds timer has passed.
SVP: All
SVP: 60-05-13/00
Changed Part DKCMAIN, SVP
16 Incorrect display of pool usage rate

Phenomena When the pool threshold was changed, the pool usage rate was
displayed fewer than the actual figure.
(1) Pool threshold (variable threshold) is changed.
(2) The operation in (1) results in the status that the fixed threshold
(80%) < pool usage rate < variable threshold after the change.
Category Dynamic Provisioning
17 Unrecovered external storage path

Phenomena When a CHT PCB was replaced about 3 days after blockade of an
external storage path resulted from WCHK1 occurred (hardware-
caused) in the CHT PCB, the external storage path could not be
recovered.
The external path was recovered by dummy replacement.
(1) WCHK1 occurs at an MP where an external storage path is
connected.
(2) The MP where the failure has occurred is replaced within a time
period of odd-multiples of 73 hours to 146 hours after the failure has
occurred.
Category Open
18 Performance deterioration during a UR Re-sync operation

Phenomena During a UR Re-sync operation, host I/O response time increased.
(1) Universal Replicator for z/OS or Open is used.
(2) A Re-sync operation is executed.
(3) Host I/Os are issued.
Causes and Updates New System Option Mode 760 is available to fix the problem.
Restricted Mode – RSD Permission Required to Use
19 Occurrence of WCHK1 due to EDC error or SSB output

Phenomena When a Read I/O was issued to CoW Snapshot S-VOL, SI S-VOL of
DP-VOL, or CoW Snapshot P-VOL of DP-VOL,
(1) WCHK1 occurred due to EDC error.
(2) SSB=0xD370, 0x147B, or 0xD3F9 were output. (Log only)
Conditions of Occurrence The phenomenon (1) or (2) may occur in any case of (1), (2) or (3).
(1) All the following conditions (a) to (f) are met.
(a) DP-VOL
(b) SI S-VOL
(c) The SI pair is in PSUS/SP status
(d) Read I/O over multiple LDEV (transfer length > 256 kb) is issued
(e) Transfer range where DP page is unallocated (An area to which
Write I/O is not issued)
(f) Transfer range where differential data is un-copied (At the time of
copy processing initiation when I/O is issued)
(2) All the following conditions (g) to (j) are met.
(g) CoW Snapshot S-VOL
(h) The CoW Snapshot pair is in PSUS status
(i) Read I/O over multiple LDEV (transfer length > 256 kb) is issued
(j) At the same time when (i) is performed, a Write I/O is issued to a
CoW Snapshot P-VOL or S-VOL
(3) All the following conditions (k) to (p) are met.
(k) DP-VOL
(l) CoW Snapshot P-VOL
(m) The CoW Snapshot pair is in restoring state
(n) Read I/O over multiple LDEV (transfer length > 256 kb) is issued
(o) Transfer range where DP page is unallocated (An area to which
Write I/O is not issued)
(p) Transfer range where differential data is un-copied (At the time of
copy processing initiation when I/O is issued)
Category Dynamic Provisioning, Copy-on-Write Snapshot
20 Report of SSB=98D2 during background copy of FCv2

Phenomena During background copy of FCv2, SSB=98D2 might be reported.
The only impact was the SSB output.
(1) HDD emulation type is 3390-M.
(2) RAID level is RAID1 (2D+2D).
(3) FCv2 copy operation is performed.
Category Flash Copy Version 2
21 Failed command device creation for external volume

Phenomena Creation of a command device for an external volume which had been
mapped by Universal Volume Manager failed.
(1) A mainframe command device definition operation is performed
from Business Continuity Manager.
(2) The volume to be defined is an external volume which has been
mapped by Universal Volume Manager.
Category Shadow Image for z/OS, True Copy for z/OS, True Copy
Asynchronous for z/OS, Universal Replicator for z/OS
22 Failure of Delta Re-sync operation

Phenomena After releasing Remote Command Devices, a Delta Re-sync operation
might fail.
(2) There are 2 or more Delta Re-sync configurations using Remote
Command Devices.
(3) At a DKC site where a TC S-VOL exists in any of the Delta Re-
sync configurations above (2), a release operation of a Remote
Command Device is executed.
(4) At the site above (3), a Delta Re-sync operation is performed for
another Delta Re-sync configuration where the release operation is not
executed.
Category Universal Replicator for Open or z/OS
23 Occurrence of Suspend (EC SSB=C683)

Phenomena Under the condition of URz Delta configuration and Pending-Duplex
status, Suspend (EC SSB=C683) occurred due to difference in the copy
area between TCz (Sync) and URz.
(1) TC (Sync) for z/OS - UR for z/OS Delta configuration.
(2) The status of the URz pair changes from Suspend to Pending-
Duplex.
(3) A retry occurs during Write command chain processing over
multiple records.
Affected Products/Version DKCMAIN: 60-05-06 and higher
24 SIM output indicating journal volume full

Phenomena In a 3DC delta configuration, a SIM was issued six times in a few
seconds indicating a warning of journal volume full.
(1) True Copy - Universal Replicator (Both z/OS) in 3DC delta
(2) Pair of Universal Replicator for z/OS is suspending (Dummy JNCB
is being created).
25 Failed to report Batteries and DKUPS errors

Phenomena SIM of the DKUPS’ “PS Warning” and Batteries’ “BATT Warning”
cannot be reported if components are located in DKU-R1 or L1.
Severity (High, Medium, Low) High
Conditions of Occurrence This problem occurs when A and B or C occur.
A. USP V only (DKCMAIN Ver.: 60-03-03-00/00 and higher).
B. Case of DKU-R1:
- A breakdown of DKUPS-xx2 or DKUPS-xx3
- A breakdown of one of BATTRY-Uxx4 and Uxx5, Uxx6, and Uxx7
C. Case of DKU-L1:
- A breakdown of one of DKUPS-xx0, xx1, xx2, and xx3
- A breakdown of one of BATTRY-Uxx0, Uxx1, Uxx2, Uxx3, Uxx4,
Uxx5, Uxx6, and Uxx7
Causes and Updates DKU environmental monitor can indicate “PS Warning” and “BATT
Warning”; however SIMRC is not reported due to micro-program bug.
Category DKU
26 Data inconsistency after FastReverseRestore of FCv2

Phenomena Phenomenon A, described below, may occur with storage that uses
Flash Copy Version2 (FCv2). In addition Phenomenon B may occur
with the occurrence of Phenomenon A.
Phenomenon A:
Data inconsistency occurs (*1) in an FCv2 target volume (T-VOL).
(Data inconsistency in the Data part of Record 0). When accessing T-
VOL (VOL A) of FCv2 which performed FastReverseRestore (FRR)
(*2), the following phenomena occur.
- In the case where FRR is performed after the source volume (S-VOL)
(VOL A) data is updated, when reading the R0 data of T-VOL(VOL
A), the old data before updated should be read, but the updated data is
read instead.
- In the case where FRR is performed after the T-VOL (VOL B) data is
updated, when reading the R0 data of T-VOL (VOL A), the updated
data should be read, but the old data before updated is read instead.
Phenomenon B. During access to the FCv2 T-VOL, the phenomena

such as No Record Found, invalid record length, and track overrun
occur.
(*1) Range where data inconsistency occurs:
in case of 3390-series drive simulation, 3712 cylinder or higher
in case of 3380-series drive simulation, 3072 cylinder or higher
(*2) FRR reverses the original S-VOL and T-VOL, and copies from S-
VOL to the T-VOL only the data where were updated.
Conditions of Occurrence When all the following conditions are met, the failure may occur.
A. RAID600: 60-03-24-00/00 or higher
B. If 3390-series volume emulation, 3390-9 or larger size emulation
(more than 3712 cylinders) If 3380-series volume emulation, 3380-3
(more than 3072 cylinders)
C. In case of 3390-series volume emulation, update the data of 3712
cylinder or higher. (*3) In case of 3380-series volume emulation,
update the data of 3072 cylinder or higher. (*3)
D. Operating FRR with Incremental(NO) option
(*3)Additional information:
Dataset formatted like DAM or ISAM, job executed to update Record
0, such as restore job or dataset creation (FMTWR including Record 0)
Causes and Updates In the processing of FRR function of FCv2, the micro program judges
it is unnecessary to copy the updated R0 data which are below-
mentioned cylinder or higher. Therefore, after the relationship of FCv2
has reversed by the FRR operation, the copy of the updated R0 data
from S-VOL (VOL B) to T-VOL (VOL A) is not executed.
Category Flash Copy Version2
27 Data inconsistency in S-VOL After suspension

Phenomena When Business Continuity Manager (hereinafter referred to as BCM)
is installed in the host environment in which the time-stamping
function is installed, and if a Flush suspension for an extended
consistency group (hereinafter referred to as EXCTG) is performed
from BCM in the EXCTG configuration of Universal Replicator
(Mainframe), data may not be reflected to the secondary volume of
Universal Replicator. As a result, there is a possibility that the user who
backs up data on the secondary volume of Universal Replicator by
using Shadow Image etc. could not back up the data at the intended
time.
Conditions of Occurrence When all the following conditions A to E are met, the phenomenon
may occur.
A. Ver.60-02-04-00/00 and later
B. Universal Replicator
C. Mainframe
D. EXCTG configuration
E. Flush suspension for EXCTG
F. BCM is installed in the environment in which the time-stamping
function is installed.
(If there are multiple hosts, the system in which the SYSPLEX timer is
enabled)
Causes and Updates Flush suspension for an EXCTG configuration must regularize all
write data received in the EXCTG before the suspension in RCU. To
settle data, the time stamp assigned to the latest write command
received in the EXCTG needs to be used. Due to a microcode bug,
however, the data was settled with the last time stamp received in the
journal group that performed Flush suspension. As a result, data of host
I/O received in the EXCTG after the last time stamp received in the
journal group that performed Flush suspension was not settled in RCU.
New System Option Mode 762 is available to fix the problem.
Restricted Mode – RSD Permission Required to Use
Category Universal Replicator for z/OS, 3DC Extension

Uspv & Uspvm MICROCODE VERSION 60-05-16-00/00 RELEASED 12/14/2009 Newly Supported Features and Functions For Version 60-05-16-00/00

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Uspv & Uspvm MICROCODE VERSION 60-05-16-00/00 RELEASED 12/14/2009 Newly Supported Features and Functions For Version 60-05-16-00/00

Uploaded by

Copyright:

Available Formats

USPV & USPVM

MICROCODE VERSION 60-05-16-00/00

1-2 Control update of configuration info during external volume disconnection

The change of contents for Version 60-05-16-00/00

3 Failure of Discovery of MSA Active/Standby device

4 Failure of SM capacity setting

6 E-mail cannot be sent during E-mail notification test

7 CHA WCHK1 after UR pair creation

8 Failed to report SIM due to SVP power off

10 Delay in SIM reporting

11 Accumulation of residual transactions due to response delay

12 Incorrect display of pair volume attribute

Affected Products/Version DKCMAIN: 60-02-04-00/00 and higher

13 MIH during FCv2 copy

14 Failure suspend resulted from ABEND of copy processing

15 Blockade of all DKA on CL2 side due to DRR error

16 Incorrect display of pool usage rate

17 Unrecovered external storage path

18 Performance deterioration during a UR Re-sync operation

19 Occurrence of WCHK1 due to EDC error or SSB output

20 Report of SSB=98D2 during background copy of FCv2

21 Failed command device creation for external volume

22 Failure of Delta Re-sync operation

23 Occurrence of Suspend (EC SSB=C683)

24 SIM output indicating journal volume full

25 Failed to report Batteries and DKUPS errors

26 Data inconsistency after FastReverseRestore of FCv2

Phenomenon B. During access to the FCv2 T-VOL, the phenomena

27 Data inconsistency in S-VOL After suspension

You might also like