VSP 70-03-40-00-M120

VSP
MICROCODE VERSION 70-03-40-00/00-M120

RELEASED 07/27/2012
New supported features and functions for Version 70-03-40-00/00-M120

1. Mainframe & Open System
1-1 SOM class change
Description The class of System Option Mode 769 has changed from “RSD” to “Public” from
DKCMAIN version 70-03-40-00/00.
Changed Part Config
2. Mainframe System
2-1 Cache control information enhancement at CHK2
Description When CHK2 occurs due to any of the following errors, cache control information can be
collected as information enhancement.
- ECC/ LRC error (SSB=5833 output)
- LA error (SSB=583C output)
- PA inconsistency (SSB=5860 output)
Changed Part DKCMAIN
3. Open System
NONE
The change of contents for Version 70-03-40-00/00-M120

1 Display of invalid dashed line in graph
Phenomena When "Maximum value display" or "Minimum value display" was
selected for [Display Option] on SVP with a graph for "Bad Received
Character Count. (Fibre)" displayed, an invalid dashed line is
displayed.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) "Port" is selected for Object in [Monitor Data Choice].
(2) "Loss Of Signal Count.(Fibre)", "Bad Received Character
Count.(Fibre)", "Loss Of Synchronization Count.(Fibre)", "Link
Failure Count.(Fibre)", "Received EOFs Count.(Fibre)", "Discarded
Frame Count.(Fibre)", "Bad CRC Count.(Fibre)", "Protocol Error
Count.(Fibre)", "Invalid Frame Count.", or "HTP/FNP Ex
Multiple.[Ex/sec.](FICON)" is selected for Item of [Monitor Data
Choice]. (Those are collectively called unsupported item.)
(3) 1 [min] or 1 [hour] is selected for [Sampling Rate (Display Period)]
(4) "Maximum value display" or "Minimum value display" is checked
for [Display Option].
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-03-40/00
Category Open or Mainframe
Changed Part SVP
HDS Confidential 1 of 31
2 Data inconsistency occurs in True Copy secondary volume
Phenomena The following phenomena may occur in the secondary volume of True
Copy (hereinafter referred to as “TC”) pair.
OPEN volume: A data inconsistency occurs in the secondary volume
of TC pair.
Mainframe volume: When the host reads the secondary volume, EQC
(Equipment check) is reported to the host (SSB EC=5860).
Severity (High, Medium, Low) High
Conditions of Occurrence May occur when all the following conditions A, B, C, and D are met,
or all A, B, C and E are met.
A. RAID700 All current versions

B. TC configuration
C. In the line between MCU and RCU, a data transfer delay of 15
seconds or more occurs
D. Initial copy or update copy is performed with HostModeOption 51
OFF (Round Trip Set Up Option)
E. Initial copy is performed with all the following conditions (a) to (c).
(a)HostModeOption 51 ON
(b)HostModeOption 65 ON (Round Trip Extended Set Up Option)
(c)Full installation of MPB (2Module (32MP)) in DKC of RCU side
Causes and Updates In the MCU side of True Copy, if it does not receive a response to an
update (initial) copy instruction from the RCU side, it requests to
cancel the update (initial) copy instruction for which no response is
returned, and then it gives an update (initial) copy instruction again. In
the RCU side, when the request for cancelling the update (initial) copy
instruction is received from the MCU side, it performs the cancel
processing for all the pending update (initial) copy instructions. Due to
a microcode bug in the RCU side, however, the RCU side does not
return a cancel response to the MCU side for all update (initial) copy
instructions for which the cancel processing is performed. Therefore
the subsequent new update (initial) copy instruction and the update
(initial) copy instruction for which the RCU side does not return a
cancel response are processed wrongly. As a result, a data
inconsistency occurs in the RCU side.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-03-40-00/00
Category True Copy, True Copy for Mainframe
3 Failure of multiple SSBs output

Phenomena Even though multiple SSBs were supposed to be output, only one SSB
was output. (The problem occurred with SSBs created by SVP.)
Conditions of Occurrence The problem occurs when multiple SSBs are created by SVP in a
second.
Changed Part SVP
4 Invalid display of capacity unit
Phenomena Phenomenon 1:
Even though resources in a table list on the following windows were
for Open only, "cylinder" that was a display unit for Mainframe was
available in Options for display unit.
-LUNs, Parity Groups, LDEVs, Resource Group Properties, External
LDEV Properties, Add LUN Paths, Delete LUN Paths, Add Resources,
Change Setting (External VOL), Select Parity Groups, Select LDEVs,
Remove Resources, Edit Encryption
Phenomenon 2:
For a table list on the following windows, "Cylinder" and "Page"
which were display units for Mainframe and pool VOLs respectively
were displayed in a unit of GB.
-Edit Pools, Restore Pools, Shrink Pool, Stop Shrinking Pool, Monitor
Pools, Stop Monitoring Pools, Start Tier Relocation, Stop Tier
Relocation, Create Pools, Delete Pools, Pool Property.
Phenomenon 3:
For a table list on the following window, "Cylinder" which was a
display unit for Mainframe was displayed in a unit of GB.
-Expand Pool
Conditions of Occurrence Phenomenon 1:
The problem occurs when at least one Mainframe parity group or
LDEV exists in the configuration.
Phenomenon 2:
The problem occurs when the target window is displayed while pools
are displayed in a unit of cylinder or page on the previous window.
Phenomenon 3:
The problem occurs when the target window is opened while pools are
displayed in a unit of cylinder on the previous window.
Affected Products/Version SVP: 70-02-03/00 and higher
Category Storage Navigator
Changed Part Storage Navigator
5 Failure of PDEV replacement/installation after SAS-port or

PDEV-port blockage
Phenomena After a SAS-port or PDEV-port was blocked, the PDEV recovery
failed and PDEV replacement/installation might fail.
Conditions of Occurrence The problem may occur when the recovery of PDEV
replacement/installation is running right after a SAS-port or PDEV-
port is blocked with failure.
Affected Products/Version DKCMAIN: 70-02-54-00/00 and higher
Category HDD
6 Unable to accept host I/O after recovery from system
Phenomena When a system configuration failure due to incorrect cable connection
was recovered, an I/O from a host might not be accepted even though
SVP window showed that LDEV status was normal.
Severity (High, Medium, Low) Medium
(1) PS ON is performed with a wrong cable connection between SSWs.
(2) The wrong connection is corrected and the system is recovered by
SSW or DKA replacement.
(3) After above, host I/O is issued without performing PS OFF/ON.
7 Failure of PDEV/SSW/DKA replacement

Phenomena If a type name of spare drive was displayed as "????????" on Refer
Configuration window, replacement of PDEV of the spare drive or that
of SSW/DKA to which the spare drive belonged failed and SSB=A7E1
was output.
(1) An SSD drive is used as a spare drive.
(2) Drive copy to the spare drive is executed.
(3) PS OFF and ON is performed while the spare drive is used as a
copy target of data drive.
8 Error by FC operation or Shadow Image Initialize

Phenomena After PS OFF or power outage during Shadow Image Initialize and
then non-volatile activation, when one of the following operations was
performed, an error occurred.
(1) FC operation (SSB=9639)
(2) Shadow Image Initialize (Storage Navigator message 7105 8525)
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) The storage system is powered OFF or a power outage occurs
before the completion of Shadow Image Initialize. (* Operation order
does not matter)
(2) After the storage system stops, non-volatile activation is performed.
(3) After the storage system is activated, an FC operation or SI
Initialize is performed.
Category Flash Copy version2
9 Permission failure when multiple users log in CCI at the
same time
Phenomena When 2 users who used CCI logged in at the same time, their
permissions which should have been different became identical. As a
result, operations each of them had been originally allowed were
disabled or those each of them had been not originally allowed were
enabled.
(1) Multiple users who use CCI log in at the same time.
(2) A reset occurs by a command executed from CCI by a user other
than the above.
Category CCI
10 Failure of CM maintenance if MP is blocked due to WCHK1

during maintenance
Phenomena If an MP was blocked due to WCHK1 during CM maintenance, the
CM maintenance might fail.
(1) One of the following operations is in progress.
(a) CM maintenance
(b) CM failure blockage
(c) PS OFF
(d) PS ON
(2) Some MPs in an MPB are blocked. (Except a case that 4 MPs in the
MPB are blocked.)
Category Open of Mainframe
11 No display of write I/O "Received"

Phenomena When a write I/O was issued to a UR S-VOL while the pair was
suspended and "Enable" was set to S-VOL Write, "Received" for the
write I/O did not appear on Storage Navigator.
(1) Universal Replicator for Mainframe pair
(2) The URz pair between P-VOL and S-VOL is suspended.
(3) SOM20 is set to ON or S-VOL Write is "Enable".
(4) A write I/O is issued to the S-VOL.
Category Universal Replicator for Mainframe
12 Failure of Detail button
Phenomena When a task of Stop Shrinking in Failed status was selected on Tasks
window of Storage Navigator and then task status was displayed,
"Detail" button did not work.
Conditions of Occurrence The problem occurs when a task of Stop Shrinking in Failed status is
selected, task status is displayed, and then Detail button is clicked.
Affected Products/Version SVP for Open: All
SVP for Mainframe: 70-02-53/00 and higher (DPz), 70-03-01/00 and
higher (DTz)
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe,
Dynamic Tiering, Dynamic Tiering for Mainframe
Changed Part SVP
13 Delay in response due to conflict between I/O and processing

Phenomena When a conflict occurred between a host I/O and a processing while
monitoring status was During Computation, the response was delayed.
(1) Dynamic Tiering or Dynamic Tiering for Mainframe is used.
(2) Monitoring status of the pool is “During Computation”.
Affected Products/Version DKCMAIN for Open: All
DKCMAIN for Mainframe: 70-03-01-00/00 and higher
Category Dynamic Tiering, Dynamic Tiering for Mainframe
14 Invalid MP Usage rate display

Phenomena When MP usage rate was displayed on the performance monitor, the
rate during the time period of power OFF was displayed as 0%.
(1) The monitoring switch is turned ON and performance monitoring
data is collected.
(2) During (1), there is a time period that the performance monitoring
data cannot be collected due to power outage.
(3) One of the following is performed. (a time period that the
performance monitoring data cannot be collected is essential in the
display hours)
(a) MP usage rate is displayed on the performance monitor of Storage
Navigator.
(b) Monitoring data is displayed by using Export tool while “group
PhyProc” described in the command file at activation.
Category Performance Monitor
Changed Part SVP
15 Failure of command execution after interruption by MP reset
Phenomena After asynchronous commands were executed in series from CCI, if
the processing was interrupted by a rest, the specified command could
not be executed and the following commands which were received
were not executed too.
Conditions of Occurrence The problem may occur when an MP reset occurs while asynchronous
commands are executed in series.
Category CCI
16 Unable to confirm SAS port blockage

Phenomena After a SAS port on CL1/ST was blocked with failure without data
I/O, if failure blockage occurred in a SAS port on CL2/ST, the latter
blockage of the SAS port on CL2/ST could not be confirmed.
SIM=CF11-XX, CF12-XX (XX=SAS port number)
SSB=A4B0, A491, A06B
(1) No data I/O
(2) Both CL1 and CL2 sides of pair SAS ports are blocked.
(3) A SAS port failure except the top port between DKA and DKU
Causes and Updates The micro-program has been modified to fix the problem.
Category HDD
17 Repeated link-up and link-down with SIM/SSB output in

HTP by link failure
Phenomena When a link failure occurred and link-up and link-down repeatedly
occurred in an HTP port that was linked up, the HTP port might be
blocked and SIM=21A3XX and SSB=7A39, 7A30, and 5331 were
output.
(1) Mainframe host connection.
(2) A path is connected to an HTP port and the port is linked up.
(3) In the HTP port, a link failure (such as cable failure, cable
connection failure and SFP failure) occurs and link-up and link-down
repeatedly occur.
Affected Products/Version HTP: All
Fixed Product/Version HTP: 70-03-36
Category Mainframe
Changed Part HTP
18 Host IOS071I output when host PAV mode is changed
Phenomena When host PAV mode is changed, IOS071I (START PENDING) was
output.
(1) Mainframe host connection.
(2) Host PAV mode is set to Compatible PAV mode or Hyper PAV
mode.
(3) One of the following commands to switch PAV mode is executed
from the host during I/O processing.
- SETIOS HYPERPAV=NO (Switching to Compatible PAV mode)
- SETIOS HYPERPAV=YES (Switching to Hyper PAV mode)
Category Mainframe
19 Failure in option cache PCB replacement

Phenomena During an internal processing associated with an Option Cache PCB
failure, a power outage occurred in DKC. After that, when the Option
Cache PCB was replaced following PS ON, the replacement failed and
SVP message [ONL2288W] and [ONL2412E] was output.
(1) Basic Cache PCB is in normal condition.
(2) Option Cache PCB or any of Cache Module Group is blocked.
(3) An internal processing such as Destaging the data on the cache, or
recreation of directory is in progress.
(4) PS ON after the power outage.
20 SSB=3332 after installation or removal of parity group

Phenomena When installation or removal of a parity group was performed from
Install window of SVP, SSB=3332 might be output in rare cases.
Conditions of Occurrence The problem may occur in rare cases when all the following conditions
are met.
(1) Installation or removal of a parity group is performed from Install
window of SVP.
(2) Within a few seconds after closing the Install window, the window
is opened again.
Changed Part SVP
21 No display of "Total" for total error count on Threshold
Counter Display dialog box
Phenomena On Threshold Counter Display dialog box of Information, "Total" for
the total error count was not displayed above the column of threshold.
Conditions of Occurrence The problem occurs when Threshold Counter Display dialog box of
Information is displayed.
Changed Part SVP
22 Registered task disappears

Phenomena On Tasks window of Storage Navigator, a registered task disappeared.
(1) One of tasks listed below, which is being executed or in wait status,
is registered.
(2) SVP is rebooted.
- Format
- Shredding
- Edit encryption to request format operations
Category Open Volume Management, Virtual LVI
Changed Part SVP
23 Failure of graph display of long-range usage rate

Phenomena When usage rate in long range of Performance Monitor was displayed,
a line of graph was not displayed even in a time period when an
operation was being performed.
(1) Monitor data is collected in long-range.
(2) Data is not collected in some time period. (such as power outage
and maintenance)
(3) To display usage rate in long-range on Performance Monitor of
Storage Navigator, the specified start time is in the above time period.
(The time specified is in the above time period for Export Tool too.)
Changed Part SVP
24 No guard for incorrect operation on the window
Phenomena At CM installation/removal, if CM capacity, Cache Residency Manage
(DCR) capacity, or the number of extents of CLPR1 to 31 was changed
without changing CM capacity, the operation was not guarded on the
window. After that, SVP message ONL0870I was output during the
later processing and the operation was disabled without operation
target.
(1) CM installation or removal is performed.
(2) One of the following operations is performed.
(a) At CM removal, CM capacity, Cache Residency Manage (DCR)
capacity, or the number of extents of CLPR1 to 31 is reduced without
reducing the CM capacity.
(b) At CM installation, CM capacity, DCR capacity, or the number of
extents of CLPR1 to 31 is increased after CM capacity is increased,
and then the CM capacity is turned back to the previous.
Changed Part SVP
25 Failure suspend of delta UR/URz pair

Phenomena In 3DC multi-target configuration, when suspend was performed for
TC/TCz pairs with S-VOL specified, and an I/O was issued to L site
(TC/TCz S-VOL), the I/O stopped and delta UR/URz pair was
suspended with a failure. (SSB=EDD8 was frequently output.)
(1) 3DC multi-target delta configuration
(2) Following operations are performed in that order.
(a) An I/O is issued to P site.
(b) Suspend is performed for TC/TCz pairs with S-VOL specified.
(c) An I/O is issued to L site.
(d) Reserve Resync is performed to TC/TCz pairs.
(e) Takeover is performed to TC/TCz pairs.
(f) Suspend (SSWS) is performed for TC/TCz pairs with S-VOL
specified. (The status of TC/TCz pairs is changing to SSWS and some
pairs still in Duplex status.)
(g) An I/O is issued to L site.
(h) An I/O is issued to P site.
Category Universal Replicator, Universal Replicator for Mainframe
26 Unfinished task that restarts after SVP reboot
Phenomena When SVP was rebooted while a task was executed in Storage
Navigator, the task that restarted after the reboot could not finish.
Conditions of Occurrence The problem occurs when SVP is rebooted during one of the following
tasks is executed in Storage Navigator.
- LDEV creation (only when other than [No Format] is specified.)
- Tier relocation initiation
- Pool shrink
Changed Part SVP
27 Unable to stop Diagnosis

Phenomena When diagnosis was executed with Loop Limitless checkbox was
checked while A3 routine of Path INLINE was in progress, a dialog to
stop the processing could not be displayed because the Path INLINE
window was grayed out, and the operation was disabled.
(1) SVP is set to Modify mode.
(2) Path INLINE is opened from Diagnosis.
(3) Diagnosis with A3 routine specified is executed while Loop
Limitless checkbox is checked.
Changed Part SVP
28 Blockage of MP at offline micro-program exchange or SM

volatile power ON
Phenomena Phenomenon1
During offline micro-program exchange of DKCMAIN, WCHK1
occurred, some MPs were blocked, and the exchange failed. (SVP
message SMT2433E and SSB=0005/0006 were output.)
Phenomenon2
When SM volatile power ON was performed, the system was activated
with some MPs blocked. (SSB=0005/0006 was output.)
(1) The total capacity of DP/DPz/DT/DTz pools is 3.5PB or larger.
(2) Offline micro-program exchange or SM volatile power ON is
performed.
Category Dynamic Provisioning, Dynamic Provisioning for Mainframe,
Dynamic Tiering, Dynamic Tiering for Mainframe
29 Reserve command takes 1 or more seconds to finish
Phenomena When a reserve command was issued during Flash Copy operation, the
processing might take 1 or more seconds to finish. In that case,
SSB=506F was output.
(1) Mainframe
(2) A Flash Copy operation is in progress.
(3) A reserve command is received.
Category Mainframe
30 Page allocation to inadequate tier

Phenomena Even when the total capacity of tiering policy level1 could be
contained in Tier1, pages were allocated in Tier2 in some cases.
Even when the total capacity of tiering policy level3 could be
contained in Tier2, pages were allocated in Tier3 in some cases.
Conditions of Occurrence The problem may occur when any of the following conditions is met.
[When the number of tiers is 3]

(1) There are settings for Tiering Policy Level1, and Level2 or ALL in
a pool, and the following formula works:
The total capacity of level1 < tier1 capacity x depletion threshold < the
total capacity of level1 + the total capacity of level2 or ALL
(2) There are settings for Tiering Policy Level3, and Level4 or ALL in
a pool, and the following formula works:
total capacity of level3 + the total capacity of level4 or ALL
(3) There are settings for Tiering Policy Level2 (which can be included
in Tier1) and ALL in a pool, and the following formula works:
The total capacity of Level2 < tier1 capacity × depletion threshold <
the total capacity of Level１ + the total capacity of ALL
(4) There are settings for Tiering Policy Level4 (which can be included
in Tier2) and ALL in a pool, and the following formula works:
The total capacity of Level4 < tier2 capacity x depletion threshold <
the total capacity of Level3 + the total capacity of ALL
[When the number of tiers is 2]

(5) There are settings for Tiering Policy Level１ and ALL in a pool,
and the following formula works:
total capacity of level1 + the total capacity of ALL
Affected Products/Version DKCMAIN for Open: 70-02-54-00/00 and higher
DKCMAIN for Mainframe: 70-03-01-00/00 and higher
Category Dynamic Tiering, Dynamic Tiering for Mainframe
31 Delay in response to host when time-out occurs
Phenomena When a write request turned time-out while SOM15 or SOM862 was
set to ON, response to a host might be delayed.
(SSB=A4C2)
(1) SOM15 or SOM862 is set to ON.
(2) There is a data I/O.
(3) A command time-out failure occurs in a write request.
Category HDD
32 Failure of filtering Total or Used capacity by cylinder

Phenomena On V-VOL tab on the top window displayed when an individual pool
was selected from Pool on Storage Navigator, when Capacity Total or
Used column was filtered by cylinder for capacity unit, it was not
filtered by cylinder.
Conditions of Occurrence The problem occurs all the following conditions are met.
(1) A pool of Mainframe is displayed on V-VOL tab on the top
window displayed when a pool is selected from Pool on Storage
Navigator.
(2) Capacity Total or Used is filtered with cylinder specified for
capacity unit.
Affected Products/Version SVP: 70-02-53/00 and higher (DPz), 70-03-01/00 and higher (DTz)
Category Dynamic Provisioning for Mainframe, Dynamic Tiering for Mainframe
Changed Part SVP
33 Failure of DKCMAIN micro-program exchange in DKU-less

configuration
Phenomena When DKCMAIN micro-program was exchanged in DKU-less
configuration, SVP message SVP0732W appeared and the exchange
failed.
(1) DKU-less configuration
(2) Maintenance window has never been opened.
(3) DKCMAIN micro-program is exchanged.
Changed Part SVP
34 Host time-out with SSB=7A20 output at PDEV installation
during I/O processing
Phenomena When a PDEV was installed during I/O processing, ICC host time-out
occurred and HTP log=1870 was output.
(1) There is a data I/O from a host.
(2) A PDEV is installed.
Category HDD
35 Performance degradation of TC/TCz, UR/URz, LDEV

format or I/O processing
Phenomena When TC/TCz or UR/URz was used or LDEV format was performed,
if an MP failure such as CHK3 repeatedly occurred in the same MP,
performance of I/O processing, TC/TCz, UR/URz, and LDEV format
might degrade and SSB=1042 was output.
(1) TC/TCz or UR/URz is used or LDEV format is performed.
(2) A failure reset (such as CHK3, CHK1B, CHK4 and hang-up reset)
occurs in an MP in an MPB having ownership of the LDEV used in
(1).
(3) The above failure reset repeatedly occurs in the same MP.
Category True Copy, True Copy for Mainframe, Universal Replicator, Universal
Replicator for Mainframe
36 Continuous ICC occurrence during read I/O from host

Phenomena During read I/O processing from a host, ICC might continuously occur.
In this case, SSB=1602 and 7A20 (HTP EC=4131 and 3301) were
output.
(1) Mainframe
(2) HPF on host side is ON.
(3) HPF is installed on RAID700 side.
(4) Ownership of each LDEV is distributed to multiple MPBs.
Affected Products/Version HTP: All
Fixed Product/Version HTP: 70-03-36
Category Mainframe
Changed Part HTP
37 WCHK1 due to LA error during I/O processing for P-VOL
of SI/SIz pair
Phenomena When an LA error occurred during I/O processing to a P-VOL that was
a DP-VOL used in an SI/SIz pair in split copy processing, WCHK1
occurred and SSB=32FE, B2CB and SIM=3073 were output.
(1) UVM is used.
(2) Shadow Image or Shadow Image for Mainframe is used.
(3) DP-VOL that is an external VOL is used as a pool VOL.
(4) An SI/SIz pair whose P-VOL is the above DP-VOL.
(5) Split copy is performed for the above SI/SIz pair.
(6) During the above processing, an I/O is issued to the SI/SIz P-VOL.
(7) During the above I/O processing, an ECC/LRC error occurs.
38 SSB=14DC and 14FF output when external VOL is used

Phenomena When an external VOL was used, SSB=14DC and 14FF (waiting
timeout for resource) were output.
(1) Universal Volume Manager is used.
(2) Cache mode is ON in an external VOL.
(3) System Option Mode872 is set to ON.
(4) Sequential write I/O and random write/read I/O are issued to the
same VOL.
Category Universal Volume Manager
39 Continuous SSB=C470 output at TCz initial copy

Phenomena When TCz initial copy was performed while using a DP-VOL as a P-
VOL, SSB=C470 was continuously output.
(1) True Copy for Mainframe
(2) P-VOL is a DP-VOL.
(3) TCz initial copy is performed.
(4) Page reclamation is performed. (such as an ERASE command or
batch page reclamation)
Category True Copy for Mainframe
40 Failure of CCI activation from remote command device
Phenomena When CCI was activated using a remote command device,
SSB=D07B/B98E or D07B/B98F were output and the activation
failed.
(1) Instance of CCI connected to a remote command device is
activated.
(2) Multiple CCI instance numbers or multiple server connection
WWNs is used.
Category CCI
41 Inadequate Storage Navigator message

Phenomena At a pair addition from Storage Navigator, if a serial number different
from that corresponding to a registered mirror# was registered, Storage
Navigator message 6505 58040 (An internal error occurred.) appeared,
but the error could not be identified from the message. SSB=E8A2 was
also output.
(1) UR Open or Mainframe
(2) The following operations are performed in that order.
(a) Creation of 2 or more pairs with the same JNLG# and same
mirror# is preset from Storage Navigator, and one of the two creating
operations is intentionally ended in failure.
(b) Another pair is successfully registered and the failed creation
remains in the preset.
(c) The pair in preset is edited to replace the serial number with an
invalid value and then pair registration is retried.
* JNLG# and mirror# set in (c) are the same as those in (a), and other
parameters are correct.
Causes and Updates The micro-program has been modified to output the correct Storage
Navigator message as follows in this case.
(6505-78270) Pair creation failed because the serial number, the
controller ID, and the path type of the specified secondary storage
system are invalid.
SVP: All
SVP: 70-03-40/00
42 Failure of PS OFF with SIM=338F-00 output
Phenomena After MPB removal, PS OFF might fail and SIM=338F-00 was output.
(1) After PS ON, an MPB has been removed.
(2) MP stop by MPB removal and communication between SVP and
DKC occur at the same time. (extremely-low probability)
(3) PS OFF is performed.
43 No guard of reverse resync operation between I site and R

site
Phenomena In 3DC cascade configuration with 3 UR/URz sites, a reverse resync
operation for a pair between I site and R site after a pair between P site
and I site was suspended was not guarded.
(1) Open or Mainframe
(2) 3DC cascade configuration with 3 UR/URz sites
(3) A pair between P site and I site is suspended.
(4) A reverse resync operation is performed for a pair between me and
R site.
44 ICC occurrence when MIH occurs in Mainframe

environment
Phenomena When MIH occurred in Mainframe environment, ICC occurred. (HTP
LOG=1870)
(1) Mainframe
(2) MIH occurs.
Category Mainframe
45 Failure suspension in UR/URz pair between P site and I site
by resync operation for the UR/URz pair
Phenomena In 3DC cascade configuration with 3 UR/URz sites, when a UR/URz
pair between P site and I site was suspended, a reverse resync
operation was performed for UR/URz pair between I site and R site,
and then a resync operation is performed for the UR/URz pair between
P site and I site, failure suspension occurred in the UR/URz pair
between P site and I site.
(SSB=ED00, ED2A, and ED2B)
(1) Open or Mainframe
(2) 3DC cascade configuration with 3 UR/URz sites
(3) A reverse resync operation is performed for a UR/URz pair
between I site and R site while a UR/URz pair between P site and I site
is suspended.
(4) After the above operation (3), a resync operation is performed for
the UR/URz pair between P site and I site.
46 Failure of IP address setting

Phenomena When an IP address was changed to 126.255.255.15 by Install-
SetIPAddress of SVP, if SVP was rebooted, the IP address became
169.254.xxx.xxx. After that, Storage Navigator could not be activated.
If the Maintenance window of SVP was opened, SVP message
STA0117E (An error occurred in the Communication between the SVP
and DKC.) appeared and DKC information could not be obtained.
Conditions of Occurrence The problem occurs when the same IP address exists on the same
network.
Changed Part SVP
47 Failure of SSW replacement with SSB=4ACX/4A0X output

Phenomena SSW replacement failed and SSB=A4CX and A40X were output.
Conditions of Occurrence The problem occurs when an HDD failure occurs during SSW or DKA
replacement.
Category HDD
48 Increase in MP usage rate with SSB=14FF, 14DC, and 8956
output
Phenomena During I/O processing to a DP/DPz or DT/DTz VOL with which an
external VOL was associated as a pool VOL, if a pool VOL that was
an external VOL was added to the DP/DPz or DT/DTz VOL, MP
usage rate increased and SSB=14FF, 14DC, and 8956 were output.
(1) Universal Volume Manager configuration
(2) An external VOL is used as a pool VOL.
(3) An I/O is issued to a DP/DPz or DT/DTz VOL associated with the
above pool.
(4) The type of the I/O is sequential write.
(5) System Option Mode872 is set to ON.
(6) A pool VOL that is an external VOL is added to the DP/DPz or
DT/DTz VOL during I/O processing.
Category Universal Volume Manager
49 Taking longer time for status transfer at delta resync

operation
Phenomena When a pair for delta resync was created and then a delta resync
operation was executed in 3DC cascade configuration with 3 UR sites,
the delta resync operation succeeded but some pairs took a longer time
for status transfer from Copy to PAIR compared to other pairs in the
mirrors.
(1) Open
(2) 3DC cascade configuration with 3 UR sites
(3) In a different configuration (other than above), the following
operations are executed.
(a) UR pair creation
(b) Suspend
(c) An I/O
(d) UR pair deletion
(4) After the above operations of (3), a UR pair for delta resync is
created in the configuration of (2).
(5) A delta resync operation is executed.
Category Universal Replicator
50 SSB=DD09 output at ABTS occurrence
Phenomena When ABTS occurred, SSB=DD09 was output.
(1) Host Mode Option51 is set ON in MCU and RCU sides.
(2) There is a TC/TCz pair and TC/TCz path.
(3) ABTS occurs due to missing data frames and so on.
51 Unable to decrease JNL usage rate at S-site

Phenomena In 3DC multi-target (delta resync) configuration with 3 UR sites, even
when a host I/O to P-site was stopped, JNL usage rate at each S-site
did not decrease.
(1) Open
(2) 3DC multi-target (delta resync) configuration with 3 UR sites
(3) An operation to allocate remote command devices to all mirrors of
each P-site and S-site is executed on Journal Operation window.
52 Failure of FCSE relationship creation, leading to Start

pending/MIH
Phenomena FCSE relationship creation or deletion failed and SSB=F489, 96AF,
and 9617 were output.
If a TSE VOL was accessed while leaving the condition as was, Start
pending/MIH occurred and SSB=1602 was output.
(1) Mainframe
(2) FCSE relationship creation or deletion
(3) A target VOL is a TSE VOL.
(4) LDEV ownership is migrated.
Category Mainframe
53 SSB=48B3 and 481E output at update I/O
Phenomena When an update I/O was issued from a Mainframe host to a VOL that
was used as an FCv2 source VOL and as a UR primary VOL,
SSB=48B3 and 481E were output.
(1) A configuration in which FCv2 source VOL and UR primary VOL
share the same VOL.
(2) An update I/O that is a sequential access is executed for an un-
copied area of FCv2 source VOL.
Category Flash Copy version2
54 Failure of Long Range monitoring data backup

Phenomena For Long Range monitoring data of Performance Monitor, the
following phenomena (1) and (2) alternately occurred for each set of
monitoring data for 3 months.
(1) The data was not backed up in standby SVP.
(2) The data at 0:00 every day was not backed up.
(1) Dual SVP configuration.
(2) Monitoring data of Performance Monitor is obtained. (Monitoring
switch is ON.).
(3) Switching between the master and standby SVPs.
Changed Part SVP
55 Invalid pair status at restore copy for CoW Snapshot pair

Phenomena When a restore copy was performed for a CoW Snapshot pair, the pair
status did not become Suspend.
(1) A restore copy is requested for a CoW Snapshot pair.
(2) A failure that disables the restore copy is detected.
Category Copy-on-Write Snapshot
56 No progress of copy processing after ownership migration
Phenomena In 3DC delta configuration, if ownership migration occurred after a
delta resync was performed or a delta pair status changed to HLDE,
copy processing of UR did not make progress.
(1) JNL that supports UR multi (*)
(2) 3DC multi-target configuration with delta resync (TC and UR),
3DC multi-target configuration with delta resync (UR only), or 3DC
cascade configuration with delta resync
(4) A delta resync operation is performed.
(5) HLDE status of delta UR is changed to HOLD status.
(6) A delta pair status changes to HLDE.
(7) After the operation (6), allocation of the processor blade of LDEV
used by a JNL VOL is changed. (Maintenance, failure, or allocation
from CCI or Storage Navigator)
* JNLG of JNLG# with (M) on Journal Operation in Storage Nav.
57 Unable to correct parameters for UR/URz pair creation

Phenomena During UR/URz pair creation for the 2nd mirror UR/URz pair on the
Universal Replicator window of Storage Navigator, an incorrect
parameter was specified.
To correct the parameter, when some pairs displayed in Preview were
selected and then pair creation window was opened again, parameters
such as serial number were fixed and could not be changed.
Conditions of Occurrence The problem occurs when some pairs displayed on the Preview list are
selected and pair creation window is opened at UR/URz pair creation
for the 2nd mirror UR/URz pair.
The problem does not occur if all of the displayed pairs are selected.
Changed Part SVP
58 Incorrect status display of FCSE pair on Storage Navigator

Phenomena The status of an FCSE pair became Faildstate but it was normal on
Storage Navigator.
(1) FCSE pair configuration
(2) Pair status is Faildstate.
Category Flash Copy SE
59 Failure suspension of UR/URz pair with SSB=EF25 output
Phenomena After a failure blockage of MPB occurred, a UR/URz pair with JNLG#
0x00 output SSB=EF25 and was suspended with failure.
(1) Universal Replicator or Universal Replicator for Mainframe
(2) JNLG ownership on UR/URz secondary site belongs to multiple
MPBs.
(3) A failure blockage occurs in an MPB with JNLG ownership on
UR/URz secondary site.
Category Universal Replicator or Universal Replicator for Mainframe
60 Failure suspension at delta UR pair deletion with SSB and

SIM output
Phenomena When a delta UR pair was deleted in TCxUR multi-target delta
configuration, URxUR multi-target delta configuration, or URxUR
cascade delta configuration, a failure suspension occurred and
SSB=EC42 and EC01, and SIM=DC1XXX were output.
(1) TCxUR multi-target delta configuration, URxUR multi-target delta
configuration, or URxUR cascade delta configuration.
(2) A delta UR pair is deleted.
61 Invalid UR pair status at pair deletion/suspend

Phenomena When a pair deletion was performed for a pair between P site and R
site in UR 3DC (URxUR cascade or URxUR multi-target) delta
configuration, the pair status remained Deleting.
In the case of a pair suspend operation, the pair status remained
Suspending.
(1) Universal Replicator
(2) An old delta configuration of URxUR cascade delta configuration
or URxUR multi-target delta configuration (without UR control path
registration)
(3) UR pair deletion or suspend is performed.
62 Failures of relationship status display on Storage Navigator
When an FCv2 relationship was created while sharing the source VOL
(S-VOL) with an already-created FCSE relationship, the S-VOL of
FCv2 did not become Normal status on Storage Navigator.
Phenomenon2
When an FCSE relationship was created while sharing S-VOL with an
already-created FCv2 relationship, the S-VOL of FCSE did not
become Normal status on Storage Navigator.
Phenomenon3
When an FCv2 relationship was deleted while FCSE and FCv2 shared
S-VOL, the S-VOL of FCv2 remained in Normal status on Storage
Navigator.
Phenomenon4
When an FCSE relationship was deleted while FCSE and FCv2 shared
S-VOL, the S-VOL of FCSE remained in Normal status on Storage
Navigator.
Phenomenon5
When FCSE and FCv2 shared S-VOL and both relationships were in
Suspend status, if the relationship in Suspend status was deleted, the
status remained SUS on Storage Navigator.
Phenomenon1
(1) FCSE relationship configuration
(2) An FCv2 relationship is created by using S-VOL of the FCSE
relationship.
Phenomenon2
(1) FCv2 relationship configuration
(2) An FCSE relationship is created by using S-VOL of the FCv2
relationship.
Phenomenon3
(1) FCSE and FCv2 relationships share the same S-VOL.
(2) The FCv2 relationship is deleted.
Phenomenon4
(1) FCSE and FCv2 relationships share the same S-VOL.
(2) The FCSE relationship is deleted.
Phenomenon5
(1) FCSE and FCv2 relationships share the same S-VOL and the both
relationships are in Suspend status.
(2) Other than the above, there is another FCSE/FCv2 relationship that
uses the same S-VOL and the relationship is not in Suspend status.
(3) The FCSE/FCv2 relationship in suspend status is deleted.
Category Flash Copy version2, Flash Copy SE
63 Failure suspension of unexpected UR pair with SSB=EDD4
Phenomena In UR 3DC (URxUR cascade or URxUR multi-target) delta
configuration, a failure suspension might occur in an unexpected UR
pair and SSB=EDD4 was output.
(1) Universal Replicator
(2) URxUR cascade configuration (I site), URxUR multi-target
configuration (P site), URxUR cascade delta configuration (P site, I
site and R site) or URxUR multi-target delta configuration (P site, L
site, and R site) * Problem occurs only when sending message for job
activation fails (internal condition), and therefore probability is low.
64 Invalid value in record on View Histories window

Phenomena If View Histories window is displayed, records related to the following
operations contained invalid values (such as LDEV ID: 00:00:00,
Provisioning Type: Basic, Mirror ID/Pool ID/Relationship ID: 0).
- Initialize operation of Shadow Image, Shadow Image for Mainframe,
Snapshot, Compatible Flash Copy version2, Compatible Software for
IBM Flash Copy SE.
- Releasing area with TSE-VOL allocated.
Conditions of Occurrence The problem occurs when records are displayed on View Histories
window after one of the following operations is performed.
(1) Initialize operation of Shadow Image, Shadow Image for
Mainframe, Snapshot, Compatible Flash Copy version2, Compatible
Software for IBM Flash Copy SE.
(2) Releasing an area with TSE-VOL allocated.
Changed Part SVP
65 Failure of TCz pair creation on FC target side after deletion

Phenomena In Preserve Mirror configuration, when a TCz pair volume on the FC
T-VOL side was deleted and then the pair was created again, the
operation failed with SSB=968F output.
(1) Preserve Mirror configuration
(2) TCz pair volume on FC T-VOL side is deleted and then the pair is
created again. (regardless of whether it is a P-VOL or S-VOL of TCz )
Category True Copy for Mainframe, Flash Copy version2
66 Failure of Resync operation with SSB=23FF and 23A7 output
Phenomena When a Resync operation was executed for an SIz pair with MSGREQ
(YES) specified by using a PPRC TSO command, SSB=23FF and
23A7 were output and the operation failed.
(1) A SIz pair is in Pending (However, copy is in process due to
change from Split to Resync) or Duplex status.
(2) CESTPAIR of PPRC TSO command is issued with MODE
(RESYNC) and MSGREQ (YES) specified.
(3) Operation in (2) is repeated and is performed for the fourth time.
Category Shadow Image for Mainframe
67 Wrong status display on History window

Phenomena When a Resync operation was performed to a Copy-on-Write Snapshot
pair and then History window was displayed to confirm the status,
“COPY (RS)” was not displayed but “COPY (RS)/COPY” was
displayed in the Message column.
Conditions of Occurrence The problem occurs when History window of Shadow Image is opened
after a Resync operation to a Copy-on-Write Snapshot pair.
Category Copy-on-Write Snapshot
Changed Part Storage Navigator
68 Failure suspend (PSUE) occurs on TC/TCz

Phenomena Phenomenon 1:
At TC/TCz pair creation, when differential data was managed in track,
SSB=CBBE was output, when differential data was managed in
cylinder, SSB=C435 was output and failure suspend occurred due to
RIO time-out.
Phenomenon 2:
When an update I/O was issued to a TC/TCz pair, SSB=1699 and
D034 were output.
(1) True Copy or True Copy for Mainframe
(2) RCU side
(3) ADD RCU is executed from MCU while there are 6 or more paths
(different physical paths) connected to the same port of RCU.
(4) Path recovery from failures such as link-down of multiple paths is
performed several times.
69 Response delay with SSB=DD08 output
Phenomena SSB=DD08 was output and a response was delayed.
(1) Open host connection
(2) Multiple alternate paths (CHT PCBs are connected with different
ports) are connected to an LDEV.
Causes and Updates New System Option Mode 938 is available to fix the problem.
Restricted Mode – RSD Permission Required to Use

Category Open
70 Display failure on Universal Volume Manager window

After volume migration from an external VOL to a DP VOL by using
Volume Migration, when the volume migration result was confirmed
on Universal Volume Manager window of Storage Navigator, the
LDEV ID displayed was not that after migration but was the one
before migration.
Phenomenon2
In each case of the following operations, the LDEVs added or removed
were not reflected on Universal Volume Manager window.
a. An LDEV is added to a parity group of an external storage to which
LDEVs have already been allocated.
b. LDEVs are removed from a parity group of an external storage;
however, the number of LDEVs left in the parity group is not zero.
Conditions of Occurrence The problem occurs when all the following conditions are met for each
phenomenon.
Conditions for Phenomenon1
(1) Volume migration including the processing for an external VOL is
performed.
(2) Universal Volume Manager window is displayed.
Conditions for Phenomenon2

(1) After LDEV addition or removal from number "n" to number "m",
the number of LDEVs left in the parity group of external storage is not
zero.
(2) Universal Volume Manager window is displayed.
Category Volume Migration, Universal Volume Manager
Changed Part SVP
71 Failure suspend of UR/URz pair with SSB and SIM output
Phenomena When a UR/URz pair was suspended in 3DC multi-target delta
configuration, the suspend turned to failure suspend and SSB=EC01
and SIM=DC1XXX were output.
(1) 3DC multi-target delta configuration
(2) A TC/TCz pair is in PAIR status.
(3) LDEV#0x0000 is not registered in the configuration.
(4) A host I/O is issued.
(5) A suspend operation is executed for a UR/URz pair.
72 No progress for task status on Tasks window

Phenomena On Tasks window of Storage Navigator, display of progress status for
a task did not change after Apply was clicked. The task itself was
completed and ended normally.
Conditions of Occurrence The problem occurs when one of the following operations is executed
for a Mainframe volume on Storage Navigator.
- Format task
- Shredding task
Category Virtual LVI
Changed Part SVP
73 Receipt of incorrect information when sysObjectID in

Standard MIB is obtained
Phenomena When sysObjectID in Standard MIB was obtained, information
different from that described in SNMP Agent User Guide was received
and therefore an icon of RAID was not displayed on JP1.
In particular, described information and received information are as
follows.
Described: 1.3.6.1.4.1.116.3.11.4.1.1
Received: 1.3.6.1.4.1.116.3.11.4.1.1.0
Conditions of Occurrence The problem occurs when sysObjectID in Standard MIB is obtained.
Changed Part SVP
74 Failure of DKC display at UR/URz pair creation
Phenomena At pair creation while selecting an S-VOL that had only one mirror
from a JNL with two mirrors registered, when a pair displayed in
Preview was selected and then Paircreate dialog box was opened again
to modify a parameter, the following phenomena occurred.
(1) A DKC with an already paired mirror was displayed. The DKC was
different from that of the mirror (displayed in Preview) used when
Paircreate dialog box was opened for the first time.
(2) The DKC of mirror was fixed to the above one and could not be
changed to another one to be paired.
(1) A UR/URz pair is created while selecting a pair that has only one
mirror from a JNL with 2 mirrors registered.
(2) Above pair selected in Preview and Paircreate dialog box is opened
Changed Part SVP
75 Abend of data set creation on track without page allocation

Phenomena When a new data set was created on a track without page allocation,
job might end abnormally (abend 614 or 314) and SSB=6709 output.
(1) DP for Mainframe volume or FCSE target volume.
(2) A format write I/O is issued to a track without page allocation.
(3) A CCW chain that searches by a search ID command after
positioning by a set sector command.
(4) A sector number of the above set sector command is 0x06 or higher
and REC#0 is searched.
* I/O that meets above conditions (3) & (4) is not issued by IBM host.
Category Dynamic Provisioning for Mainframe, Flash Copy SE
76 Access failure from host to LUN

Phenomena In non-stop server connection environment, an access from a host to
LUN was disabled after CHA replacement and SSB=B64A was
continuously output.
(1) A host that sets QAM to specify sequence guarantee on DKC side
is connected.
(2) CHT including a port connected with the above host is replaced.
Category Open
77 Failure of micro-program downgrade with SVP message
SMT4002W output
Phenomena Micro-program downgrade after deleting an Incremental Flash Copy
pair was disabled and SVP message SMT4002W was output.
(1) Multiple relationships using Incremental Flash Copy are
established.
(2) Only the Incremental Flash Copy pair is deleted.
(3) Micro-program is downgraded.
Category Flash Copy version2, Flash Copy SE
78 LA error with SSB=A443 output during I/O processing

Phenomena During I/O processing to a DKS2D-H3R0SS drive, an LA error
occurred and SSB=A443 was output.
(1) DKS2D-H3R0SS drives are mounted.
(2) I/O processing is performed.
(3) A read or write command of asynchronous de-staging processing to
the above drive turns to a media failure (SSB=A403).
(4) LBA of the above media failure is 0x100000000h or larger.
79 Write PIN occurrence in HDD

Phenomena When a DKA port was removed during I/O processing while SOM15
or SOM862 was set to ON, write PIN occurred in an HDD under the
DKA port and the following messages were output.
SIM=EF4X-YY, SIM=CF12-XX, SSB=A4C3, SSB=A4CC,

SSB=A4C2
(1) SOM15 or SOM862 is set to ON.
(2) A write I/O is issued.
(3) A port failure occurs between DKA and SSW.
Causes and Updates Microcode modified to fix problem when SOM 15 or SOM 862 is on.
System Option Mode 15: RSD Permission Required to Use
System Option Mode 862: TS Permission Required to Use
Category HDD
80 Temporary pinned slots with SSBs output
Phenomena Due to a conflict of zero data page reclamation and correction copy,
dirty slots remained in an unallocated page and pinned slots might
temporarily occur.
SSB=9CB9, 9F01, 9F80, 9F85, 13AE and 9CF4
(1) Zero data page reclamation is performed.
(2) Correction Copy, Dynamic Sparing, or Copy Back is performed.
Category Dynamic Provisioning, Dynamic Tiering
81 LDEV created with wrong capacity

Phenomena When multiple LDEVs were created by a single operation on Create
LDEVs window of Storage Navigator, an LDEV might be created with
the capacity that was specified for another LDEV.
(1) On Create LDEVs window, a wizard is activated, Basic or External
is selected for Provisioning Type, and multiple LDEVs are selected.
(added to the right table)
(2) Before the wizard is completed, LDEV ID is changed on Change
LDEV Setting window while meeting the following conditions.
(a) The number of LDEVs whose LDEV ID is changed at a time is 2
or more.
(b) An LDEV ID that is specified as an initial LDEV ID before change
is entered.
(c) LDEVs to be changed are in the same parity group.
(d) Among LDEVs to be changed, there is an LDEV whose capacity is
different from others.
(3) Apply is clicked for LDEV creation.
Changed Part SVP

VSP 70-03-40-00-M120

Diunggah oleh

Informasi Dokumen

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

VSP 70-03-40-00-M120

Diunggah oleh

Hak Cipta:

Format Tersedia

VSP

MICROCODE VERSION 70-03-40-00/00-M120

New supported features and functions for Version 70-03-40-00/00-M120

The change of contents for Version 70-03-40-00/00-M120

A. RAID700 All current versions

3 Failure of multiple SSBs output

5 Failure of PDEV replacement/installation after SAS-port or

7 Failure of PDEV/SSW/DKA replacement

8 Error by FC operation or Shadow Image Initialize

10 Failure of CM maintenance if MP is blocked due to WCHK1

11 No display of write I/O "Received"

13 Delay in response due to conflict between I/O and processing

14 Invalid MP Usage rate display

16 Unable to confirm SAS port blockage

17 Repeated link-up and link-down with SIM/SSB output in

19 Failure in option cache PCB replacement

20 SSB=3332 after installation or removal of parity group

22 Registered task disappears

23 Failure of graph display of long-range usage rate

25 Failure suspend of delta UR/URz pair

27 Unable to stop Diagnosis

28 Blockage of MP at offline micro-program exchange or SM

30 Page allocation to inadequate tier

[When the number of tiers is 3]

[When the number of tiers is 2]

32 Failure of filtering Total or Used capacity by cylinder

33 Failure of DKCMAIN micro-program exchange in DKU-less

35 Performance degradation of TC/TCz, UR/URz, LDEV

36 Continuous ICC occurrence during read I/O from host

38 SSB=14DC and 14FF output when external VOL is used

39 Continuous SSB=C470 output at TCz initial copy

41 Inadequate Storage Navigator message

43 No guard of reverse resync operation between I site and R

44 ICC occurrence when MIH occurs in Mainframe

46 Failure of IP address setting

47 Failure of SSW replacement with SSB=4ACX/4A0X output

49 Taking longer time for status transfer at delta resync

51 Unable to decrease JNL usage rate at S-site

52 Failure of FCSE relationship creation, leading to Start

54 Failure of Long Range monitoring data backup

55 Invalid pair status at restore copy for CoW Snapshot pair

57 Unable to correct parameters for UR/URz pair creation

58 Incorrect status display of FCSE pair on Storage Navigator

60 Failure suspension at delta UR pair deletion with SSB and

61 Invalid UR pair status at pair deletion/suspend

64 Invalid value in record on View Histories window

65 Failure of TCz pair creation on FC target side after deletion

67 Wrong status display on History window

68 Failure suspend (PSUE) occurs on TC/TCz

Restricted Mode – RSD Permission Required to Use

70 Display failure on Universal Volume Manager window

Conditions for Phenomenon2

72 No progress for task status on Tasks window

73 Receipt of incorrect information when sysObjectID in

75 Abend of data set creation on track without page allocation

76 Access failure from host to LUN

78 LA error with SSB=A443 output during I/O processing

79 Write PIN occurrence in HDD

SIM=EF4X-YY, SIM=CF12-XX, SSB=A4C3, SSB=A4CC,

81 LDEV created with wrong capacity

Anda mungkin juga menyukai