Uspv 60-01-44-00-00

USPV
MICROCODE VERSION 60-01-44-00/00

RELEASED 07/06/2007
Newly supported features and functions for Version 60-01-44-00/00

1. Mainframe & OPEN System
1-1 DKS2E-K support
Description The following 15krpm type of DKS2E are supported:
1. DKS2E-K72FC: The below shows the equivalent types in supported RAID level,
emulation, and the number of settable LDEV and these types are compatible among each
other. DKS2D-K72FC, DKR2F-K72FC
2. DKS2E-K146FC: The below shows the equivalent types in supported RAID level,
emulation, and the number of settable LDEV and these types are compatible among each
other. DKS2D-K146FC, DKR2F-K146FC
3. DKS2E-K300FC: The below shows equivalent types in supported RAID level, emulation,
and the number of settable LDEV and these types are not compatible among each other
because the rotation speed differs among each other. DKR2F-J300FC, DKS2D-J300FC
Changed Part HDD
1-2 Support for the alternate path configuration using different clusters of DS4800
Description Alternate path configuration using different clusters on IBM DS4800 now supported.
Setting port parameter (host type) of DS4800 to “Linux” is required to enable the function.
Changed Part DKCMAIN
1-3 RAID500 Support for TC/ TC for z/OS/ UR/ UR for z/OS
Description The RAID600 has supported the following connections with the RAID500:
True Copy connection with the RAID500
True Copy for z/OS connection with the RAID500
Universal Replicator connection with the RAID500
Universal Replicator for z/OS with the RAID500
Function only available for RAID500 with DKCMAIN version 50-09-15-00/00 and higher.
1-4 Support for TC/ TC for z/OS Migration from RAID450/RAID500

Description The RAID600 has supported the migration function of True Copy/ True Copy for z/OS
(Async) performed from the RAID450/RAID500.
The supported DKCMAIN versions for RAID500 is 50-09-15-00/00 and higher.
The supported DKCMAIN versions for RAID450 is 21-14-36-00/00 and higher.
For the specification about the migration function in detail, please refer to Apx-
ao_TCA_Migration_Spec.xls.
HDS Confidential 1 of 28
2. Mainframe System
2-1 UR for z/OS 3DC Multi Target Support
Description RAID600 supports the 3DC Multi Target connection of TC for z/OS and UR for z/OS.
RAID600 has also supported the 3DC Multi Target connection of TC for z/OS and UR for
z/OS with the RAID500.
Function only available for RAID500 with DKCMAIN version 50-09-15-00/00 and higher.
3. OPEN System
3-1 RAID Manager 01-20-03/06
Description RAID Manager updated as follows:
- Supported the maximum values for RAID600
- Support LDKC per 64K LDEV
- Supported the option to display HDP information
- Added "-v aou" option for the raidvchkscan command
- Added "-v aou" option for the raidvchkdsp command
- Added "-v pida" option for the raidvchkscan command
- Added the identification for HDP to the inqraid command
- Supported "-pin" option for displaying PIN volumes to the inqraid command
- Changed behavior of the horc command
- Horctakeover command performs PVOL_takeover under condition
(MINAP=0) on Link-failure.
- Pairsplit command performs "-P" option using the purge for HORC_Async/UR.
- Supported command option for awaking delayed I/O for dismounting on Windows2003
- -x syncd, -x umountd, raidscan -find syncd
- Supported RAID Manager communication between 32bits and 64bits HORCM
- Supported "RM Shadow Copy provider(01-03-03/02)" using TC with HPtM
- Added two securities for raidcfg command, and avoided a problem that
"raidcfg -a set -o hgrp" bring on EX_CMDIOE
Changed Part RAID Manager
The change of contents for Version 60-01-44-00/00

1 CMDREJ FM=04, EC=47a6 at ESTPAIR (Failback) issued to
TC P-VOL
Phenomena After ESTPAIR (Failover) had been issued to the S-VOL of TC, if
ESTPAIR (Failback) was issued to the P-VOL of TC, the processing
ended abnormally and CMDREJ FM=04, EC=47a6 was reported.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Problem may occur with all the following conditions met.
1. True Copy for z/OS
2. After issuing ESTPAIR (Failover) to TC S-VOL, issue ESTPAIR
(Failback) to TC P-VOL.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 60-01-44-00/00
Category True Copy for z/OS
2 Inappropriate error message for EXG allocation failure
Phenomena 1. At the execution of ADD VOLUME with the maximum number of V-
VOL used, EXG# was allocated from the window for EXG# allocation,
however, the CU: LDEV setting window showed "0-0" for the allocated
EXG.
2. After #1, allocated CU: LDEV# (ADD VOLUME mapping), and then
returned to the previous window that showed "-" for the EXG#. In that
case, clicking the OK button displayed the message saying no parameter
was set.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem #1 occurs when all of the following operations are
performed with the Volume Operation window showing that the number
of external volumes has reached the limit:
1. Add volumes manually.
2. Enter ExG# in the window for setting an external volume parameter.
3. Click OK.
The problem #2 occurs when after performing #1; click OK in the volume
addition window.
Causes and Updates Microcode modified so that an error message showing EXG setting
failure will be displayed for problem #1, and the error message for
problem #2 will indicate the reason for the parameter setting.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 60-01-44/00
Category Universal Volume Manager
Changed Part SVP
3 TC pair suspend at replacement of CHT during I/O

Phenomena While issuing an I/O to a TC pair, if the host-targeted CHT was replaced,
the TC pair was suspended.
Conditions of Occurrence The problem occurs when replacing the host-targeted CHT during an I/O.
Category True Copy for Open
4 SSB log (EC=549e) about atomic lock processing at SCSI reset

Phenomena SCSI was reset, the SSB log (EC=549e) was inappropriately reported,
saying that atomic lock acquisition processing took more than 400 ms.
Conditions of Occurrence Problem occurs with all the following conditions met.
1. An I/O from an open host is being processed.
2. SCSI reset occurs due to an I/O failure.
3. Along with I/O processing, any asynchronous processing (SM or CM
maintenance, etc.) is in progress within the DKC.
Category Open
5 SSB=D310 caused by reset command issued from RCU to MCU
Phenomena In UR for open or z/OS, if the MCU received the reset command from the
RCU since the processing on the MCU failed due to overload or any
failure, SSB=D310 was reported.
1. UR for open or z/OS
2. RCU issues the reset command to MCU where processing fails due to
overload or any failure.
Category Universal Replicator for Open or z/OS
6 UR Reverse Resync failure

Phenomena After a UR pair creation, path between P-VOL and S-VOL disabled, and
then horctakeover performed to S-VOL. After that, when performing
Reverse Resync immediately after re-enabling the path, the normal result
was returned to RAID Manager, but the pair state remained unchanged.
1. UR for Open
2. After disabling the path between MCU and RCU, issue the
horctakeover command to the S-VOL from RAID Manger
3. After re-enabling the path, perform Reverser sync with the JNL group
state in Active for MCU and in Stop for RCU
Affected Products/Version DKCMAIN: 60-01-30-00/00 and higher
Category Universal Replicator for Open
7 Error message after executing Disconnect Volume command

Phenomena While executing de-stages processing with the Disconnect Volume or
Disconnect Subsystem command, if the same command was issued again,
error message 605-8122 was in some cases reported, indicating the
logical volume was busy.
Conditions of Occurrence Problem may occur with the following condition #1& #2, or #1&#3 met.
1. UVM is in use
2. Execute the Disconnect Volume or Disconnect Subsystem command to
32,768 or more external volumes
3. Execute the Disconnect Volume or Disconnect Subsystem command to
an external volume, and execute either of the two commands to another
external device before the de-staging completed
Causes and Updates Microcode modified so that error message 605-58332 (The external
volume is blocked.) will be reported in this case.
8 Improper status of external device during Cache De-stage
Phenomena After executing Disconnect Volume or Disconnect Subsystem, if the
micro-program exchanged during Cache De-stage, the external device
showed in normal state even though the device had not yet completed
Disconnect.
Conditions of Occurrence The problem may occur with the condition both #1 and #2 met and any of
the following condition #3 or #4 or #5 met.
1. Use external devices.
2. After executing the Disconnect Volume or Disconnect Subsystem
command to external devices, some external devices, on which the
command has not completed, are in the process of Cache De-stage.
3. Perform micro-program exchange.
4. Perform PCB exchange.
5. Recovery from a MP failure
DKCMAIN: 60-01-30-00/00 and higher
Affected Products/Version
9 No support for external volume of minimum size

Phenomena An external volume of the minimum capacity (77,760 blocks) recognized
as an unsupported device.
Conditions of Occurrence The problem occurs with all of the following conditions met.
1. Use UVM.
2. The number of blocks of an external volume on an external storage is
77,760.
3. Perform Discovery for the external storage.
10 Improper maximum percentage value on the Y-axis

Phenomena In the usage window of TC, TC for z/OS, UR, or UR for z/OS, a graph
displayed the percentage value of "120" on the Y-axis.
1. In the usage window of TC, TC for z/OS, UR, or UR for z/OS
2. A graph with percentage values displayed
3. All the data displayed reach 100%
Causes and Updates The maximum scale mark of the Y-axis is set to 100.
Category True Copy for Open or z/OS, Universal Replicator for Open or z/OS
Changed Part SVP
11 Data transfer failure with SSB=b6d8 reported

Phenomena At the time of a data (parameter) transfer failure, SSB=b6d8 was
reported, indicating the double send of a status. This did not affect the
subsequent operation because the status sent only once although the SSB
reported twice.
Conditions of Occurrence The problem may occur when the data (parameter) transfer with the
PersistentReserveOUT command fails.
Category Open
12 CHK2 during cache replacement

Phenomena When issuing a Write I/O during Cache replacement, SSB=13fe was
reported and then CHK2 occurred.
Conditions of Occurrence The problem may occur with all of the following conditions met.
1. During Cache replacement
2. Open-V
3. Same MP issues multiple Write I/Os at the same time to the same slot
4. Highly loaded I/O
Category Open
13 No emulation type available for adding external volumes

Phenomena When performing Add Volume on the device with mainframe PCB not
installed and the capacity of an external volume was between 77,760 and
83,519 LBA, no emulation types was available for the operation, and
therefore no add volume occurred.
1. No mainframe PCB installed.
2. Perform Add Volume.
3. The capacity of an external volume is between 77,760 and 83,519
LBA.
Causes and Updates Microcode modified so that the external volume whose emulation type
does not exist will not display on Add Volume window.
Changed Part SVP
14 SCSI commands abnormal end

Phenomena When adding or deleting SCSI path definition, the following commands
failed.
1. PGR-OUT command
i. Key Clear failed, or the Key of other LU was cleared
ii. Key Preempt failed, or the Key of other LU was preempted
iii. Reservation Released U.A was not reported, or reported twice, or
reported to a non-intended initiator
2. PRG-IN command
i. The registered Key was not reported by Read key, or the same Key
was reported twice, or a Key other than the intended Key for the LU was
reported
3. Normal Reserve command

i. If PGR Key had been registered, Reserve ended normally
ii. If PGR Key not registered in the LU and Conflict returned
4. Normal Release command

i. If PGR Key had been registered, Good was returned
ii. If PGR Key not registered, Conflict returned
5. E5 command
i. If PGR Key had been registered, Reserve ended normally
ii. If PGR Key had not been registered in the LU, Conflict was returned
iii. E5 U.A was not reported, or reported twice, or reported to a non-
intended initiator
6. Set Device Identifier command
i. SDI U.A was not reported, or reported twice, or reported to a non-
intended initiator
1. Multiple ports share a device.
2. During SCSI path addition or deletion at another port, any of the
following commands is received:
- PGR-OUT command S.A=Register, Release, Clear, Preempt,
Preempt&Abort, Register&Ignore
- PGR-IN command S.A=Read Key
- Normal Reserve command
- Normal Release command
- E5 command
- Set Device Identifier command
Category Open
15 PIN slot after releasing HDP association

Phenomena When formatting an HDP volume, the de-staged dirty volume remained
invalidly. In that case, when releasing the association, the PIN slot
generated in the POOL volume.
1. An HDP volume whose volume size is not a multiple of 86,016 blocks
exists.
2. Data written throughout the volume
3. Release the association after formatting the volume
The cache replacement operation can release the PIN slot. The data itself
not affected because it formatted.
Category Dynamic Provisioning
16 Ping error at LAN CHECK

Phenomena If LAN CHECK performed with "ALL MP" selected, the Ping error
occurred.
Conditions of Occurrence The problem occurs when performing LAN CHECK with "ALL MP"
selected.
Category SVP
Changed Part SVP
17 Duplicate FSW list shown at PDEV un-installation failure

Phenomena PDEV un-installation fails, a dialog window may appear asking users to
replace FSW. In that case, dialog window shown duplicate FSW list.
1. Uninstall PDEV and DKU, or uninstall PDEV until the number of
PDEV in the dialog window becomes 0.
2. Un-installation fails due to FSW or HBC cable failure.
Category Un-installation
Changed Part SVP
18 Unable to add Pool due to hardware failure

Phenomena Unable to add to Pool
The problem occurs when a hardware failure (CHK1 or CHK3) occurs
Conditions of Occurrence
while creating the pool of COW or HDP.
Category Dynamic Provisioning for Open
19 Pair suspend after MCU power cycle during TC initial copy

When performing an MCU planned power cycle during the initial copy of
Phenomena
TC Sync, failure suspend occurs to several tens of the pairs.
1. True Copy Sync or Async
2. True Copy for open or z/OS
3. When pairs are in Pending state and either the following is performed:
- MCU planned power cycle
- MCU PS Off and then non-volatile PS On (for Sync only)
Category True Copy for Open or z/OS
20 Performance degradation due to failure staging CR setting area

During the pre-staging operation, data not staged to the intended CR
setting area, and Disconnect Time occurred when accessed from the host
Phenomena
for the first time after the pre-staging. The performance obtained was
lower than expected.
Problem occurs with all the following conditions met.
1. Activate the pre-staging processing after changing the CR setting
through any of the following: SVP, Storage Navigator, Define
Configuration, HDEV un-installation, or the CMG utility.
2. Between a CR setting change in #1 and activation of pre-staging, LM
configuration information not updated periodically.
Category Cache Residency Manager (Pre-staging)
Unable to PS OFF during Quick Restore of SI or Volume

21
Migration operation
While executing Quick Restore of Shadow Image or Volume Migration,
Phenomena
the planned PS OFF of the RAID600 was not available.
1. Execute Quick Restore or Volume Manager of Shadow Image.
2. Turn the power supply off at the phase immediately before the copy
operation is completed.
Category Shadow Image for Open and z/OS
22 ABEND when issuing I/O to unequal-length track of TCZ pair

When issuing an I/O to an unequal-length track of True Copy for z/OS,
Phenomena
the operation ended abnormally with EC=c662 reported.
1. True Copy for z/OS pair
2. Issue the Write Track Data command to an unequal-length track.
3. The data length of the last write record differs from that of the next
record.
23 SLPR remained in Not Enough state

When ECC group moved, and as a result, the used capacity of SLPR
exceeded the licensed capacity, SLPR became in the Capacity Insufficient
Phenomena (30 days) state. Then, when the available period of this state expired, the
state turned to Not Enough. After that, even if the ECC group was
deleted, the "Not Enough" state remained unchanged.
Conditions of Occurrence 1. SLPR is in Not Enough state.
2. Delete an ECC group.
Category SVP
Changed Part SVP
24 Many SIM indicating SLPR expiration

When using a PP that uses SLPR, if the Emergency or Temporary key
Phenomena expired, many SIM indicating the key expiration generated (186 SIM in
this case).
1. Use a PP that uses SLPR
2. The key type, Permanent or Term, is defined in SLPR.
3. Any of the following conditions met according to the type of the key.
Conditions of Occurrence If the key type is
- Emergency or Temporary, the key has expired.
- Permanent, the SLPR Insufficient state has expired.
- Term, the Term period has expired, or the SLPR Insufficient state has
expired.
Category SVP
Changed Part SVP
25 Improper child PP status at Term expiration

When two PP have relationship that one PP must install first (A) to install
Phenomena the other PP (B), and the Term of the both PP expired at the same time, PP
(B) became in the Not Enough state.
1. Two PP are in the relationship that one PP must install first to install the
other PP.
2. Both of the PP expires on the same day.
3. The key type of the PP that installed after the first one is Term.
Category SVP
Changed Part SVP
Storage Navigator start failure after SVP micro-program

26
exchange
After installing the SVP of 60-01-21 version, starting Storage Navigator
Phenomena ends abnormally with SSB=3332 reported. This problem repeatedly
occurred.
1. The Performance Monitor switch of Storage Navigator is ON.
2. Under the condition #1, perform SVP micro-program exchange as
follows:
from: between 60-00-06/00 and 60-00-21/00
to: 60-00-22/00 or later
Category JAVA, Storage Navigator
Changed Part SVP
27 PCB location listed in improper order in Dump window

The DUMP window listed the PCB locations, by selecting the Select
Phenomena Adapter radio button, in the alphabetical order, not in the order of PCB
installation.
The problem occurs when selecting the "Dump" from Auto Dump, and
then, in the Dump window, selecting the Select Adapter radio button.
Category SVP
Changed Part SVP
Improper name of monitoring item displayed in monitoring

28
window
At regular monitoring of R600 SVP, although the Cache Async RCU Side
Phenomena File Rate item showed 1%, the Cache Side File Rate item remained
showing 0%.
The problem may occur when selecting Cache Side File Rate to display
from the SVP monitoring window.
Microcode modified to change the title of the monitor as follows.
Causes and Updates Old title: "Cache Side File Rate"
New title: "Cache MCU Side File Rate"
Category SVP
Changed Part SVP
29 No color indication for expired PP license

After the license key of Term expired, the window of Storage Navigator
started. In that case, the icons representing their function were not grayed
Phenomena
out. The Refresh operation was required to make the icons to be grayed
out, but the message for the operation did not appear.
Conditions of Occurrence 1. The PP license has expired.
2. Open Storage Navigator to display the menu
Category SVP
Changed Part SVP
30 Intervention requested at link down during I/O

When setting Volume Security, the link wends down during an I/O and an
Phenomena
intervention was requested.
The problem may occur when all of the following conditions are met.
Conditions of Occurrence 1. Perform Volume Security setting
2. During an I/O, the link went down caused by plugging off/in the cable.
Category Mainframe
31 Conflicted hash value resulting in performance decrease

When the DP performance is measured in the environment that 32 DP-
VOL of 268 Gbyte each was used, the internal hash of DKC was
unevenly used, thus hash value conflicted 32 times in the average, up to
Phenomena
64 times. Those conflicts decreased the operation performance to 8
microseconds per host I/O, which usually took more or less than 1
microsecond.
Conditions of Occurrence 1. DP-VOL
2. Define 2 or more DP-VOL of 2.625 or more GB each
Category Open
Improper interval time period of monitoring and value

32
displayed
When 65 or more CUs to be monitored were set, the interval of
monitoring was enabled to less than 5 minutes, which is invalid. In that
case, the following phenomena occurred:
Phenomena - Performance Monitor operated with a less-than-5-minute interval.
- Some monitored data by Performance Monitor might drop.
- The displayed interval value did not match between the Performance
Management window and Monitoring Options window.
1. Set 65 or more CUs to be monitored with the SW ON.
2. Perform the following operation from #1) through #4):
1) In the Monitoring Options window, set 64 or less CUs to be
monitored (displayed in blue)
2) Click the Cancel button
3) Set the interval to between 1 and 4 minutes in the combo box.
4) Click the Apply button.
Changed Part SVP
33 Response degradation during sequential overwrite I/Os

During sequential overwrite I/Os, WAIT occurred at track switching and
Phenomena the response performance degraded with DISC TIME of several ms
increased.
The problem occurs when sequential overwrite I/Os that generate track
switching exist.
Category Mainframe
34 EIO de-staging delay

CM replacement took 3 hours since urgent de-stage to an external volume
Phenomena
took longer time.
The problem may occur when performing any of the following
maintenance operations in the configuration that includes external
volumes:
1. CM or SM replacement
2. Power cycle
3.Execute Disconnect to an external volume
35 PPRC command failure for changing port attribute
With the Mode 114 set to On, when creating a path to a port with the
Phenomena RCU Target attribute by using the PPRC command, the path creation
failed with SSB EC=B101 reported.
Problem may occur with all the following conditions met.
2. Create a path to a port with the RCU Target attribute by using the
PPRC command (including GDPS) when, for instance, performing SWAP
between MCU and RCU.
3. In another MP in CHT PCB that includes the port where path creation
was attempted, there exists the Target/RCU Target port to which a HOST
I/O or a TC or UR I/O is issued. In that case, load balancing is performed,
and the load of I/O requests becomes high in the MP in the port where
path creation was attempted.
36 Initiator Port switching failure

Phenomena When a UR pair existed, switching Target Port to Initiator Port failed.
The problem may cases occur with all of the following conditions met.
1. A Universal Replicator pair
2. A port without TC path registration exists in the CHT PCB
3. Switch the attribute of the port in #2 from Target Port to Initiator Port.
Category Universal Replicator
37 HTP recovery failure by restart S/W after MP Restore

1. The blocked HTP did not recover by turning the restart S/W On.
2. When two HTP are blocked in a PCB, only one HTP was recovered by
Phenomena turning the restart S/W On.
3. Turning the restart S/W On recovered the blocked HTP in the PCB, but
the normal HTP in the same PCB was blocked.
The problem occurs when any of the following condition is met. Each
condition, #1 to #3, corresponds to the same number of each phenomenon
above.
1. After exchanging a micro-program online, turn the restart S/W On
while the HTP is being blocked.
2. After four blocked microprocessors in CMF PCB recovers by MP
Restore; turn the restart S/W On.
3. After performing the procedure of MP block and then MP Restore to
each MP one by one in a CMF PCB, turn the restart S/W On while the
HTP is being blocked.
Category Mainframe
38 Invalid PP license after SVP exchange

After the SVP exchange, the PP license became invalid. The license was
Phenomena
valid before the exchange.
1. An expired PP exists in BackupFD.
2. Copy the BackupFD onto SVP by executing All Configuration.
3. Perform the SVP reboot between 1 p.m. and 2 p.m.
Category SVP
Changed Part SVP
39 LOGIN-TOV at command issue requested to HDD

In the case of using Path Inline at DKA or FSW replacement, when all the
HDD in the loop simultaneously received the requests of command issue,
Phenomena
the LOGIN process (Link Up) took long, resulting in LOGIN-TOV
(SSB=A040).
The problem occurs when the result of the following calculation exceeds
8 seconds:
Conditions of Occurrence <the Link Up time per unit> * <the number of HDD>
Note that the Link Up time varies in a large range according to each
configuration with a different drive type.
Category HDD
40 Improper data display of exported CSV file in Excel

When the CSV file exported from the LDEV tab of the Basic Information
Phenomena Display was opened in Excel, the data in the fifth and the subsequent
columns were not properly displayed.
1. Display the LDEV tab.
2. The value of MAXLBA has four or more digits.
3. Click the Export button in the LDEV tab to export a CSV file.
Conditions of Occurrence 4. Open the CSV file in Excel.
Notes:
1. The problem always occurs when the above conditions are met.
2. The problem occurs only with RAID600, not with RAID500 or earlier.
Changed Part SVP
41 Remained dirty slots after removing mapped external LU
1. After disconnecting the mapped external LU, the dirty slots were not
de-staged.
Phenomena
2. When performing DELETE LU to the mapped external LU, the dirty
slots remained.
The problem occurs when the following condition #1 and #2, or #1 and
#3 are met.
1. Perform ADD LU to an external device that exceeds the maximum
capacity for each emulation type, but OPEN-V.
2. To the external VOL #1, perform format.
3. To the external VOL in #1, accept an host I/O.
42 PIN slot not displayed by volatile PS Off/On

Although a PIN slot existed, the slot was not displayed by performing
Phenomena
volatile PS Off/On.
Conditions of Occurrence 1. A PIN slot occurs.
2. Perform volatile PS Off/On.
Category Open or mainframe
43 Job ABEND with SSB=6709 due to cache failure

Phenomena JOB ABEND occurred due to cache failure with SSB=6709 reported.
Conditions of Occurrence 1. During an I/O
2. Cache failure
Category Cache
44 CHK3 and WCHK1 and SM failure during I/O to ex. volume

If SM failed during an I/O to an external volume, CHK3 was reset and
Phenomena
WCHK1 was generated due to the exceeded threshold value.
Conditions of Occurrence Problem may occur when SM fails during an I/O to an external volume.
45 CR failure at Web Server Status processing

After performing Define Configuration & Install, CR failed at the
processing of Web Server Status. In addition, a logical error occurred in
Phenomena
Refer Configuration and Define Configuration & Install, and this caused
the window display to be unavailable.
1. Perform Define Configuration & Install
2. The number of DCR settings is 8193 or more.
3. The 8,192nd and 8,193rd DCR information is set in the same LDEV.
The DCR information is registered in the order of parity groups and the
LDEV in each parity group.
Category Cache Residency Manager
Changed Part SVP
46 Pair suspend with SSB during initial copy of TC or UR

Initial copy of TC or UR, the following SSB occurred and pair suspended
Phenomena - For True Copy: SSB=c480, c4c8
- For Universal Replicator: SSB=8f81, 8f9a
The problem occurs when performing an initial copy of TC or UR when
HOST I/Os are successively issued to the same slot.
Category True Copy for Open or z/OS, Universal Replicator for Open or z/OS
47 TC initial copy failure with SSB=c45b, etc.

During TC initial copy, any of the following SSB occurred and the pair
Phenomena suspended.
SSB=c45b, c45d, c463, c4c9, c4cc
The problem occurs when performing TC initial copy with a highly
loaded device due to many Host I/Os or other factors.
Category True Copy
48 WCHK1 in DKA at CHK3 failure

Phenomena When CHK3 occurred, WCHK1 also occurred in DKA.
The problem occurs when CHK3 fails during an I/O. This occurs only in
DKA.
Category Shared Memory
49 Micro-program exchange online ABEND at MP reboot

A micro-program exchange online ended abnormally when one out of
Phenomena
eight numbers of MP Rebooted.
2. In a job using a synchronous channel, a copy instruction is issued.
3. Cancel is received from the host during write processing or while
waiting for copy completion.
4. A temporary blockade (link down) occurs on the path between CUs.
50 Invalid LDEV information of external connection

When acquiring Rmapi external connection information
Phenomena (dsvp_GetExternalInf2), the LDEV information of the external
connection became invalid.
The problem occurs when using RAID600 as an external-connection
destination.
Category Open or mainframe
Changed Part SVP
51 Improper display of CRIT status

When suspending a TC for z/OS (Sync, CRIT=Yes) pair, a
communication error, such as link down, occurred between the P-VOL
and S-VOL. This allowed the P-VOL only to suspend and caused the S-
Phenomena VOL to fail to change its status. In addition, Update WR to the P-VOL
was rejected due to "CRIT=Yes". Under this case, when CQUERY was
issued to the P-VOL, CRIT=No was reported while CRIT=PATHS/ALL
was supposed to be reported.
1. TC for z/OS pair, and CRIT=Yes
Conditions of Occurrence 2. When the pair is made to cause Suspend, a communication error (link
down, etc.) occurs.
3. Issue CQUERY to P-VOL.
52 LA error (SSB=3287, etc.) due to waiting for free segment space

During an FMTWRT update I/O to a UR pair, if a wait occurred for free
Phenomena segment space of a BITMAP slot, an LA error (SSB=3287, 3570, B011)
might occur.
1. MCU of a UR for z/OS pair in the Duplex or Duplex Pending state
Conditions of Occurrence 2. The UR pair in the RAID5 level
3. FMTWRT update I/O to the UR pair
4. Wait occurs for free segment space on BITMAP slot (I/O load high.)
Category Universal Replicator for z/OS
53 Write pending after LDEV format

After performing LDEV format, the SVP monitor shows that write
Phenomena
pending remained.
1. LDEV format
2. Mainframe volume
Conditions of Occurrence 3. RAID1
4. Use CVS to define the volume size to smaller than the maximum
capacity, or the volume is an external volume connected.
Note the write pending will be recovered and not continue to remain.
Category Mainframe
54 No SIM reported at blockade of COW or DP pools

When multiple pools of COW or DP are blocked at the time of volatile PS
Phenomena
On, a SIM was not reported.
The problem occurs when Mode 460 is set to OFF*, create multiple
Pools, and then perform volatile PS Off and then On.
* Mode 460 OFF: Backing up and recover the SM information are
unavailable.
Category Dynamic provisioning for Open
55 Unable to restore backup file

When a Syslog setting file (adtPrm.txt) did not exist, if the Syslog setting
Phenomena file backed up when creating the configuration backup file, the Restore
operation of the backup failed
The problem occurs when the file "adtprm.txt" does not exist under
c:/dkc200/mp/pc/, create a backup file with the Syslog checkbox selected
in the Download window of Control Panel, and then restore the created
file in the Restore window
Category SVP
Changed Part JAVA
56 Improper SIM at S-VOL failure during copy on MCU

When occurring an S-VOL failure during the Copy operation,
Phenomena SIM=DC5X, indicating P-VOL suspend due to S-VOL deletion, was
reported on the MCU.
1. Universal Replicator for Open or z/OS
2. The pair option error level is LU, or the pair status is Copy.
3. LU failure suspend occurs on the S-VOL.
When an S-VOL failure occurs, SIM reported on the MCU has been
changed from DC5X to DC2x.
Causes and Updates
DC2X: P-VOL suspend due to S-VOL failure
DC5X: P-VOL suspend due to S-VOL deletion
57 Data inconsistency on secondary for open Universal Replicator

Phenomenon 1: At the secondary site where UR for OPEN is used, the
following phenomenon (a) and (b) may occur. i) And ii) of (b) can occur
on volumes other than UR volumes.
(a) Data on the secondary volume of UR is not updated.
(b) An LA error (SSB EC=3287) occurs many times.
i) Host job abend
Phenomena
　　　　ii) Copy pair suspend
　　　　iii) WCHK1 of CHA MP
　　　　iv) FCA blockade in DKA
Phenomenon 2: At the secondary site where UR for OPEN is used, an LA
error does not occur, but logical inconsistency (SSB EC=ECA6, EC91,
EC94, etc.) may occur at the time of data update, which may suspend.
Severity (High, Medium, Low) High
Conditions of Occurrence The phenomenon’s 1 and 2 have the conditions of occurrence in common.
The phenomenon may occur when all of the following conditions are met:
　　　
A. RAID500: 50-09-01 and later, RAID600: 60-01-30-00/00 and later
B. UR for OPEN (It occurs in the secondary volume of the pair)
C. A UR pair consists of LUSE volumes.
D. An initial copy is performed or an update I/O is issued to a UR pair.
E. DKU L2 BOX or External Storage is in use
(256 or more external volumes are or were connected)
Note) In RAID, the information, called “VDEV”, is managed with the
following units.
Internal VOL: Per parity group
External VOL: Per LU
VDEV is managed with 2-byte information, and the upper one byte is
called “EDEV”.
- VDEV (2Byte): XXYY, XX=EDEV#
- External volumes use VDEV#:0x0400 and larger, and internal volumes
use smaller than 0x0400.
Therefore, when 256 or more external volumes are connected for
instance, the upper one-byte EDEV# is +1.
- Because the LUSE volume consists of volumes of different EDEV, the
problem occurs.Note that EDEV are managed internally, and it is hard to
see the EDEV. The problem occurs in the following cases.
- For example, LU of different EDEV is defined because 256 or more
external volumes are connected, and an LUSE volume consists of the LU
of different EDEV.
- As for internal volumes, this problem also occurs when DKU-L2 is
added, and when LUSE volume consists of LU of different EDEV.
When a UR secondary volume is a LUSE volume, each LU (LDEV)
Causes and Updates constituting the LUSE is accessed with the management information of
the top LU (LDEV) improperly due to a micro-program failure.
Category Universal Replicator
58 No password required at volume restoration

With the LDEV blocked, when performing PS Off and then volatile PS
On, users were not asked to enter the password, which was supposed to
Phenomena
be required at Volume restoration. As a result, the data could be restored
without the assurance of data integrity.
Conditions of Occurrence 1. The LDEV before performing PS Off has dirty slots and is blocked
2. Perform PS Off and then volatile PS On.
Category Open
59 Improper Takeover return code after removing path for UR

When performing Takeover from RAID Manager with the path removed,
Phenomena "SWAP-takeover" was returned. The expected return code was
"SVOL_SSUS-takeover".
1. Universal Replicator for Open
2. Device configuration does not have CU: LDEV# = 0:00 mounted.
3. Perform pair creation, Resync (including Takeover), Suspend, or Delete
from Raid Manager.
4. The operation in #3 fails.
Category Universal Replicator for Open
SSB=1602 and MIH when issuing YKQuery to highly loaded

60
RCU from BCM
When using TC for z/OS Sync or Async with the RCU highly loaded, if
Phenomena issuing the YKQuery command to the RCU by using the remote DKC
function of BCM, SSB=1602 and MIH occurred.
1. TC for z/OX or TC Async for z/OS
Conditions of Occurrence 2. Issue YKQuery to RCU by using the remote DKC function of BCM.
3. The RCU is highly loaded because an update I/O or initial copy to a
Sync or Async pair is being performed.
61 Failure of Restore or Blockade by specifying ECC Group

The Restore or Blockade operation might fail when performing it by
Phenomena specifying an ECC Group from the Logical Device window of the
Maintenance function.
The problem may occur when an ECC Group meets all of the following
conditions, and when performing Restore or Blockade by specifying the
ECC group from the Logical Device window of the Maintenance
function.
Conditions of Occurrence 1. The drive type is any of the following:
DKR2F-J300FC, DKS2D-J300FC, DKS2E-K300FC
2. The RAID level is 7D+1P.
3. The emulation type is any other than OPEN-V.
4. The RAID is 4-concatenated.
Category SVP
Changed Part SVP
62 Error code with no LDEV mounted in LDEV Security

When LDEV was not mounted in LDEV Security and Refresh All in
Phenomena Storage Navigator was performed, HIC on the Web Server Status window
turned red with the error code 67001 displayed.
The problem occurs when performing Refresh All in Storage Navigator
with LDEV not mounted in LDEV Security.
Changed Part SVP
63 MP Hang-up at pair suspending during TC initial copy
When suspending TC pairs during initial copy, MP hang-up occurred with
Phenomena
SSB=1609 reported.
1. True Copy for Open
2. Multiple remote copy pairs are in the Pending state.
3. Cause pair suspend by operation.
64 No display of volume information on LUN Manager Window

The LUN Manager window did not display some volumes that were not
Phenomena
used in Volume Migration.
Conditions of Occurrence 1. Perform the Volume Migration operation from Raid Manager.
2. Delete the pair whose volume migration has completed.
Category Volume Migration for Open
65 Improper number of SI pairs displayed on SI window

The number of pairs that the SI window of Storage Navigator displays
Phenomena
exceeded the actual number of the SI pairs.
Conditions of Occurrence The problem occurs when creating Volume Migration pairs.
Category Shadow Image for Open or z/OS
66 Improper remained days displayed for TC Async license

After the TERM-KEY of TC Async had expired, the license window of
Phenomena Storage Navigator showed that 177 days were remained for the use of TC
Async.
1. Term key will expire after 3 days.
Conditions of Occurrence 2. Install the Temporary key.
3. The installed temporary key has expired, or was uninstalled.
4. After #3, the Term key has expired.
Category SVP
Changed Part SVP
67 Unable to release RSV at Non-Stop micro-program exchange

At Non-Stop micro-program exchange, the Reserve could not be released
Phenomena
even though SCSI reset was received.
The problem occurs when Non-Stop micro-program exchange is
performed, SCSI reset occurs to the LDEV that has been reserved.
Category Open
68 Many 14DC with EC=9815 during TC Copy

During a TC pair in Copy, performing PS Off failed. 14DC occurred
Phenomena many times with EC=9815 reported, indicating that the number of retries
within RAID reached the upper limit.
1. TC for z/OS pair
2. A JOB using synchronous channel issues a copy instruction.
Conditions of Occurrence 3. A job cancel is received from the host while waiting for processing
other than the copy completion.
4. Temporary blockade (link down) occurs on the path between CUs, or
the status of the pair is being changed.
Category Mainframe
69 MP blockade due to exceeded CHK3 threshold

Phenomena At the SM failure, MP was blocked due to exceeded CHK3 threshold.
1. SM is blocked.
2. Highly loaded, which causes TOV that are waiting for free segment
space
Category Open
Invalid SSID setting when failing to add volume of UVM,

70
Snapshot, and DP
When the ADD LU operation of UVM or the addition of V-VOL of
Phenomena Snapshot or DP failed, SSID setting that corresponded to the VOL# of the
volume that attempted to add became invalid.
The problem occurs when ADD LU of UVM, or the addition of V-VOL of
Conditions of Occurrence Snapshot or DP fails, and when MF VOL is mounted in the range of
HDEV to which the same SSID given as that of VOL attempted to add.
Category Mainframe or open
71 SSB=b839 during I/O to TC for Open

While executing an I/O to a TC for Open pair, Check Condition of
Phenomena
SSB=b839 indicating no Sense Data occurred.
1. TC for Open in the COPY of PAIR state.
Conditions of Occurrence 2. Perform an I/O to the OPEN-VOL.
3. A failure occurs on RCU where the TC pair belongs or on the path
between MCU and RCU.
72 IGGN505A and MIH due to IPL delay

The IPL operation was delayed and message IGGN505A occurred. In
Phenomena
addition, MIH occurred or an error was reported to the host (EQC).
1. Use PAV.
2. Delete the Alias device used for the host I/O.
3. The deleted Alias device has not been used by the host (No I/Os).
4. Under the condition #3, an LDEV is mounted in the address of the
deleted device.
Category Compatible PAV for z/OS
73 Mismatched number of differential tables

The displayed number of used differential tables exceeded the actual
Phenomena number of used differential tables. In addition, the number of differential
tables available for use decreased.
Conditions of Occurrence The problem occurs when the following condition #1 and #2, or #1 and
#3 are met.
1. Use FCv2 or Snapshot, and no pair of SI, VM, or FCv1 exist.
2. After PS OFF, perform volatile PS ON.
3. Perform micro-program exchange offline.
Category Compatible Flash Copy V2, Copy-on-Write Snapshot
74 Failure of SI pairresync -restore

In the configuration where HUR and SI share a volume or the
Phenomena configuration where TC and SI share a volume, the pairresync -restore
command issued from RAID Manager failed.
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.
Category Shadow Image
75 Failure of pairresync -restore when using DPVOL in SI

When the DP VOL was used as the P-VOL or S-VOL of Shadow Image,
Phenomena
the pairresync -restore command from RAID Manager failed.
The problem occurs when all the following conditions are met.
1. System Option 80 is set to ON.
2. Perform pairresync -restore command from Raid Manager.
Conditions of Occurrence 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 DP VOL as the P-VOL or S-VOL of Shadow Image.
Category Shadow Image
76 Microcode exchange offline failure after Swap Resync failure

After HUR Swap Resync failed due to link down, when micro-program
Phenomena exchange offline was performed with the failed HUR pair remained, the
exchange operation failed.
The problem may occur when all the following conditions are met.
Conditions of Occurrence 1. Swap Resync of HUR fails.
2. Perform PS OFF, including dummy PS OFF at micro-exchange.
77 SI/VM/FCv1 pair creation failure

Phenomena Creating a SI/VM/FCv1 pair failed
1. Use SI/VM/FCv1.
2. After #1, uninstall the SM (This operation causes SI to become
unavailable.).
Conditions of Occurrence 3. After #2, install the SM (This operation causes SI to become
available.).
4. After #3, use SI/VM/FCv1.
5. Between #2 and #3, neither power cycle nor micro-program exchange
offline is not performed.
Category Shadow Image, Volume Migration, Compatible Flash Copy
78 Data miss-compare during I/O from OpenVMS

Phenomena During an I/O processing from OpenVMS, data miss-compare occurred.
1. Issue successively Write I/Os to the same LBA.
2. Receive reset.
The probability of occurrence will increase if the reset occurs frequently
and the same LBA is accessed frequently.
79 TCZ/ TCZ Async pair suspend due to invalid R0 data detected

After copying from a smaller P-VOL to a bigger S-VOL of TCZ/ TCZ
Async、
when using the volume which had been the S-VOL as the P-VOL to
Phenomena perform initial Copy,
the pair was suspended due to invalid R0 data detected (EC=c4d4) on the
area exceeding the capacity of the smaller volume which had been used as
the P-VOL.
Conditions of Occurrence 1. TC for z/OS/ TC for z/OS Async
2. Copy from a smaller P-VOL to a bigger S-VOL.
Category True Copy for z/OS/ True Copy for z/OS Async
80 Time out acquiring utilization rate long range physical PG

When acquiring the utilization rate of Physical PG of Long Range by
Phenomena using Export Tool, the processing aborted with error massage 4-6001
(time out error) displayed.
The problem may occur when it takes more than 30 minutes to acquire
the monitor data under the following conditions.
1. 90 or more PGs
2. Monitor data for Long Range of 5 days
Changed Part SVP
81 Fail to Initialize Web Server Status

Maintenance operations via SVP failed after the following operations:
1. A failure of HDD addition,
2. After recovering the blocked DKA caused by #1, without trying to add
Phenomena
HDD again, a micro-program exchange was attempted, but failed,
3. After #2 and SVP reboot, the initializing operations other than function
name DKC and BASE of Web Server Status failed.
Causes and Updates Microcode modified to fix the problem.
Category SVP
Changed Part SVP

Uspv 60-01-44-00-00

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Uspv 60-01-44-00-00

Diunggah oleh

Hak Cipta:

Format Tersedia

USPV

MICROCODE VERSION 60-01-44-00/00

Newly supported features and functions for Version 60-01-44-00/00

1-4 Support for TC/ TC for z/OS Migration from RAID450/RAID500

The change of contents for Version 60-01-44-00/00

3 TC pair suspend at replacement of CHT during I/O

4 SSB log (EC=549e) about atomic lock processing at SCSI reset

6 UR Reverse Resync failure

7 Error message after executing Disconnect Volume command

9 No support for external volume of minimum size

10 Improper maximum percentage value on the Y-axis

11 Data transfer failure with SSB=b6d8 reported

12 CHK2 during cache replacement

13 No emulation type available for adding external volumes

14 SCSI commands abnormal end

3. Normal Reserve command

4. Normal Release command

15 PIN slot after releasing HDP association

16 Ping error at LAN CHECK

17 Duplicate FSW list shown at PDEV un-installation failure

18 Unable to add Pool due to hardware failure

19 Pair suspend after MCU power cycle during TC initial copy

20 Performance degradation due to failure staging CR setting area

Unable to PS OFF during Quick Restore of SI or Volume

22 ABEND when issuing I/O to unequal-length track of TCZ pair

23 SLPR remained in Not Enough state

24 Many SIM indicating SLPR expiration

25 Improper child PP status at Term expiration

Storage Navigator start failure after SVP micro-program

27 PCB location listed in improper order in Dump window

Improper name of monitoring item displayed in monitoring

29 No color indication for expired PP license

30 Intervention requested at link down during I/O

31 Conflicted hash value resulting in performance decrease

Improper interval time period of monitoring and value

33 Response degradation during sequential overwrite I/Os

34 EIO de-staging delay

36 Initiator Port switching failure

37 HTP recovery failure by restart S/W after MP Restore

38 Invalid PP license after SVP exchange

39 LOGIN-TOV at command issue requested to HDD

40 Improper data display of exported CSV file in Excel

42 PIN slot not displayed by volatile PS Off/On

43 Job ABEND with SSB=6709 due to cache failure

44 CHK3 and WCHK1 and SM failure during I/O to ex. volume

45 CR failure at Web Server Status processing

46 Pair suspend with SSB during initial copy of TC or UR

47 TC initial copy failure with SSB=c45b, etc.

48 WCHK1 in DKA at CHK3 failure

49 Micro-program exchange online ABEND at MP reboot

50 Invalid LDEV information of external connection

51 Improper display of CRIT status

52 LA error (SSB=3287, etc.) due to waiting for free segment space

53 Write pending after LDEV format

54 No SIM reported at blockade of COW or DP pools

55 Unable to restore backup file

56 Improper SIM at S-VOL failure during copy on MCU

57 Data inconsistency on secondary for open Universal Replicator

58 No password required at volume restoration

59 Improper Takeover return code after removing path for UR

SSB=1602 and MIH when issuing YKQuery to highly loaded

61 Failure of Restore or Blockade by specifying ECC Group

62 Error code with no LDEV mounted in LDEV Security