VSP 70-02-54-00

VSP
MICROCODE VERSION 70-02-54-00/00

RELEASED 08/17/2011
Newly supported features and functions for Version 70-02-54-00/00

1. Mainframe & OPEN System
1-1 Support for CCI configuration report

Description Configuration information report files which are currently obtained from Storage Navigator
can be obtained using CCI. The supported commands are as follows:
raidinf add report (report creation)
raidinf delete report (report deletion)
raidinf download report (report download)
raidinf get reportinfo (report list display)
For syntax on each command, see Appendix B in the Storage Navigator User Guide
Along with the support for deleting report files of configuration information, the condition
to delete report files from Storage Navigator is changed as follows: Before: The user who
has the storage administrator (initial setting) role. If the user does not have this role, he
cannot delete report files that he previously created. After: The user who has created report
files or the user who has the storage administrator (initial setting) role. Regardless of the
role, the user can delete the report files that he previously created.
Changed Part SVP, raidinf (new tool)
1-2 Support for per-PCB battery life warning SIM setting

Description Setting unit of battery life warning SIM is changed as follows.
Versions V02 and earlier: Per system (one setting for a system)
Versions V02+1 and higher: Per CM battery (PCB)
Changed Part SVP
1-3 New window support for external authentication server connection setting
Description New window of Storage Navigator to set connection with an external authentication server
is supported.
Changed Part Storage Navigator
1-4 Support for SIM syslog report

Description When a RAID system failure occurs, it is directly reported to users using syslog.
Syslog server can be set from Setting -> Environment Setting -> Edit SIM Syslog Server
Settings on Storage Navigator.
Changed Part SVP
1-5 Support for 2 TB NL-SAS HDD of 7 Krpm

Description 2 TB NL-SAS HDD of 7 Krpm is supported on Model: DKS2C-H2ROSS with RAID level:
RAID5 (3D+1P, 7D+1P (*1)), RAID1 (2D+2D (*2)), RAID6 (6D+2P)
*1: Two and four-parity group concatenations are supported.
*2: Two-parity group concatenation is supported.
Changed Part DKCMAIN, CONFIG, SVP
HDS Confidential 1 of 107

1-6 Support for BB_Credit virtualization and TC Round Trip reduction
Description For long-distance connection in TC Sync, the following functions are newly supported.
1. BB_Credit virtualization function reduces protocol overhead by virtually using the value
of BB_Credit which considers frame accumulation in long-distance connection. By setting
both Host Mode Option 49 and 50 on MCU and RCU side, the number of BB_Credits can
be increased.
2. TC Round Trip reduction function can transfer data without receiving XFER_RDY from
RCU when MCU sends a command, so that round trip time of frames in long-distance
connection can be reduced. Available by setting Host Mode Option 51 on MCU and RCU
Changed Part DKCMAIN/SVP/Storage Navigator
Note (1) When BB_Credit Virtualization function is used, employ Point to Point connection.
(2) Host connection to the RCU Target port is unacceptable.
(3) The number of MCUs to be able to connect with the RCU Target port is one.
(4) This function cannot be used together with the FCSW function, which transfers data to
the Target side asynchronously by buffering the data in switch.
For example, this function cannot be used together with the Fast Write function of
Brocade Switch or the Write Acceleration function of Cisco Switch.
(5) RCU Target cannot be used for UR.
(6) Target hardware is 8 UFC and 16 UFC. (Initiator, target).
(7) When using the BB_Credit virtualization function, make sure to set SOM 769 to OFF.
(8) Make sure to enable or disable the BB_Credit virtualization/ TC Round Trip functions
after the pair is suspended or when the load is low.
(9) Before downgrading the micro-program to an unsupported version, set HMO 49, 50 and
51 to OFF. For details, see Maintenance Manual (MICRO03-140).
*: The above restrictions apply when HMO 49, 50 or/and 51 are set to ON.
1-7 Support for True Copy OPEN and Mainframe consistency

Description OPEN and Mainframe TC pairs can be registered in the same consistency group.
By issuing pair suspend command with group specified from RAID Manager or Business
Continuity Manager (BCM); all pairs are suspended while the consistency in data between
OPEN pair and Mainframe pair S-VOLs in the same consistency group are guaranteed.
If a failure suspend occurs on MCU side of a consistency group where OPEN and
Mainframe pairs are registered, all pairs are suspended while the consistency in data
between OPEN and Mainframe pair S-VOLs in the same consistency group are guaranteed.
Only True Copy Sync is supported (OPEN/Mainframe)
If group suspend is executed for S-VOL from RAID Manager, only OPEN pairs are
suspended while MF Mainframe pairs are suspended when the operation is done from BCM.
Consistency is guaranteed only in the same DKC. Consistency over different DKCs is not
supported.
Changed Part DKCMAIN, Business Continuity Manager, SVP
Note If OPEN and Mainframe pairs are registered in the same consistency group, the microcode
cannot be exchanged to an unsupported version, or delete the Mainframe pairs in the
consistency group and then exchange the microcode.
1-8 Improvement for dual SVP configuration

Description When SVP is hung-up, Windows kernel memory dump is collected before SSVP turns SVP
OFF and then ON to recover the SVP. In dual SVP configuration; If master SVP is hung-up,
Windows kernel memory dump is collected before failover is executed. If standby SVP is
hung-up, Windows kernel memory dump is collected before SSVP turns SVP OFF and then
ON to recover the SVP.
Changed Part SVP, SSVP
Note Function works when Config version matches supported SVP/SSVP microcode versions.

1-9 Operability improvement of Storage Navigator
Description - Back and Forward buttons are added to menu bar on Storage Navigator main window
Improvement: By storing operation records of tree, the window can be returned or
forwarded using the above buttons.
- Pie chart is improved in Allocation Summary on Storage Navigator main window
Improvement: White line is added for boundary to increase visibility and Alphabets are
assigned to graph and legend to increase accessibility.
- Unit for allocation summary can be specified in Storage Navigator main window
Improvement: Capacity display with unit specified is enabled.
- Top-20 MPB usage rates can be displayed in Performance Monitor
Improvement: For real-time display, when graphs are displayed for each MP, up to 20
operating tasks for each MP PCB can be displayed.
Changed Part SVP
1-10 GUI improvement of DP/DT

Description For a DT pool, the following setting per tier from Storage Navigator is supported.
-Buffer area rate for relocation
-Free area rate for new allocation
Changed Part Storage Navigator
1-11 New storage support

Description As external storage connection, the following storage is supported without profile tool.
FUJITSU storage: DX90/80/60
Changed Part DKCMAIN
1-12 Support for new SIM for pool volume blockade

Description When a pool volume is blocked, a SIM below corresponding to a pool to which the blocked
pool volume belongs is reported.
Changed Part DKCMAIN, SVP
1-13 Support for new CCI commands

Description The following commands are supported.
-raidcom get ldev
The following are added to display item of LDEV information
-OPE_TYPE: Pool in shrinking operation
-TIER_LEVEL: DT Tiering Policies setting (newly added)
-raidcom modify ldev
A parameter to set Tiering Policies when DP-VOL is used is added (-status)
-raidcom get pool
Pool type and status that shrinking is in process when "-key opt" is set are added
-raidcom get dp_pool
Relocation buffer amount and monitoring mode when "-key opt" is set are added.
-raidcom modify pool
A parameter to set monitoring mode and relocation buffer amount is added
-resource option is added to all of raidcom commands
For details on each command, see "RAID Manager Command Reference”.

For details on each PP function, see the corresponding PP user guide.
Changed Part DKCMAIN, RAID Manager

1-14 Change of response watch time for backend processing
Description System Option Mode 862 is available to shorten the response watch time for backend
processing. Restricted Mode – Technical Support Permission Required to Use.
1-15 Support for microcomputer chip for CPC from the 2nd vendor as backup
Description Microcomputer chip for CPC supplied by the 2nd vendor as backup is supported.
The microcomputer chip from the 2nd vendor is a substitute of the current product.
Both microcomputer chips from the current and the 2nd vendor are supported.
The shipping schedule for the 2nd vendor chip is TBD.
1
Changed Part DKCMAIN, SVP, CMBK, CUDG4
1-16 PIN Deletion Tool support for Solaris 10

Description The PIN Deletion Tool is supported for Solaris 10.
2. Mainframe System
2-1 Support for EAV, MF-DP and DVE functions

Description Extended Address Volume (EAV), Dynamic Provisioning for Mainframe, and Dynamic
Volume Expansion (DVE) functions are supported as follows.
1. Supported DKU emulation type:
-EAV and DVE: 3390-A
-Dynamic Provisioning for Mainframe: 3390-A, 3390-V
2. Supported host OS:
-z/OS 1.10 and later (z/OS 1.9+PTF is also supported)
-z/VM 6.1 and later (z/VM 5.4+PTF is also supported)
3. Supported program products:
-Both the normal volume and DP volume can be used as the 3390-A volume.
-True Copy for Mainframe
-Universal Replicator for Mainframe
-Shadow Image for Mainframe
-Compatible Flash Copy V2
-Compatible XRC
- Universal Volume Manager
4. I/O synchronous page discarding is also supported.
5. HDP license can be installed even in the minimum SM configuration
Changed Part DKCMAIN, SVP, Storage Navigator, CLI
Note 1. For TC-MF; If both of MCU and RCU are RAID700, install the supported version on
both MCU and RCU. Pair creation using P-VOL of other than 3390-A and S-VOL of 3390-
A is supported, but the swap operation of P-VOL and S-VOL is unavailable. Pair creation
using P-VOL of 3390-A and S-VOL of other than 3390-A is not supported. Using an EAV
or MF-DP volume to pair with a previous model (RAID500/RAID600) is not supported.
2. For UR-MF; Pair creation using 3390-A and other than 3390-A (such as 3390-3) volumes
is unavailable. 3DC configuration using 3390-A volumes is unavailable.
3. For SI-MF, VM; Pair creation using 3390-A and other than 3390-A (such as 3390-3) is
unavailable.
4. Set SOM 871 to ON before downgrading the microcode from V02+1 or higher to V02
ICS; and set SOM 871 to OFF after the downgrade.
Restricted Mode – RSD Permission Required to Use

2-2 Function Switch#36 to enable time stamp option
Description In TCz/URz cascade configuration, when a TCz Sync pair is created from Storage Navigator
or BC Manager, the timestamp option is enabled, so that the timestamp of host I/O that the
TCz Sync pair receives is sent to the URz pair and the consistency of URz is maintained.
However, in the case of TCz Sync pair creation by PPRC, because the timestamp option
cannot be enabled, the consistency of URz cannot be kept. This function allows timestamp
option to be enabled at TCz Sync pair initial copy/pair resync by PPRC or failback by
enabling Function Switch#36.
Note After microcode exchange, enable Function Switch#36.
In configuration where RCU is RAID500 (earlier than version 50-09-70-00/00), do not
enable the Function Switch#36, or TCz pair initial copy/pair resync by PPRC fails.
3. OPEN System
3-1 Support for resource ID takeover function (Virtual ID function)

Description The resource ID takeover function enables an open host to recognize a new model storage as
an old model storage. In open environment, if an inquiry command is issued from a host, the
response of the old model storage (RAID500, RAID600) is returned in accordance with the
old model storage information set per resource group.
The information to show to the host OS as old model storage is as follows.

Fibre port WWN, Model name, port name, and serial number included in inquiry command.
With implementation of the function, stopping host IO is necessary, but as the host OS
recognizes the RAID700 as an old model storage, OS reboot on the host side and change of
definition for device files are not necessary, so that the down time of the host for storage
migration can be reduced.
3-2 Support for Server Priority Manager GUI

Description The Server Priority Manager setting from Storage Navigator window is enabled.
The Server Priority Manager is a function to set the upper limit of I/O amount, which each
port at front-end can process.
3-3 Support for Tiering Policies per V-VOL in DT

Description Tiering Policies setting is supported. The Tiering Policies setting is a function that enables
users to specify tiers to be used by DP-VOL. For the DP-VOL with Tiering Policies
specified, all pages are allocated to tiers in the Tiering Policies. For example, if tier 1 is
specified for a DP-VOL, DT relocates the DP-VOL pages to the tier 1. In other words, no
matter how low the I/O workload in the page is, the page is allocated to the tier 1.
[Background]
In order to maximize the entire pool performance, DT allocates pages from higher tier
according to relative page ranking based on I/O workload. For this, a page with lower I/O
workload is likely to be allocated to lower tier. Depending on customer environment, there
is data with high importance but low I/O and such data should be allocated to higher tier in
some cases. However, because of low I/O workload, DT allocates the data to tier 2 or tier 3
and the data with low importance and high I/O workload may use tier 1. As a solution for
the above issue, Tiering Policies setting is supported.

3-4 FCoE enhancement (PP combination/Platform)
Description 1. Combination with the following program products when FCoE is used as a I/F for host
I/O is supported. True Copy, Universal Replicator, Volume Migration. Note: Use the Fibre
channel interface as a path for remote connection between TC and UR. FCoE I/F cannot be
used for it.
2. A function to collect a dump of FCoE protocol chip is supported.
Collecting a dump of FCoE protocol chip starts with SIM=2120xx output and completes by
SSB=BCC9 output. After that, a dump of FCoE protocol chip can be collected by
performing a normal dump operation.
3. The following platforms are supported as host connection: OS, CNA, Switch
Changed Part DKCMAIN, SVP, Storage Navigator
3-5 Support for all-page discarding during LDEV format

Description All-page discarding (discarding all of the mapping information between DP pools) during
LDEV format for DP-VOL is supported. System Option Mode 867 is available to enable the
function. Public Mode – No Permission Required to Use
Note Do not change SOM setting during LDEV format for DP-VOL.
Even if the SOM setting is changed during LDEV format, the method of format does not
change but remains as is for the volume being formatted.
3-6 Support for vStorage PP combination

Description [Function 1] The vStorage with the following additional support as follows.
1. Commands: FULL XCOPY and Compare & Write
2. Supported program products: SI , Snapshot, VM , TC , HAM , and HUR
[Function 2] When Host Mode Option 63 is set to ON, the following commands based on
T10 are supported for VAAI (ESX5.0).
1. For TC, HAM, HUR: UNMAP
2. For SI, Snapshot, VM, TC, HAM, HUR:
FULL XCOPY, Compare & Write, RECEIVE COPY RESULTS, READ CAPACITY,
STANDARD INQUIRY, and INQUIRY PAGE B0
Note: Host Mode Option 63 is available to enable the function. Public Mode – No
Permission Required to Use
Note When downgrading the microcode to an unsupported version online, SSB=d334,d33f,d3ca
may be output without causing any problem.
The following commands for Function 1 and 2 are supported only by OPEN-V.
FULL XCOPY, Compare & Write, UNMAP, and RECEIVE COPY RESULTS
3-7 Improvement to keep previous I/O information

Description Previously collected I/O information remains even when the pool configuration is changed
by pool VOL addition.
[Background]
When the pool configuration is changed by pool VOL deletion or addition in the DT
Continuous mode, previously collected I/O information is discarded, which may cause
unnecessary page migration at tier relocation as the trend of previous I/O is not considered.

3-8 RAID Manager/LIB Ver 01-15-03/05
Description Addition of some functions for checking the Resource Group.
Added flag checking resource group
Added EL_EGPERM as return value
Corrected a problem that getjnlstat() may cause a core dump over 16 LDEVs for JNL.
Changed Part RAID Manager/LIB
3-9 RAID Manager 01-25-03/11

Description Support of CLPR# option for making AoU/Snapshot
Support of Tier level for AoU volume
Addition of monitor mode for Pool
Addition of Tier buffer rate for Pool
Added deleting mode for pool
Addition of SSID to the output for querying LDEV
Addition of an option for displaying unassigned host group
Correct a problem “raidcom get ldev” reports PORTs.
Changed Part RAID Manager
3-10 Support for Snapshot combination in UR 3DC delta configuration

Description Snapshot combination is supported at L site or R site in UR 3DC delta configuration.
A Snapshot pair can be created by using a delta volume at L site or R site in UR 3DC delta
configuration as a P-VOL.
Note Release all Snapshot pairs combined with a delta volume at L site or R site in UR 3DC delta
configuration before exchanging the microcode to an unsupported version.
3-11 Support for host group option 59

Description The online device recognition function provided by SOM 717 affects all CHF ports in a
storage system. To provide the same function per port, Host Mode Option 59 is newly
supported. Restricted Mode – Technical Support Permission Required to Use.
Note Perform the following procedure to use this option.
Set System Option Mode 847 to ON.
Set Host Mode Option 59 to ON to the LUN Management window of SVP.
Set System Option Mode 847 to OFF.

The change of contents for Version 70-02-54-00/00
1 SSB=50D3 output during PAV mode switching
Phenomena In Mainframe environment, when switching the PAV mode between PAV
and hyper PAV, SSB=50D3 was wrongly output.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Mainframe environment.
(2) An I/O using PAV is in process.
(3) PAV mode is switched between PAV and hyper PAV from a host.
(4) During the above (3) operation, the processing in (2) is canceled.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-02-54-00/00
Category Compatible PAV
2 Unable to open detailed error information window

Phenomena When a file I/O error or media error occurred during DKU or SCHIP
micro-program exchange, if the Detail button was clicked on Version
window, a window for detailed error information was not displayed in
some cases.
Conditions of Occurrence The problem may occur if a file I/O error or media error occurs during
DKU or SCHIP micro-program exchange.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-02-53/00
Category Open and Mainframe
Changed Part SVP
3 LDEV blockade and disabled access to MCU

Phenomena Under the condition that Fast Write function of Blockade Switch was
used between MCU and RCU in TC-Sync configuration, an LDEV on
RCU side was blocked and access to MCU from host was disabled.
(1) True Copy Sync environment.
(2) Blockade Switch is connected between MCU and RCU and Fast Write
function is used.
(3) LDEV of TC S-VOL is blocked on RCU side.
Causes and Updates New System Option Mode 781 is available to fix the problem.
Restricted Mode – Technical Support Permission Required to Use
Category True Copy

4 Incorrectly completed SSD replacement
Phenomena Replacing* SSD#1 in cache PCB was requested and the SSD#1 remained
removed but the replacement ended normally. (The replacement did not
fail). * SSD alone replacement was supported in V02.
(1) The configuration consists of a certain CMG size and number of
CMGs which allow cache data backup to SSD only using the capacity of
SSD#0. (The configuration that allows cache data backup to work
correctly without SSD#1)
(2) SSD#1 is defined in the configuration.
(3) The replacement is completed without SSD#1 installed.
Affected Products/Version DKCMAIN: 70-02-02-00/00 and higher
5 Unexpected DP pool initialization and failure of SI initialization

Phenomena Phenomenon1: DP pool initialization was executed while any
TC/TCz/UR/URz/SI/SIz/VM/CoW/FCv2 pair that used DP-VOL existed.
(Initialization was not guarded)
Phenomenon2: SI initialization was disabled if any TC/TCz/UR/URz pair

that used DP-VOL existed. (Storage Navigator message: 7005 68814)
Severity (High, Medium, Low) Medium
Phenomenon1
(1) TC/TCz/UR/URz/SI/SIz/VM/CoW/FCv2 pair created using DP-VOL.
(2) DP pool initialization is executed.
Phenomenon2
(1) A pair of TC/TCz/UR/URz/ is created using DP-VOL.
(2) SI initialization is executed.
Affected Products/Version DKCMAIN: All SVP: All
Fixed Product/Version DKCMAIN: 70-02-54-00/00 SVP: 70-02-53/00
Category Dynamic Provisioning
6 SSB=EF50 output and failure suspension of UR pair

Phenomena MP failure during a UR/URz pair restore operation, SSB=EF50 was
output and the UR/URz pair was suspended with failure.
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Open or Mainframe
(2) UR pair or URz pair
(3) Restore is in process. (Initial copy or update I/O is in process)
(4) An MP failure occurs on RCU.
Category Universal Replicator, Universal Replicator for Mainframe

7 I/O stop with SIM=DEA0xx output
Phenomena Quorum disk failure and LDEV format executed to recover the quorum
disk, I/O stopped and SIM=DEA0xx was output.
Conditions of Occurrence Problem may occur when conditions (1) and (2), or (1) and (3) are met.
(1) HAM pair.
(2) LDEV format is executed for a quorum disk.
(3) The data on the quorum disk is overwritten with other data.
Category High Availability Manager
8 Failure suspension with SSB=2A30

Phenomena After an HAM pair failover occurred due to an MCU failure in HAM-UR
cascade configuration, when the MCU was recovered and swap resync
was executed for the HAM pair, the pair once became "PAIR" status but
failure suspension occurred and SSB=2A30 was output.
(1) There is an HAM pair.
(2) MPs are overloaded.
(3) The health check for a quorum disk turns to time-out.
Category High Availability Manager
9 Unable to refresh display information

Phenomena During Quick Format processing, if Refresh All or Refresh View was
executed from Storage Navigator, Storage Navigator message 20123-
107027 appeared and the displayed information was not updated.
Conditions of Occurrence The problem occurs when Refresh All or Refresh View is executed from
Storage Navigator during Quick Format processing.
10 Correction copy delay when Full Speed Mode ON

Phenomena The time of correction copy when System Option Full Speed Mode was
set to ON slowed down by 20%.
(1) Correction copy is executed.
(2) Full Speed Mode is set to ON.

11 Continuous failure of pair creation or reserve VOL creation
Phenomena Due to one of the following errors, SI/VM/CoW pair creation or reserved
VOL creation continuously failed.
- Storage Navigator error [7005 68837]: The command has been rejected
because the specified P-VOL is a volume of Dynamic Provisioning
whose zero data is being discarded.
- Storage Navigator error [7005 68838]: The command has been rejected,
because the specified S-VOL is a volume of Dynamic Provisioning
whose zero data is being discarded.
- Storage Navigator error [7005 68839]: The command has been rejected,
because the specified reserved volume is a volume of Dynamic
Provisioning whose zero data is being discarded.
(1) VXFS (Symantec) * Does not occur if VMWare Write Same is used.
(2) TC/UR pair in PAIR (Duplex) and Write Same is issued to P-VOL.
(3) Before 0 data for Write Same is discarded in S-VOL, the TC/UR pair
is deleted/created.
(4) Using the S-VOL of (3), an SI/VM/CoW pair is created or a reserved
VOL setting is performed.
12 Prolonged periodical processing with SSBs output

Phenomena During dump collection, periodical processing took time due to a delay in
dump collection by OSW control and SSB=10FD/10FE/10FF were
output.
Conditions of Occurrence The problem may occur when a dump is collected.
13 Shadow Image copy stop when write pending rate over 60%
Phenomena Even though workload of a RAID group of copy target LDEV was low, if
write pending rate of CLPR on the copy target was over 60%, Shadow
Image copy was stopped.
Conditions of Occurrence The problem may occur when write pending rate of CLPR to which the
copy target LDEV of Shadow Image pair belongs is over 60%.
Causes and Updates New System Option Mode 855 and the existing System Option Mode 467
are required to be set together to continue the copy processing.
Public Mode – No Permission Required to Use
Category Shadow Image or Shadow Image for Mainframe

14 Output of unrelated SSB in TC/TCz operation
Phenomena In TC/TCz operation, SSB=DD09 might be output along with
SSB=D838/D839.
(1) TC Sync or TCz Sync
(2) A internal logical contradiction (SSB=D838/D839) occurs.
Category True Copy, True Copy for Mainframe
15 Unexpected EPW check after track over run

Phenomena When track over run occurred at the TCz pair creation, the TCz control
information became invalid value. For this, unexpected EPW check
started at the writing on the RCU side.
(1) True Copy for Mainframe Sync.
(2) Track over run occurs during write I/O processing of two or more
records per one slot.
Category True Copy for Mainframe
16 Unable to cancel update copy after receiving SelReset

Phenomena When SelReset was received in the TCz configuration, an update copy
request could not be canceled if EC=8630 was output. In this case, when
the update copy started lately, CHK2 occurred. (EC=B2FF, 8BXX)
(1) True Copy for Mainframe Sync.
(2) A Write I/O issued to the 2nd or later records is received.
(3) The Write I/O is stopped. (abend, reset, or cancel occurs)
Category True Copy for Mainframe Sync

17 Wrongly continued HDD erase at PDEV replacement
Phenomena When PDEV replacement was performed during HDD Erase following
the sparing, a red LED of HDD kept lighting and another green LED of
HDD flashed because the erasing did not stop, and the following SIMs
occurred.
SIM=4C1X-XX (PDEV Erase Start)
SIM=4C3X-XX (PDEV Erase Abnormal End)
*: X-XX is C/R#.
Conditions of Occurrence The problem occurs when PDEV replacement or PDEV removal is
performed during HDD Erase.
Category HDD
18 Invalid scroll box position after clicking Add or Remove on

Add LUN Paths window
Phenomena After Add or Remove was clicked on a wizard window (Add LUN Paths,
etc) of Storage Navigator, which contained two tables located next to
each other, the position of scroll box of the table where an item was
added or removed did not change.
Conditions of Occurrence The problem occurs when Add or Remove is clicked on a wizard window
(Add LUN Paths, etc) which contains two tables next to each other.
Category Storage Navigator
Changed Part SVP
19 Incorrectly active ADD button on Create LDEVs window

Phenomena On the Create LDEVs window of Storage Navigator, the ADD button
was active even no parity group was selected. Under the condition, if the
ADD button was clicked, an error message, "The processing cannot
continue due to an internal logical contradiction” (03022-105149), was
displayed and the processing could not be continued.
Conditions of Occurrence The problem occurs when LDEV size or the number of LDEVs is entered
without selecting a parity group.
Changed Part SVP

20 Delay in decrease of side file usage rate during XRC operation
Phenomena During an XRC operation, even though ownership changed, the side file
usage rate for an MP PCB of side file migration source did not decrease
immediately as expected.
(1) XRC is in use.
(2) MP PCB maintenance, SI pair creation/deletion, or ownership
migration from CCI/Storage Navigator is performed.
21 Non-display of error list on the Task Properties window

Phenomena When a task status after Edit External Volumes executed from Storage
Navigator was shown "Failed", no error list was displayed on the Task
Properties window.
(1) Edit External Volumes is executed from Storage Navigator.
(2) Task status after the above operation is "failed".
Category Universal Volume Manager
Changed Part SVP
22 SSBs output after cache maintenance or a cache failure

Phenomena After cache maintenance or a cache failure, SSBs=DD86, D031, D034,
and 14DD might be output.
(1) After cache maintenance is performed or a cache failure occurs.
(2) An I/O is in process, causing write pending rate to reach about 70%
per CLPR/MPB.

23 Incorrectly changed page display in table on wizard window
Phenomena On a wizard window (Add LUN Paths, etc) of Storage Navigator where
two tables were displayed side by side to select an item from one table
and to add the item to another table, when an item displayed in the second
or later page was selected in one table and Add button was clicked to add
it to the other table, display of the former table was turned to the first
page.
Conditions of Occurrence The problem occurs when the Add button on a wizard window (Add LUN
Paths, etc) of Storage Navigator is clicked while the second or later page
of a table from which an item is selected is displayed.
Changed Part SVP
24 Display of an empty error list after clicking Apply

Phenomena When abend occurred after Apply was clicked on one of the following
Storage Navigator windows, an empty error list was displayed on the
tasks status window and the user could not confirm the root cause of the
abend.
- Delete LDEVs
- Create LDEVs
- Edit LDEVs
- Edit Encryption
Conditions of Occurrence The problem occurs when any of the following operations is executed on
each window and the operation ends abnormally.
(1) Delete LDEVs: DP VOL or CoW Snapshot VOL deletion
(2) Create LDEVs: VOL creation and format, or concurrent VOL creation
and LDEV name setting
(3) Edit LDEVs: Concurrent LDEV name setting and tier relocation
(4) Edit Encryption: Concurrent encryption setting and format
Changed Part SVP

25 Repeated command retry with SSBs output
Phenomena When an I/O is issued to a volume mapped from an external storage by
using UVM, if the response status of other than "GOOD" or "Check
Condition" is received, the threshold of response is controlled and the
volume is blocked. (This is the expected behavior) However, if abnormal
response status is determined prior to controlling threshold and the
command abort is set and reported to the host without the threshold
control, a command retry is executed until reaching the retry threshold of
the host. In this case, SSBs=8932, B236 and 8BF1 are output.
(1) Universal Volume Manager
(2) FCP_STATUS returned for the I/O issued from RAID700 to the
external storage is other than "GOOD" or “Check Condition”.
26 Incorrect CDEV# indicated in SIM (501XYY)

Phenomena In SIM (501XYY) which was output when ORM threshold of SSD was
exceeded, CDEV# (CDEV serial number in the storage system), which is
subject to "X" in the reference code, was different from the actual
CDEV# where the failure occurred.
Conditions of Occurrence The problem occurs when ORM threshold is exceeded in SSD drives
where CDEV# is 0x01 and later.
Changed Part SVP
27 SSBs output at read/write I/O issued to a DP/DT volume

Phenomena In DP/DT configuration, when a read/write I/O was performed to a
DP/DT volume associated with a pool in which internal and external
volumes coexist, SSB=9821, 9F02, 9090, 9C0A, 9848 and so on output.
(1) DP/DT configuration.
(2) Pool volume with internal and external volumes coexist is created.
(3) DP/DT volume associated with pool volume created in (2) is created.
(4) A read/write I/O is issued to the DP/DT volume created in (3).
Category Dynamic Provisioning, Dynamic Tiering

28 Failures caused by disabled access to part of cache
Phenomena After a failure occurred, accesses to part of cache were disabled and the
following phenomena might occur.
(1) In addition to repetitive output of SSB=9C15 and AE63, hung up
might occur.
(2) After repetitive output of SSB=13F2 and 1607, a CHECK response
might be returned to a host for accesses to some volumes.
(3) MIH or EQC might occur during I/O to some mainframe volumes.
Conditions of Occurrence The problem may occur when one of the following conditions is met.
(1) Cache capacity is 128 GB or more.
(2) After one of the following operations, a failure occurs within 30
minutes.
(a) MPB maintenance/failure
(b) LUSE combination/release
(c) SI pair creation/release
(d) CoW Snapshot pair creation/deletion
(e) JNL volume addition/deletion
(f) Ownership migration from CCI/Storage Navigator
29 Inadequate meaning of dialog displayed

Phenomena When Add External Volumes was executed from Storage Navigator,
Discovery Volume processing was executed by clicking the Next button
on the Select External Path Groups window while the window was
changing. The window transfer took long time and a dialog of “Now
Loading…” appeared, but what kind of processing was being executed
was not clear from the dialog.
Conditions of Occurrence The problem occurs when the Next button is clicked on the Select
External Path Groups window at the execution of Add External Volumes
from Storage Navigator.
Causes and Updates The dialog message of "Now loading…" is changed to "Discovering
External Volumes…."
Changed Part SVP

30 Failure of setting items to a mapping policy
Phenomena When an operation of Add External Volume was performed from Storage
Navigator, the following items could not be set to a mapping policy.
- Use External Storage System Configuration
- Number of LDEVs per External Volume
- Processor Blade
Conditions of Occurrence The problem occurs when the Edit Policy window of Storage Navigator is
activated.
Changed Part SVP
31 No display of detailed error information at an error in MP

blade editing
Phenomena When an error occurred during MP blade editing on Storage Navigator,
the task was completed and the detailed error information (20305
76501/20305 78000) was not displayed.
Conditions of Occurrence The problem occurs when an error occurs during MP blade editing such
as an operation on a blocked MP blade.
Changed Part SVP
32 XRC session suspend with SSBs output

Phenomena In XRC operation, XRC session might be suspended and SSB=133C and
1315 might be output.
(1) XRC is in use.
(2) Side file of 128GB or more is created in the MPK.
(3) CMP PCB maintenance is performed.

33 Incomplete display of LDEV information on the Mapped
Volumes window
Phenomena On the Mapped Volumes window for external storages of Storage
Navigator, only one LDEV in the parity group was displayed, but all
other LDEVs could not be displayed.
Conditions of Occurrence The problem occurs when the Mapped Volumes window for external
storage is opened.
Changed Part SVP
34 No display of error message at an error in MP blade editing

Phenomena When an error occurred during MP blade editing from Storage Navigator,
message “Error Occurred.” (20305-xxxxxx) did not occur.
xxxxxx: 7060, 5099, 6012, 6023, 6036, 76500, 76501, 7310 or 78000
Conditions of Occurrence The problem occurs when an error occurs during MP blade editing such
as an operation on a blocked MP blade.
Changed Part SVP
35 Unable to execute monitoring or relocation for pool with

internal logical error
Phenomena Monitoring or tier relocation to a pool whose status was other than
normal could not be executed and an internal logical error (03122-
107007) was displayed on Storage Navigator.
(1) A pool is in shrinking.
(2) Usage rate is 100%.
(3) Either of the following:
- Warning threshold is exceeded.
- Warning threshold and depletion threshold are exceeded.
Affected Products/Version SVP: 70-02-03/00 and higher
Changed Part SVP

36 SSBs output at delta UR deletion in UR 3DC delta
configuration
Phenomena In UR 3DC delta configuration, when a delta UR was deleted, the
processing ended normally but SSB=EC07, EC47, EC1F might be output
frequently.
(1) Universal Replicator, Universal Replicator for Mainframe
(2) TC-UR delta configuration
(3) JNL usage rate at L site is over 70%, or an I/O is issued from a host in
a configuration where command devices are allocated to all mirrors at
each site.
(4) A delta UR is deleted by an operation or is automatically deleted by a
deletion of TC pair or UR pair.
37 SSB=CC08 at cache maintenance during I/O operation on URz

pair
Phenomena When cache maintenance was performed to a URz pair during I/O
operation, the maintenance ended normally though it took time, but
SSB=CC08 was output.
(1) Universal Replicator for Mainframe
(2) Update I/O (overwrite) is executed.
(3) Cache maintenance is performed or one side of cache is blocked.
Category Universal Replicator for Mainframe
38 Unable to recover file system due to issuing read/write I/O to

blocked pool VOL
Phenomena When a read or write I/O was executed to an area of a blocked pool
volume, a file system might be unable to be recovered.
(1) A pool volume is blocked.
(2) A read or write I/O is issued to an area of the blocked pool volume in
(1).
Causes and Updates New System Option Mode 803 is available to fix this problem.
Public Mode – No Permission Required to Use


39 Wrongly completed DP/external VOL removal and abend of
shredding
Phenomena A removal of DP or external volume which was in shredding was not
disabled but completed and the shredding ended abnormally.
Conditions of Occurrence The problem may occur when a DP/external volume which is in
shredding is removed.
Category Universal Volume Manager, Dynamic Provisioning
40 Unable to output pool volume operating information to an

RMF report
Phenomena Operating information per pool volume was not output to an RMF report.
(1) Mainframe connection.
(2) DP-VOL is mounted.
(3) An RMF report is displayed.
Category Mainframe
41 Incorrect display of RAID level on RMF report

Phenomena The RAID type displayed on an RMF report was different from the actual
RAID type.
In particular;
- RAID-5 on the RMF report when the actual RAID level was RAID1.
- RAID-5 on the RMF report in case of an external VOL.
(1) Mainframe connection
(2) There is an ECC group in RAID1, or an external VOL exists.
(3) An RMF report is displayed.
Causes and Updates New System Option Mode 868 is available to display correct RAID levels
on RMF report.
Restricted Mode – Technical Support Permission Required to Use

Category Mainframe

42 Failure of LDEV name setting
Phenomena LDEV deletion was performed from Storage Navigator. Before the
deletion was completed, LDEV name setting was executed for both the
LDEVs where the LDEV deletion was in process and other LDEVs for
which deletion was not performed.
In this case, the name setting for the former LDEVs failed with Storage
Navigator message (3005-78053) as expected. However, the name setting
for the latter LDEVs ended normally but the LDEV names were not set.
(1) LDEV name setting is performed for multiple LDEVs.
(2) Error occurs and LDEV name setting fails in any of above LDEVs.
Causes and Updates The micro-program has been modified to output Storage Navigator
message (3005-5637) when LDEV name setting fails in this case.
Changed Part SVP
43 Display of unnecessary message on EREP after SIM output

Phenomena When Environmental Recording, Editing, and Printing (EREP) was
output after DKC SIM or cache SIM output, the following message was
displayed on EREP.
"IFC264I INVALID INFORMATION FOUND FOR DASD OBR
CODE 2024 IN RECORD"
(1) DKC SIM or cache SIM is output.
(2) EREP is output on a Mainframe host.
Category Mainframe
44 Unable to display LDEV Status window

Phenomena When displaying LDEV Status window was requested from DXRay, if
there was an LDEV for which any of the operations; format, quick
format, verify, or shredding, was executed, the LDEV Status window
could not be displayed.
(1) Displaying LDEV Status window is requested from DXRay.
(2) There is an LDEV for which format, quick format, verify, or
shredding (*) is executed.
* Any of the operations cannot be executed offline. But the configuration
information collected from a RAID700 shows that any of the operations
is being executed.
Changed Part SVP

45 Lack of explanation for next operation in text box
Phenomena On Select External Path Group window of Add External Volumes wizard
of Storage Navigator, as no explanation for the operation was displayed
in a text box to display Path Group ID, it was difficult to understand what
to do next.
Conditions of Occurrence The problem occurs when Select External Path Group window of Add
External Volumes wizard is displayed.
Changed Part SVP
46 SSB=9B31 output at Correction Copy, Drive Copy or Verify

Phenomena When Correction Copy, Drive Copy or Verify was executed for an ECC
group of SSD drives, SSB=9B31 was output.
(1) Correction Copy, Drive Copy or Verify is executed.
(2) ECC group for the above operation is executed using SSD drives.
(3) There is more than one DKA pair.
47 No display of item for DATA TRANSFERS

Phenomena At LISTCOUNT job execution, the item of "DATA TRANSFERS" was
not displayed.
Conditions of Occurrence The problem occurs when an I/O is issued from a Mainframe host.
Category Mainframe
48 Incorrect error message display at CHA replacement

Phenomena When 16FC CHA was replaced with 16UFC CHA, an SVP error message
[ONL2788E] showing "Error response from DKC" appeared instead of
[ONL3713E] showing "The PCB(s)(%s) could not be restored because
the PCB type is incorrect".
(1) A maintenance operation is performed on CHA or DKA.
(2) The above CHA or DKA is replaced or installed.
(3) A type of PCB different from the above is installed.
Changed Part SVP

49 Additional SM accesses in purge processing
Phenomena Additional SM accesses were executed in purge processing of UR.
(1) Universal Replicator or Universal Replicator for Mainframe
(2) A UR pair is in PAIR status.
(3) There is an I/O from host.
50 Incorrect response time output by Export tool

Phenomena When a write I/O was issued to an LDEV without read I/O, the response
time of read I/O output by the Export tool was 0 instead of "-3" (invalid
value in case of no I/O). On the contrary, when an read I/O was issued to
an LDEV without write I/O, the response time of write I/O output by the
Export tool was not "-3" (invalid value in case of no I/O) but "0".
Conditions of Occurrence The problem occurs when the Export tool is used while the collected data
of option monitor is under the following condition.
- There is no read I/O and one or more write I/Os, or there is no write I/O
and one or more read I/Os.
Category Performance Monitor
Changed Part SVP
51 “All 0” report or MLRC error at pair status collection after a

planned power cycle
Phenomena When a pair status was obtained using a route list without any operation
from BCM after a planned power cycle (SM non-volatile), “All 0” was
reported to BCM or an MLRC error occurred with SSB=4B4F output on
the P site.
(1) 2DC or 3DC configuration
(2) A planned power cycle (SM non-volatile) is performed.
(3) Pair status is obtained using a route list without any operation from
BCM after (2).
Category True Copy for Mainframe, Shadow Image for Mainframe, Universal
Replicator for Mainframe

52 Incomplete status of SIM=624000
Phenomena When SIM=624000 was reported, Complete SIM was executed from
Storage Navigator but the SIM status did not turn to Complete.
(1) SIM =624000 is reported.
(2) Complete SIMs is executed from Storage Navigator.
Changed Part SVP
53 Wrong output of SSB=23FF at volume migration

Phenomena When Volume Migration was performed from Storage Navigator,
SSB=23FF was wrongly output.
(1) Multiple migration plans executed at one time from Storage NAV
(2) A plan in which a virtual volume of Dynamic Provisioning is
specified as a migration source is included in the migration plans of (1).
(3) The migration plan of (2) fails.
Category Volume Migration
54 Response delay and SSB output at pair operation or pair status

collection
Phenomena When a pair operation or pair status collection was performed using a
route list from BCM, the response might unexpectedly be delayed for a
maximum of 30 seconds, and SSBs=EBD7 and EBAD were output
several times at the L or R site.
If a response is returned to a host and the host time-out is set to 45
seconds (if BCM is used, the time-out needs to be set to 45 seconds), the
above phenomenon does not affect the host.
(1) 2DC or 3DC configuration.
(2) A planned power cycle (SM non-volatile) is performed.
(3) Pair status is obtained using a route list without any operation from
BCM after (2).
(4) After (3), a pair operation or pair status collection is performed using
the route list from BCM.
Category True Copy for Mainframe, Shadow Image for Mainframe, Universal
Replicator for Mainframe

55 Failure of decoding encryption license key
Phenomena If Normal Format/Quick Format/LDEV addition was executed with
wrong encryption license key information, the format was performed
based on the wrong information and decoding by a correct key failed.
(1) Encryption key information is wrong.
(2) Any of the following operations is performed.
(a) Normal Format
(b) Quick Format
(c) LDEV addition
Category Encryption License Key
56 Wrong output of SSB=9C61 at drive blockade

Phenomena SSB=9C61 was wrongly output at drive blockade.
(1) SOM031 is set to ON.
(2) Correction Access is in progress.
(3) RAID5 or RAID6
57 Wrong re-output of SSB=620XXX for warning threshold

exceedance
Phenomena SIM=620XXX (XXX indicates a pool ID), which was supposed to be re-
reported again when DP/DT pool usage rate continuously exceeded the
warning threshold for 8 hours, was re-reported within 8 hours.
(1) SOM734 is ON.
(2) DP/DT pool usage rate continuously exceeds the warning threshold.
(3) SIM=620XXX (XXX indicates a pool ID) reported when the usage
rate exceeds the warning threshold is completed.

58 Wrong output of SSB=625000 for depletion threshold
Phenomena SIM=625000, which was supposed to be output when DP/DT pool usage
rate continuously exceeded the depletion threshold for 8 hours, was
output within 8 hours.
(1) SOM734 is ON.
(2) DP/DT pool usage rate continuously exceeds the depletion threshold.
(3) Any of the following operations is performed.
(a) Off-line micro-program exchange
(b) Planned stop of the storage system
(c) Power cut of the storage system
59 Abend of path inline processing with SSBs output

Phenomena Inline (A3) ended abnormally and SSB=1C00, A730, A659 were output.
(1) Path Inline (A3) is executed.
(2) An HDD in abnormal state due to an individual failure etc is mounted.
Category HDD
60 Long processing time of path inline (A3)

Phenomena In configuration with the maximum number of DKCs, the processing time
of path inline (A3) was long.
Conditions of Occurrence Problem occurs in configuration with large number of HDDs mounted.
Category HDD
61 WCHK1 and SSB=32FE occurrence during LDEV format

Phenomena During LDEV format, WCHK1 and SSB=32FE might occur.
Conditions of Occurrence The problem may occur when any of the following processing is executed
after SSB=9C89 is output.
(1) LDEV format
(2) Quick format
(3) Sequential write

62 Command reject after executing for 1281 or more times
Phenomena When the following commands were executed for 1281 or more times
from CCI, SSBs = 2EE8 and 00EE were output and the command was
rejected.
(1) raidcom delete ldev
(2) raidcom initialize ldev
Conditions of Occurrence The problem may occur when the following commands are executed for
multiple LDEVs (more than 1280 LDEVs).
(1) raidcom delete ldev (LDEV deletion)
(2) raidcom initialize ldev (quick format)
63 4E retry of CC or session suspend of XRC

Phenomena During Concurrent Copy (CC) or XRC operation, SSB=138A was output
and CC turned to 4E retry or XRC session was suspended.
(1) CC or XRC is executed.
(2) MPB maintenance.
Category Mainframe
64 CHK3 occurrence with SSBs output (without blockade)

Phenomena When ESW was removed along with DKA removal, CHK3 occurred.
In this case, SSB=3250 and 3251 were output but no blockade occurred.
(1) I/O overload
(2) Maintenance with ESW removal or ESW replacement
65 All ports blockade when invalid setting value is detected

Phenomena When LRP detected an invalid setting value for the Tachyon chip (invalid
frame detection), all ports on a PCB where the failure was detected were
blocked.
Conditions of Occurrence Problem occurs when an invalid Tachyon chip setting value is detected.
Category Open

66 SSBs output at I/O to UR P-VOL
Phenomena When an I/O was issued to a UR P-VOL, SSB=D031, D034, DE4D and
DE4E were output.
(1) UR P-VOL is in SUSPEND status.
(2) Inflow control mode.
(3) A write I/O is issued.
(4) Pair resync is executed.
Category Universal Replicator
67 Frequent SSB=A466 output at CHK3 or LA error with

SSB=A443
Phenomena When CHK3 occurred (SSB=3250), SSB=A466 (access is disabled due to
post-processing for LA error) was frequently output.
If any SATA HDD was mounted, a LA error occurred one time at drive
reading and SSB=A443 was output.
* The LA error did not occur many times.
Conditions of Occurrence The problem may occur when CHK3 occurs, which does not lead to a
blockade of logical path between DKA and MP.
(The case that SSB=3250 is output but not SIM=33xx-xx)
Category Open of Mainframe
68 Storage Navigator display failure such as incorrect page status

Phenomena (1) When 0 data page discarding was executed, the page status on Storage
Navigator was not "Reclaiming Zero Pages".
(2) Configuration changes made from Storage Navigator, SVP, CCI or
HDVM was not reflected on Storage Navigator window.
(3) Refresh View or Refresh All was executed from Storage Navigator,
Storage Navigator message [20123-107027] appeared.
Conditions of Occurrence The problem may occur when any of the following operations is being
executed.
(1) 0 data page discarding.
(2) Write Same.
Changed Part SVP

69 Incorrect order display of LDEVs with the same MP operating
rates
Phenomena In the rank order of LDEVs whose MP operating rates were the same, an
LDEV with Backend kernel was placed higher than that with Open-target.
When the MP operating rates were the same, LDEVs should be ranked
according to kernel type from Open-Target, Open-External, Open-
Initiator, Mainframe-Target, Mainframe Initiator, Backend to System in
that order.
Conditions of Occurrence The problem occurs when collected MP data of option monitor data is
displayed in graph on Performance Monitor window of Storage
Navigator, or the data is output by Export tool while "group PhyMPPK"
command is active in configuration where MPs are mounted.
Changed Part SVP
70 XRC pair suspension and SSBs output due to CHK2 after

receiving CCW chain
Phenomena After a CCW chain command was received, CHK2 occurred, SSB=3289,
3570, B2FF, B21B, 5871, B2C8, 481E and 4732 were output, and an
XRC pair was suspended.
(1) Compatible XRC
(2) A write up data command or write up key and data command, which
can write data to record0 and record1 (key length =0, data length =8) by
the same CCW chain, is received.
Category Compatible XRC
71 Failure of DP-VOL format with SSB output after slot busy

Phenomena During DP-VOL format, slot busy occurred (SSB=7B5D). After that,
Destaging might end abnormally (SSB=7B97), and then the format might
fail (SSB=7B0A).
(1) External and internal pools coexist.
(2) DP-VOL format is executed.
Category Open

72 Incomplete pair status change at snapshot data collection
Phenomena When snapshot data was obtained using At-Time Snapshot function,
some pairs whose pair status could not be changed remained in a
consistency group and SSB=9721 was output.
(1) Snapshot data is obtained using At-Time Snapshot function.
(2) The license expires before the status of all pairs in a consistency group
changes completely.
Category Copy-on-Write Snapshot
73 Unable to log into Storage Navigator after repeated log-out

Phenomena After log-out from Storage Navigator in a way different from normal
logout, such as clicking "x" button in the upper right of browser, was
repeated, login to Storage Navigator failed. Even after 10 minutes which
was time-out time, login was still disabled.
(1) Login, logout and then login Storage Navigator fails.
(3) Logout in a way different from normal logout, such as clicking "x"
button in the upper right of browser, is repeated.
Category Open
Changed Part SVP
74 Memory volatilization at storage activation with SIM and SSB

output
Phenomena At offline CM DIMM replacement, if a DIMM whose type was different
from the configuration information was wrongly mounted even in one
cluster, the storage system was activated with memory volatilized and
SIM=FFE8-00 and SSB=15A7 were output.
Conditions of Occurrence The problem occurs when the storage system is activated while the
configuration definition and the type of mounted DIMM are inconsistent.

75 Incorrect display of progress status after communication error
Phenomena When a communication error between SVP and DKC occurred during
DKU, SSW or Expander micro-program exchange, "Transfer to physical
device" on a window to display the progress status was over 100%. 30
minutes after that, the micro-program exchange ended abnormally.
Conditions of Occurrence The problem occurs when a communication error between SVP and DKC
occurs during DKU, SSW or Expander micro-program exchange.
Changed Part SVP
76 Delay of low workload I/O response

Phenomena Due to a delay of XRC RSCB deletion (2 msec), low workload I/O
response of SEQ-UPWRITE (BLK=26KBx5 (A5 command x 5)) became
slower than that of RAID600 (version V08).
Conditions of Occurrence The problem may occur when an XRC pair exists.
77 Pair status remaining in COPY or MCU JNL full

Phenomena When a failure slot occurred in a UR volume, SSB=D2B7 and D346 were
output and the UR pair status remained in COPY, or UR journal copy
stopped and a journal on MCU became full.
(1) UR MCU.
(2) A failure slot occur in a volume used by UR.
78 Unable to log into Storage Navigator

Phenomena During an operation on Storage Navigator, a Storage Navigator error
message [20121-107022] was displayed and Storage Navigator was
terminated. After that, login to Storage Navigator was disabled.
Conditions of Occurrence Problem may occur with the following operations executed in order.
(1) SVP micro-program is installed.
(2) At 20 minutes after SVP reboot, SVP mode is changed from Modify
mode to View mode.
Changed Part SVP

79 Unintentional wait dialog display
Phenomena When battery change was executed on SVP Maintenance window, a wait
dialog appeared on the right bottom corner.
Conditions of Occurrence The problem occurs when battery change is executed.
Changed Part SVP
80 WCHK1 resulting from loop CHK3 due to unidentified failed

part
Phenomena When a failure in SW was detected, the failure part could not be
identified in rare cases, which caused CHK3 loop resulting in WCHK1.
In this case, SIM=3080 or 3073 was output.
Conditions of Occurrence The problem may occur in rare cases when a failure in SW is detected.
81 No output of SIM for failure

Phenomena When an ESW PCB failure or X-path cable failure was detected at
power-on, a SIM for the failure was not output. (SSB=3560 was output)
Conditions of Occurrence The problem occurs when an ESW PCB failure or X-path cable failure is
detected at power-on.
82 Enable to delete a LU in host I/O processing or a reserved LU

Phenomena When LU deletion was executed from Raid Manager for an LU which
was in host I/O processing, the LU was deleted. LU deletion for a
reserved LU was enabled too.
Conditions of Occurrence The problem occurs when LU deletion from Raid Manager is executed
for an LU which is in host I/P processing or for a reserved LU.
Category Open

83 SSB output in TC Sync operation
Phenomena TC or TCz operation, SSB=14E6, DF12, D160, D036, D099 may output.
(1) True Copy or True Copy for Mainframe.
(2) UA is detected in TC S-VOL.
(3) An error (such as disconnection, implicit logout) is detected in
transfer processing of check condition due to UA.
84 PIN error and LDEV blockade

Phenomena During a TC pair resync operation, LDEV blockade and PIN errors
occurred in a raid-group consisting of SSDs (Solid State Disk). SSB =
C45B was output.
(1) P-VOL of True Copy for Open or Mainframe.
(2) A temporary drive failure occurs and the data cannot be read even by
correction read.
(3) Initial copy or resync is executed.
Category True Copy, True Copy for Mainframe.
85 Incorrect error judgment leading to failure of CMG blockade

Phenomena While a failure DIMM where uncorrectable error and correctable error
occurred in the same CMG was mounted on a cache PCB, if PS-ON was
performed, a failure was detected by diagnosis but it was determined as a
correctable error and CMG was not blocked. SIM=760400 and
SSB=3306 were output.
(1) A failure DIMM where uncorrectable and correctable errors occur in
the same CMG is mounted on a cache PCB.
(2) PS-ON is performed.

86 Unable to activate SVP launcher
Phenomena When logging into SVP from Remote Desktop, Storage Navigator SVP
launcher might not activate.
(1) Access to SVP launcher activation setting file set to Windows registry
is disabled because the file is deleted or other reasons.
(2) Log-in to SVP from Remote Desktop
Changed Part SVP
87 WCHK1 in all MPs

Phenomena At PS-ON, WCHK1 might occur in all MPs.
(1) PS-ON.
(2) A correctable error occurs in CMMG used as Cm Dir/CM.
88 Failure suspension causing all differential data copy

Phenomena When any operation, cache replacement (maintenance), or a power cycle
(nonvolatile) was executed for UR while a PIN occurred in a journal
volume, failure suspension occurred with SSB=EDDD output causing all
differential data copy.
(2) Journal group status is other than Initial and Stop.
(3) A PIN occurs in a journal volume.

89 SSB=5348 at the MP PCB dummy replacement
Phenomena When MP PCB dummy replacement was performed while an I/O was
issued to a DP-VOL of a pool consisted of external volumes, SSB=501F
(Time-over of Sync command JOB) and 505F (No ownership when
restarted) were output, and then SSB=5348 (Information complementing
SSB for DAK not transmitted at WaitSENSE migration) was output.
Conditions of Occurrence The problem occurs when SSB=501F and 505F occurs.
Category Mainframe
90 Unable to delete pool VOL (shrink) with SSB output

Phenomena Pool VOL deletion (shrink) might be disabled and SSB=AF0D was
output.
(1) DP pool or DT pool.
(2) Multiplying the number of pages of maximum pool VOL capacity by
the number of allocated pages in the pool is larger than 0xFFFFFFFF
pages.
* Page calculation:
Open-V: 42 MB/page
Mainframe: 38 MB/page
Category Dynamic Tiering
91 Failure of DP-VOL deletion with Storage Navigator message

Phenomena When DP-VOL deletion was executed, Storage Navigator message [3205
2011] appeared and DP-VOL deletion failed.
(1) DP-VOL
(2) TC or HAM P-VOL.
(3) The pair status is PAIR or COPY.
(4) Host I/O is being executed.
(5) A swap operation for P-VOL and S-VOL is performed.
Category Dynamic Provisioning, True Copy, High Availability Manager

92 SSB=EC84 output at SPLIT operation
Phenomena When SI was combined with UR pair S-VOL and SPLIT was executed,
SSB=EC84 was output at UR S-VOL.
(1) UR pair in PAIR or Duplex status.
(2) Update I/O is issued to UR P-VOL.
(3) SI pair (or CoW) is combined with UR S-VOL.
93 UR pair status remaining after power cycle or offline micro-

program exchange
Phenomena When a UR pair was suspended in Duplex status or during pair deletion,
or failure suspend processing, PS-OFF/ON or offline micro-program
exchange was executed on RCU side, the UR pair status remained
Suspending or Deleting.
(2) While a pair is in Suspending status by a suspend operation or due to a
failure, or is in Deleting by a pair deletion operation, either (a) or (b)
below is performed.
(a) After performing PS-OFF for RCU, SM volatile or nonvolatile PS-
ON is performed.
(b) Online micro-program exchange on RCU side.
94 Display remaining of MP Reboot window

Phenomena When MP Reboot window displayed during DKCMAIN or RAMBOOT
micro-program exchange was continuously moved by clicking mouse, the
MP Reboot window might remain displayed after the completion of MP
reboot processing.
(1) DKCMAIN or RAMBOOT micro-program is exchanged.
(2) MP Reboot window is continuously moved by clicking mouse.
Changed Part SVP

95 SSB=3300 output at abend of micro-program exchange
Phenomena If SSW or Expander micro-program exchange ended abnormally due to
an SSW hardware failure, SSB=3300 was output.
Conditions of Occurrence The problem occurs when an error occurs in SSW during SSW or
Expander micro-program exchange.
Changed Part SVP
96 Failure of maintenance or SI pair operation after failure reset

Phenomena After a failure reset, SSB=15B9 was output and cache, LDEV, or PDEV
related maintenance or an SI pair operation failed.
Conditions of Occurrence The problem may occur when a failure reset occurs after the following
operation (1) or (2) is performed.
(1) Cache, LDEV or PDEV related maintenance.
(2) SI pair operation. * Problem occurs when a failure reset occurs in a
specific program step during queue operations on job management areas.
97 Failure of pool shrink operation with SSB=AF0D output

Phenomena When a pool shrink operation was executed from Storage Navigator,
Storage Navigator message [0305 078043] appeared, and the operation
failed with SSB=AF0D output.
1. 0 data discarding is executed.
2. 0 data discarding is stopped.
3. Rebalance (pool expansion, pool shrink, or tier relocation) is activated.
98 Continuous SSB=AF01 output after Define Configuration

Phenomena After online Define Configuration, SSB=AF01 was continuously output
at a minute interval.
(1) Maintenance and Provisioning setting is performed from SVP.
(2) Within a minute after the above operation, online Define
Configuration is executed.
Changed Part SVP

99 Failure of TC pair creation with SSBs output
Phenomena When a TC pair was created in N_port connection, the creation failed and
SSB=D9A7 and D985 were output from RCU.
(1) N_port connection
(2) TC pair configuration where MCU is RAID700 and RCU is
RAID600.
(3) Any of the following is executed or occurs while a path is established.
(a) Link down
(b) PS-OFF and then PS-ON
(c) CHT replacement
(d) Offline micro-program exchange
Category Open
100 Unchanged UR pair status

Phenomena In UR Open MxN configuration, when Group Deletion was requested
from Raid Manager for a JNLG where UR pairs in PSUS status and UR
pairs in PAIR or COPY status coexisted, the status of UR pairs which
was in PAIR or COPY status remained Deleting.
(1) Universal Replicator
(2) Open MxN configuration
(3) In the same JNLG, UR pairs in PSUS status and UR pairs in PAIR or
COPY status coexist.
(4) From Raid Manager, Delete per group is requested for the UR pairs in
PSUS status. (The top pair in Config file of Raid Manager is in PSUS
status)
101 Unable to identify failed drive on Maintenance window

Phenomena Due to a temporary drive failure when performing PS-ON, if drive
activation failed, the failed drive could not be identified on SVP
Maintenance window and SSB=1C00 was output.
Conditions of Occurrence The problem occurs when obtaining an ID of a failed drive fails at PS-
ON.
Category HDD

102 Failed operation from Storage Navigator due to SVP reboot
Phenomena In a time period of SVP periodical reboot, SVP was rebooted even though
an operation from Storage Navigator was in process and the operation
failed.
Conditions of Occurrence The problem occurs when any operation is performed from Storage
Navigator during SVP periodical reboot processing.
Changed Part SVP
103 Unable to record and report SIM log files due to access error
Phenomena An access to SIM log files failed and the SIM log record and report were
disabled.
Conditions of Occurrence The problem occurs when an access to SIM log files fails.
Changed Part SVP
104 LA error and possible PDEV blockade due to JNL VOL

deletion during quick format
Phenomena When a journal VOL in quick format processing was deleted from a
journal group, an LA error occurred and PDEV might be blocked.
(1) Universal Replicator for Mainframe, and the journal VOL is
Mainframe emulation VOL.
(2) While the status of UR pair is COPY or PAIR, Purge Suspend is
executed or failure suspension occurs.
(3) A journal VOL in quick format processing is deleted.
105 Abnormality of Flash time-out error dialog

Phenomena On Storage Navigator Main window, a dialog of Flash time-out error
(20121-107096) could not be fully displayed.
Conditions of Occurrence The problem occurs when a Flash time-out error (20121-107096) occurs.
Changed Part SVP

106 Incorrect message display at volume migration
Phenomena If a TC secondary volume (S-VOL) in Pending status was selected as a
migration source VOL on Volume Migration window of Storage
Navigator, and then Volume Migration was executed, a Storage
Navigator error occurred as expected, but the message [5205 5506]
displayed was not correct.
5205 5506: The specified volume cannot be migrated because it is used

as P-VOL in the following status.
- A volume of True Copy or True Copy for Mainframe in the Pending
status.
(1) TC S-VOL in Pending status is selected as a migration source VOL.
(2) Volume Migration is executed.
(3) An error occurs.
Causes and Updates The micro-program has been modified to display the correct message
[5205 5504].
5205 5504: The specified volume cannot be migrated because it is used as

S-VOL in the following status.
- A volume of True Copy or True Copy for Mainframe in the Pending
status.
Changed Part SVP
107 Time-out error and unintentional SVP reboot 30 minutes after

pool creation
Phenomena 30 minutes after pool creation on Create Pools window of Storage
Navigator, a time-out error, Storage Navigator message [0004 6001],
occurred and SVP was rebooted.
Conditions of Occurrence The problem occurs when the following condition is met.
Pool creation takes more than 30 minutes. (The time required for pool
creation varies depending on the number of pools to create and the
number of logical devices to be selected)
* Even a time-out error occurs, the actual pool creation continues on
DKC side and pools created do not have any problem.
Changed Part SVP

108 Incorrect message displayed at encryption setting
Phenomena If an encryption setting was made on Edit Encryption window while
blocked and not blocked parity groups coexisted, a Storage Navigator
error occurred as expected but the message [3005 68786] displayed was
not correct.
[3005 68786] The specified parity group is not blocked.

Conditions of Occurrence The problem occurs when an encryption setting is performed while
blocked and not blocked parity groups coexist.
Causes and Updates The message [3005 68786] is modified as follows.
A parity group that is not blocked is included in the specified parity

groups.
Category Encryption License Key
Changed Part SVP
109 Incorrect value output by RMLIB command

Phenomena When an RMLIB command to output system status was executed from a
host, the output value of rminfo (DKC-CACHE) CMB of write pending
data was larger than the actual value.
Conditions of Occurrence The problem occurs when an RMLIB command below is executed on the
host.
- test_getrminfo_DKC_CACHE dsp_on
110 Disabled FCv2 pair operation after pair suspend due to failure
Phenomena If a failure occurs during FCv2 operation, FCv2 pair in process was
suspended, and the following operation of the pair was disabled.
(SSB=9680 and 9694)
(1) Mainframe
(2) FCv2 Establish or Withdraw command is being processed.
(3) The above command processing is stopped (a failure occurs)
Category Compatible Flash Copy V2

111 Delay in rebalance processing
Phenomena Rebalance processing delayed.
Due to the above delay, when pool shrink was executed from Storage
Navigator, the task status seemed not to make progress.
Conditions of Occurrence The problem may occur when rebalance processing (pool expansion, pool
shrink, and tier relocation) is executed.
* In particular, the problem likely occurs if an I/O is issued to a rebalance
target DP-VOL or if cache load is high.
112 Drive blockade due to continuous Check Condition occurrence

Phenomena During I/O processing, if Check Condition [01/00xx], [01/1D00], and
[01/40xx] occurred sequentially, a drive was blocked.
In this case, SSB=A401 and A434, and SIM=EF1X-xx were output.
Conditions of Occurrence The problem occurs when a drive failure occurs during I/O processing.
Category HDD
113 Incorrect SSBs output at virtual VOL creation by CCI

command
Phenomena At creation of a virtual VOL for DP by a CCI command,
(1) If a pool ID for CoW Snapshot was specified, an error occurred as
expected but SSBs output (2EFF and FFFF) were incorrect.
(2) If a pool ID for an un-mounted pool was specified, an error occurred
as expected but SSBs output (2E10 and 6014) were incorrect.
Conditions of Occurrence The problem occurs when the following condition (1) or (2) is met.
(1) At virtual VOL creation for DP by a CCI command, a pool ID of
CoW Snapshot is specified after -pool option.
(2) At virtual VOL creation for DP by a CCI command, a pool ID of an
un-mounted pool is specified after -pool option.
Causes and Updates The micro-program has been modified to output the correct SSBs in each
case.
(1) SSB=2E30 and 6003 are output instead of 2EFF and FFFF
(2) SSB=2E20 and 6000 are output instead of 2E10 and 6014

114 Inadequate SI consistency rate
Phenomena The consistency rate of Shadow Image for Mainframe pair in Duplex
status did not become 100%.
(1) A write I/O is issued to an SI/SIz pair.
(2) The pair status is as follows.
(a) PAIR in case of Shadow Image
(b) Duplex in case of Shadow Image for Mainframe
Category Shadow Image, Shadow Image for Mainframe
115 Frequent SSB=3B07 output at time-out occurrence

Phenomena If time-out occurred before completing initial setting for PCB Rev
collection, SSB=3B07 was frequently output.
1. Operating MP PCB removed and mounted w/o maintenance operation.
2. Any of the following operations is executed.
(a) PCB Rev window is opened from Maintenance window.
(b) Auto Dump is executed with Normal Dump selected.
(c) PCB maintenance is performed.
116 SSB=9C4A output and incomplete read I/O

Phenomena True Copy configuration, SSB=9C4A output and incomplete read I/O.
(1) True Copy
(2) TC P-VOL is a DP-VOL and an external volume.
Category True Copy
117 Memory leak at LDEV nickname reference

Phenomena Memory leak (about 2 MB) occurred while viewing LDEV nicknames.
Conditions of Occurrence The problem occurs when either of the following conditions is met.
(1) An LDEV nickname is set or changed.
(2) All Refresh is executed.
Changed Part SVP

118 I/O interruption with SSB=BC4F output
Phenomena During I/O processing, when an MP failure occurred, the I/O partially
stopped and SSB=BC4F was output.
Conditions of Occurrence The problem occurs when one of the following conditions is met.
(1) MP PCB is removed.
(2) An MP failure occurs.
* The problem occurs if link down or link up occurs due to the above
operation or failure, and a reset at link down is executed after receiving
Port Database Changed.
Category Open
119 I/O interruption with SSB=BC3B output

Phenomena During I/O processing, if a cache error was executed, the I/O stopped
partially and SSB=BC3B was output.
Conditions of Occurrence The problem occurs when any of the following conditions is met.
(1) A cache failure
(2) An ESW failure
(3) A CHF PCB failure
* The problem may occur if any above failure occurs and data transfer
stops due to a CHK2 failure.
Category Open
120 Pair suspend with SSB output at pair status change

Phenomena When pair status change was executed in TC configuration, the pair was
suspended and SSB=86D2 was output.
(1) Any of TC, UR and UVM configurations
(2) I/O processing of external port or MCU is reset. (*)
(3) The Exchange# to be reset is the same one used by the same MP.
In the above condition, the response to the reset I/O is received.
* In host target port which uses TC/UR VOL or external VOL, transfer
time-out occurs, or time-out for response waiting or ABTS response
waiting occurs in TC/UR or external path,
Category True Copy, Universal Replicator, Universal Volume Manager

121 Abend of concurrent copy or suspend of XRC pair creation
Phenomena When an external VOL in concurrent copy or XRC pair creation
processing was deleted, SSB=477E was output, and the concurrent copy
ended abnormally or XRC pair creation processing was suspended.
Conditions of Occurrence The problem occurs when an external VOL is deleted during concurrent
copy or XRC pair creation.
122 Possible MIH occurrence with SSB=1602 output

Phenomena When an update I/O was executed for an FCv2 source volume (S-VOL),
MIH might occur and SSB=1602 was output.
(1) Mainframe
(2) A volume is used by multiple pairs, and SRC and TGT coexist.
(3) CCHH range of copy source and copy target of the SRC pair is
partially overlapped. (No problem if completely matches)
(4) An update I/O is issued to the above overlapped area.
Category Mainframe
123 Unclear information output to audit log

Phenomena DKU micro-program exchanged, [+{Micro Kind, Old Ver, New
Ver}={DKU(SCSIR2G), 004F01,004F01}] was output to audit.log, but
the relation with HDD type on micro media was unclear.
Conditions of Occurrence The problem occurs when DKU micro-program is exchanged.
Changed Part SVP
124 Link down with SSBs output during FCoE operation

Phenomena During an FCoE operation, link down occurred and SSB=B6FB and
BC4F were output.
(1) During I/O processing, SCSI reset is received from a host.
(2) Immediately after reset response, PLOGI is received from the host.
(3) In the post-processing for transfer abend, internal resource is depleted
Category Open

125 Wrongly active button for DT function window
Phenomena When executing remote log-in to SVP while there was no P.P. supporting
Dynamic Tiering, a button to activate DT function window did not
become inactive.
Monitor Pools
Stop monitoring Pools
Start Tier Relocation
Stop Tier Relocation
(1) P.P. supporting DT (Dynamic Provisioning, Dynamic Tiering) is not
available.
(2) A button for DT function window activation is displayed from SVP
remote log-in.
Changed Part SVP
126 WCHK1 in normal MP with SSB and SIM when MPB

blockade
Phenomena When an MPB was mounted to a blocked location without any
maintenance operation, WCHK1 occurred in a normal MP. In this case,
SSB=32FA and SIM=3073xy and 3080xy were output.
Conditions of Occurrence The problem occurs When an MPB is mounted to a blocked location
without any maintenance operation.
127 Incorrect normal end of maintenance operation

Phenomena Even though reserving DXBF resource failed, a maintenance operation
ended normally and SSB=A066 was output.
Conditions of Occurrence Problem occurs with any of the following maintenance operations
- DKA replacement
- SSW replacement
- PDEV replacement
- DKA installation or removal
- DKU installation or removal
- PDEV installation or removal
- SSW micro-program exchange
- EXP micro-program exchange
- DKU micro-program exchange
Category HDD

127 SSB=548D output at DP-VOL creation
Phenomena When a DP-VOL was created, SSB=548D was output.
(The problem was just log output and no effect on the DP-VOL)
Conditions of Occurrence The problem occurs when a DP-VOL is created.
129 Failure of automatic cache directory recovery after CHK3

Phenomena During automatic cache directory recovery, CHK3 occurred frequently
and the recovery failed. (SIM=0xFFEE0x)
Conditions of Occurrence The problem occurs when there is a blocked CM PCB in a cluster where
the automatic cache directory recovery is executed.
130 Incorrect usage rate display of migration target

Phenomena During migration plan creation by Volume Migration, the estimated
usage rate of migration target displayed in a graph did not include the
usage rate of migration source.
(1) The usage rate of migration source is 1% or higher.
(2) Migration plan is created.
(3) A graph of migration target is displayed.
Changed Part SVP
131 Failure of migration plan creation due to internal logical error

Phenomena After [Make New Plan] was clicked on Auto Plan window to create
migration plan, Storage Navigator message [5205 7423] showing a
internal logical error appeared and the migration plan was not created.
(1) There is a parity group whose usage rate within a time period
specified as sampling term is higher than the threshold of HDD class
where the parity group belongs to.
(The lower the HDD class threshold, the higher the occurrence frequency)
Changed Part SVP

132 I/O error due to no record
Phenomena After LDEV format with SOM305 set to ON, if OS IPL of z/VSE system
was executed, an I/O error due to no record might be detected.
(An error message appeared on the host console)
Conditions of Occurrence Problem occurs when reading track#2 and later of cylinder#0 from a host.
(VOL formatted while SOM305 is ON creates records up to track#1 of
cylinder#0)
Category Mainframe
133 Failure of pool shrink with SSB and error message output
Phenomena Pool shrink failed and SSB=AF0D was output. Storage Navigator
message appeared in this case was [3005 78043].
(1) DP or DT is used.
(2) A pool consists of multiple pool VOLs which vary in capacity.
(3) The pool usage rate after pool shrink is close to the capacity threshold.
134 Host I/O long response time with SSBs output

Phenomena Slow response to host I/O and SSB=DD86, 14DD and 13F3 may output.
(1) Cache capacity is over 128GB.
(2) I/O load concentrates on a specific MPB.
*Problem is more likely to occur if random property of host I/O is strong.
135 MP blockade resulted from LDEV deletion during I/O

Phenomena If a logical VOL was deleted during I/O processing from a Mainframe
host, an MP was blocked and SSB=1644 might be output.
(1) I/O from Mainframe host is in process.
(2) An LDEV is deleted.
(3) Unit check occurs for the I/O and receiving sense command from the
Mainframe host takes one second or more.
Category Mainframe

136 NOP of CLI command when 1,280 CLI commands in process
Phenomena When CLI (raidcom) asynchronous commands were sequentially issued
and there were 1280 commands waiting for processing or in process in
DKC, a NOP would occur if another CLI command was issued
(1) 1,280 CLI (raidcom) asynchronous commands are being processed.
(2) Another CLI (raidcom) command is issued.
Category Open
137 SSB=2CC7 output at TC/UR pair deletion

Phenomena When a TC/UR pair was deleted, SSB=2CC7 might be output.
(1) A TC/UR pair is created using DP-VOL.
(2) Immediately after the above pair creation, the pair is deleted.
138 SSB=4470 output and failure suspension

Phenomena When offline micro-program exchange or volatile PS-OFF/ON was
performed, SSB=4407 was output. In this case, if there was any UR pair
in COPY or PAIR status, failure suspension occurred.
(2) JNLG is already defined.
(3) Offline micro-program exchange, or volatile PS-ON after PS-OFF.
139 Path failure with SSBs output during FCoE processing

Phenomena During FCoE processing, a path failure occurred and SSB=B6FB and
BC4F were output.
(1) A host I/O is processed using a port of CHG PCB.
(2) 512 or more commands are received from the host.
(3) SCSI reset is received from the host.
Category Open

140 SSB=9C3E due to conflict of rebalance and cache maintenance
Phenomena When cache maintenance and rebalance processing conflicted each other,
SSB=9C3E might be output.
Conditions of Occurrence May occur if the operations below are performed at the same time.
(1) Cache maintenance
(2) Rebalance (pool expansion, pool shrink or tier relocation)
141 SSB=12DF output during I/O to TC P-VOL

Phenomena During an I/O to TC P-VOL, SSB=12DF might be output.
(1) TC pair configuration
(2) 342 or more write I/Os are issued to TC P-VOL at the same time.
(3) For the above write I/Os, time-out occurs frequently. (Overload, path
disconnection, or a failure)
Category True Copy or True Copy for Mainframe
142 Non-execution of PP expiration processing

Phenomena If SVP was never logged in after SVP reboot, SVP launcher did not
activate. In this case, if PP expiration processing was executed, SVP
launcher check mounted on PP activation part determined as no launcher
and the PP expiration processing was not executed.
(1) No log-in to SVP after reboot.
(2) PP expiration processing is executed.
Changed Part SVP
143 SSB=8971 output during TC pair creation

Phenomena At TC pair creation, SSB=8971 was output on target VOL side.
(1) DP pool VOL contains an external VOL.
(2) No page is allocated to a DP-VOL associated with the above pool.
(3) TC pair is created using the DP-VOL of (2) as P-VOL.

144 Application error during Define Configuration and Install
Phenomena During Define Configuration and Install processing, an application error
may occur.
Conditions of Occurrence The problem may occur when Define Configuration and Install is
executed.
Changed Part SVP
145 "Aborted command" on a host with SSB=D1F3 output

Phenomena "Aborted command" appeared on a host and SSB=D1F3 was output.
(1) External storage system
(2) Cache mode is set to "Disable".
146 SSB=137E and 137F output at recover from CM PCB failure

Phenomena Recovery from a CM PCB failure, SSB=137E and 137F might be output.
(1) Configuration where CM PCBs are 4 PCBs or more.
(2) Any operation accompanied with LDEV ownership migration (MPK
maintenance/ failure, LUSE combination/release, SI pair creation/release,
CoW Snapshot pair creation/deletion, JNL volume addition/deletion,
ownership migration from CLI/Storage Navigator) is executed.
(3) After the above operation, a CM PCB failure occurs.
(4) The failed CM PCB is recovered.
147 Unable to reflect configuration change done from SVP

Phenomena Configuration change done on SVP was not reflected to Storage
Navigator window.
Conditions of Occurrence The problem may occur when one of the following conditions is met.
(1) After configuration change from SVP, and maintenance from SVP.
(2) After configuration change from SVP, Refresh of Storage Navigator
fails.
Changed Part SVP

148 SSB output and MP blockade during Open I/O or TC/TCz
Sync processing
Phenomena During an Open I/O operation or TC/TCz Sync operation, SSB=1644 was
output and MP might be blocked.
(1) Open I/O or TC/TCz Sync.
(2) An error (such as link down, implicit logout) is detected during
transfer processing of status.
(3) I/O is overloaded.
Category Open, True Copy, True Copy for Mainframe
149 Incorrect display of raid group usage rate

Phenomena (1) On Performance Adviser which monitored operating rate, the usage
rate of raid group exceeded 100%.
(2) On Performance Monitor of Storage Navigator, the usage rate of raid
group displayed was higher than the actual rate.
(1) An I/O is issued from a host.
(2) Performance Monitor of Storage Navigator is turned ON, or
Performance Adviser of operating rate monitoring tool is activated.
(Monitoring data collection of Performance Monitor and Performance
Adviser, and monitoring data update of DKC are not in right timing)
150 MIH occurrence due to a failure during background copy

Phenomena When a failure occurred during FC background copy processing, MIH
might occur and SSB=1602 was output.
(1) Mainframe.
(2) FC pair with Incremental specified.
(3) Reset occurs just before the completion of background copy.
Category Mainframe

151 Disabled log-in to Storage Navigator with error message
Phenomena During Storage Navigator operation, Storage Navigator message [10121
107022] appeared and Storage Navigator was terminated. After that log-
in to Storage Navigator was disabled with Storage Navigator message
[10123-107025].
(1) After remote log-in to SVP, the mode is changed to "Modify".
(2) SVP [Install] button is clicked and Install dialog opens.
(3) In the condition of (1) and (2), a LAN cable is plugged off and left
disconnected for more than a minute.
(4) More than 30 minutes passes after (3).
After that, log-in to Storage Navigator is disabled even SVP mode is

changed to "View".
Changed Part SVP
152 Wrong LU reset due to SAS port blockade or link down

Phenomena When DMA transfer time-out occurred at SAS port link down or
blockade, LU reset was wrongly issued and SSB=1B2E and SIM=0F12-
xx were output.
Conditions of Occurrence The problem occurs when SAS port blockade or link down occurs.
Category HDD
153 SSB=A73B output if DKA port recovery fails

Phenomena If DKA port recovery failed, SSB=A73B was output.
Conditions of Occurrence The problem occurs when a hardware failure occurs during DKA port
recovery in any of the following maintenance.
(1) DKA replacement
(2) SSW replacement
(3) DKA installation
(4) DKU installation
(5) SSW micro-program exchange
(6) EXP micro-program exchange
(7) DKA micro-program exchange
Category HDD

154 Multiple SSB=8E04 output
Phenomena When offline DKC micro-program exchange on UR MCU side was
performed, or PS ON was performed, SSB=8E04 might be output on
MCU side more than 10 times.
(2) MCU DKC
(3) A volatile power cycle is performed for MCU.
(4) System Option Mode449 is set to ON to RCU.
155 Drive blockade and no progress of reboot on SVP

Phenomena A drive was blocked during the time between the completion of SCHIP
micro-program exchange download processing and reboot initiation, and
the reboot processing status displayed on SVP did not make a progress.
SSB=DFxx, and EFxx.
Conditions of Occurrence The problem occurs when a HDD failure occurs during the time between
the completion of SCHIP micro-program exchange download and reboot
initiation and then a drive is blocked.
Category HDD
156 Failed micro-program exchange after time-out due to no

available resource
Phenomena When EXP or SSW micro-program was exchanged while I/O was
overloaded, time-out to wait for resource occurred and the exchange
failed.
(1) EXP or SSW micro-program exchange
(2) No resource is available. (It may occur in case of I/O overload and in
large configuration)
Category HDD

157 Decrease in command multiplicity
Phenomena When HDD micro-program was exchanged, time-out occurred in transfer
from cache to DXBF and command multiplicity decreased.
(1) HDD micro-program exchange
(2) Time-out occurs in transfer from cache to DXBF.
Category HDD
158 Failed path inline due to confliction of path inline and ORM
Phenomena Path in-line (A3/A6/A2 routine) and ORM (HDD diagnosis function)
conflicted with each other and the path in-line might wrongly fail.
Conditions of Occurrence The problem may occur when path in-line is executed from Diagnosis.
Category HDD
159 Failed installation of DKA PCB with SSBs output after

CHT/CHG PCB removal
Phenomena When CHT PCB was removed and then DKA PCB was installed in the
same location, SSBs=B615 and B2E4 were output and the installation
failed.
(1) CHT PCB or CHG PCB is blocked.
(2) The blocked CHT PCB or CHG PCB is removed.
(3) DKA PCB is installed in the location where CHT PCB or CHG PCB
is removed.

Category Open
160 No output of SIM for external temperature problem

Phenomena The following SIMs which were supposed to be output when external
temperature problem occurred were not output.
SSB=BF1010, BF1110, BF1210, BF1011, BF1111, BF1211, BF1012,
BF1112, BF1212, BF1013, BF1113, and BF1213
Conditions of Occurrence The problem occurs when an external temperature problem occurs.
Affected Products/Version SSVP: All
Fixed Product/Version SSVP: 70-02-53/00
Changed Part SSVP

161 Invalid information contained in SSVP dump
Phenomena When SSVP dump was collected, invalid data was contained in the
header of SSVP dump data and architecture. In particular,
(1) SSVP DUMP was SSVP MP.
(2) Minute and second of DUMP collection time were incorrect.
Conditions of Occurrence The problem occurs when SSVP dump is collected.
Changed Part SSVP
162 Failed data writing and actual value reading

Phenomena A request of environment monitor read and write for an interface between
SVP and SSVP succeeded but the data was not written in some cases.
Also, the actual value could not be read.
Conditions of Occurrence The problem may occur when register write and read of DKCMAIN is
executed from a PC for production line test.
Changed Part SSVP
163 No output of SIMs for internal temperature warning/alarm

disagreement
Phenomena SIM=BFA4A4 for internal temperature warning disagreement of CLI on
module1 side was not output.
SIM=BFA3A5 for internal temperature alarm disagreement and BFA4A5
for internal temperature warning disagreement of CL2 on module1 side
was not output.
Conditions of Occurrence The problem occurs when internal temperature warning disagreement of
CL1 on module1 side, or internal temperature alarm/warning
disagreement of CL2 on module1 side is detected.
Changed Part SSVP

164 Failure suspension with SSB=EF47 output after SSB=FE13
Phenomena Hours after resync operation following I/O processing while a UR pair
was in SUSPEND status, SSB=EF13 was output on RCU side, and then
SSB=EF47 was output and failure suspension occurred.
(1) UR or UR for Mainframe pair
(2) Update I/O while pair status is PAIR or COPY
(3) SSB=EF13 is output on RCU side.
165 Delay in response to I/O in port with no SCSI reset

Phenomena If SCSI reset occurred frequently, response to an I/O in port where the
SCSI reset did not occur was delayed.
Conditions of Occurrence The problem may occur when one of the following occurs.
(1) Frequent SCSI reset
(2) Frequent link failure
Category Open
166 Hang-up with SSBs output during reset processing

Phenomena Reset hang-up occurred and SSB=1609 and 10FF were output.
Conditions of Occurrence The problem may occur when one of the following occurs.
(1) Frequent SCSI reset
(2) Frequent link failure
Category Open
167 Incorrect progress status of LDEV format

Phenomena The progress status of LDEV format might not be displayed correctly.
(1) 73 or more LDEVs are selected.
(2) The above LDEVs contain LDEVs whose emulation type is 3390-A
(without DP VOL attribute).
(3) LDEV format (excluding quick format) is executed.
Category Mainframe

168 Wrongly enabled maintenance for DP-VOL or pool VOL
Phenomena Maintenance (blockade, format, recovery) for DP-VOL or pool VOL was
wrongly enabled.
Conditions of Occurrence The problem occurs when one of the following conditions is met.
(1) For a pool VOL of DP pool with which a not-blocked DP-VOL
associated, blockade or format is executed.
(2) DP-VOL associated with a blocked DP pool is, blockade is executed.
(3) For a DP-VOL which is associated with a DP pool whose pool VOL
is blocked, format or recovery is executed.
169 Failure of path re-creation after link down and then link up
Phenomena When a path was established in Point to Point connection without switch,
if link down and then link up occurred, the path could not be re-created
and SSB=C242 was output.
(1) Point to point connection without switch.
(2) A path is already created.
(3) Link down and then link up occur.
Category Open
170 Abend of SSW or Expander micro-program exchange

Phenomena When SSW or Expander micro-program was exchanged on a system
without DKU, the exchange ended abnormally and SVP message [2433
E] appeared.
(1) DKU is not installed.
(2) SSW or Expander micro-program is exchanged.
Fixed Product/Version SVP: All
Changed Part SVP

171 Abend of test plan with SSB output when reset occurs during
FCoE I/O processing
Phenomena If reset occurred during FCoE I/O processing, a test plan ended
abnormally and SSB=BC3B was output.
(1) A reset is received from a host during I/O processing in FCoE port.
(2) Response to a reset target command is being transferred.
(3) ABTS is received from the host for the reset target command.
Category Open
172 Abend of test plan due to P-path or CHK3 failure during FCoE
I/O processing
Phenomena During FCoE I/O processing, if P-path failure or CHK3 failure occurred,
a test plan ended abnormally and SSB=BD21 and BD22 were output.
(1) MCH-DMA transfer is delayed.
(2) DMA transfer is stopped due to P-path or CHK3 failure.
(3) There is an FCoE event in stopped MCH-DMA transfer.
Category Open
173 SSB=B695 output in port different from the failed port

Phenomena When a cable of FCoE port was disconnected and connected, SSB=B695
was output in other ports.
(1) A link failure is detected in FCoE port.
(2) Both of the following occur.
(a) A Tag# obtained at link failure is not consistent with the one
calculated at receipt of Notify Acknowledge.
(b) A Tag# obtained at link failure is reserved in a port different from the
one where the link failure occurs.
Category Open

174 Incorrect version display of SSW, Expander and DKAF
Phenomena When micro-program was exchanged on a system without DKU, the
versions of SSW, Expander and DKAF on Replace (current) side were
displayed as "xx-xx-xx".
- Failure of SSW and Expander version display
(1) DKU is not installed.
(2) Micro-program exchange is performed.
- Failure of DKAF version display
(1) DKA is not installed.
(2) Micro-program exchange is performed.
Changed Part SVP
175 Incorrect display of PP expiration on license key window

Phenomena At Config micro-program exchange, PP expiration check was stopped by
SVP reboot and SIM=7FF7 was output, but configuration information
displayed on license key window of Storage Navigator was not updated.
For this, the PP was not expired on the license key window.
Conditions of Occurrence The problem may occur when any of the following conditions is met.
(1) It is 13:00 o'clock while SVP mode is other than View and SVP is
rebooted without changing the mode to View.
(2) It is 13:00 o'clock during maintenance which requires SVP reboot and
the SVP reboot is not yet performed, and then SVP is rebooted before
date changes.
Changed Part SVP
176 Wrongly same LBA start points of LDEVs

Phenomena When a command was executed from CLI in the order below, LBA start
points of LDEVs created in (1) and (2) were the same.
(1) Install CV command was requested.
(2) CoW Snapshot VOL creation was requested for the LDEV# same as
that in (1).
(1) Install CV command is received from CLI.
(2) CoW Snapshot VOL creation is requested with the same LDEV#
specified before the processing result is reflected to the actual
configuration.
Category Open

177 Command reject after CoW Snapshot VOL creation fails
Phenomena After CoW Snapshot VOL creation from CLI failed (SSB=2E30, 4119)
failed, a command of configuration change for the VOL specified at the
CoW Snapshot VOL creation from CLI was rejected. (SSB=2E11, 0153)
Conditions of Occurrence The problem occurs when CoW Snapshot VOL creation fails and
SSB=2E30 and 4119 are output.
Category Open
178 Pair suspend due to MPB failure during TC initial copy

Phenomena During TC initial copy, MPB failure occurred and the pair might be
suspended.
(1) TC initial copy is executed.
(2) MPB failure occurs.
179 Unable to calculate monitoring information of page

Phenomena When an I/O was issued to a page of external VOL of DT pool (including
external VOL), the monitoring information of the page was not
calculated.
(1) UVM is used.
(2) DT pool
(3) Emergency destage
180 High Write Pending rate resulting in MIH and SSB

Phenomena When XRC was in use, Write Pending went over 70%, MIH occurred and
SSB=1602 was output.
(1) There is an XRC pair.
(2) Write Pending of MPB where XRC utility VOL exists is high.

181 Wrongly enabled LDEV installation while 1024 LDEVs exist
Phenomena While 1,024 LDEVs existed in a RAID group of RAID1 (2D+2D) or
RAID5 (3D+1P), when LDEV installation was executed from CLI to the
same Raid group, the LDEV could be created.
(1) 1,024 LDEVs exist in a RAID group of RAID1 (2D+2D) or RAID5
(3D+1P).
(2) LDEV installation is executed from CLI with the same RAID group
specified.
182 Incorrect display of non-mounted LDEV available to select on

Logical Devices window
Phenomena On Logical Devices window, when a LDEV which was displayed on the
window but not mounted was selected and then any of the following
operation was executed, the LDEV information was not displayed on
Confirm window. In this case, if Apply was clicked, Storage Navigator
message [20122 106004] appeared.
- Format LDEVs
- Block LDEVs
- Shred LDEVs
- Restore LDEVs
Conditions of Occurrence The problem occurs when the following operations are executed in that
order.
(1) On Logical Devices window, a LDEV is selected and Delete LDEV is
executed.
(2) Before the above operation is completed, Logical Devices window is
displayed for 5 minutes (until the operation is completed).
(3) The LDEV selected in (1) is selected and Format LDEVs, Block
LDEVs, Shred LDEVs or Restore LDEVs is executed.
Category Open Volume Management, Virtual LVI
Changed Part SVP
183 SSB output at MP PCB removal

Phenomena When an MP PCB was removed during the duplex pair creation between
2 storages, SSB=8BE9 was output.
Conditions of Occurrence The problem occurs when an MP PCB is removed.
Category Open

184 Incorrectly enabled operations
Phenomena On Logical Devices window, when LDEVs other than those with Access
Attribute of read/write were selected and then any of the following
operation was executed, a Wizard could be opened.
- Format LDEVs
- Shred LDEVs
Conditions of Occurrence The problem occurs when the following operations are executed in that
order.
(1) On Data Retention window, a LDEV is selected and Access Attribute
is changed to Read Only or Protect.
(2) On Logical Devices window, the LDEV selected in (1) is selected and
Format LDEVs or Shred LDEVs is executed.
Causes and Updates The micro-program has been modified to fix the problem.
Category Open Volume Management, Virtual LVI
Changed Part SVP
185 Incorrect message display on host side log

Phenomena Messages such as "Input/output error" was displayed on a log on host
side.
(A test plan might stop)
(1) CHG port
(2) Reset is received during data transfer.
(3) Reset target command is queued.
Category Open
186 Failed MPB maintenance with WCHK1

Phenomena When MPB replacement was performed after ESW PCB replacement
failed, WCHK1 occurred in the replaced MPB and maintenance failed.
SIM=3072, 3073, and 3080
SVP message ONL2412
(1) ESW PCB replacement or installation fails. Or ESW PCB removal
and installation without maintenance is performed.
(2) After the above operation, MPB is replaced or installed.
(3) Micro-program version on FM in the above MPB is before V02.

187 Memory leak of 254Kbytes
Phenomena During Storage Navigator operation, memory leak of about 254Kbytes
occurred.
Conditions of Occurrence The problem occurs when Option tab of Shadow Image or Shadow Image
for Mainframe is opened, or the window is updated while the tab opens.
Changed Part SVP
188 Increased time to enable log-in to Storage Navigator

Phenomena The time to enable log-in to Storage Navigator after SVP activation
increased 10 minutes at the maximum.
Conditions of Occurrence The problem occurs when SVP micro-program is downgraded from the
version 70-02-03/00 and higher to 70-01-61/00.
Changed Part SVP
189 Incorrect version display on MP Ver tab

Phenomena DKA Port version displayed on MP Ver (Curt/Running) tab of Version
window was incorrect. In particular,
- The version of SAS#1-Port#1 was displayed in SAS#0-Port#1.
- The version of SAS#0-Port#0 was displayed in SAS#1-Port#0.
Conditions of Occurrence The problem occurs when DKAF version corresponding to SAS
controller is inconsistent.
Changed Part SVP
190 LDEV blockade after SM nonvolatile and CM volatile

Phenomena At powering OFF and nonvolatile power ON after offline micro-program
exchange failed, SM was not volatilized and CM volatilized, and then a
LDEV was blocked. (SVP message SMT2433 E was output)
Conditions of Occurrence The problem occurs when power OFF and nonvolatile power ON is
performed after offline micro-program exchange fails.

191 Host time-out or MIH occurrence with SSBs output
Phenomena At CPC replacement, host time-out or MIH occurred and SSB=1602,
1603, DD86, D031, D034, DE4E, DE4D, 14DD etc., might be output.
(1) There is a CLPR in capacity less than that recommended in
Maintenance Manual and users guide.
(2) There is XRC/CC pair.
(3) CPC replacement or CPC replacement after failure
(4) Side file capacity increases.
192 SSB=59F0 output during FCv2 copy processing

Phenomena During FCv2 copy processing, SSB=59F0 (byte44-45: 0x0901) was
output.
(1) Mainframe system
(2) Flash Copy version2
(3) A write I/O is issued to FCv2 source VOL (S-VOL). (Host I/O or
configuration where FCv2 S-VOL is combined with secondary VOL of
other PP for copy)
(4) FCv2 copy is executed.
Category Flash Copy version2, Shadow Image for Mainframe
193 Failure of SSWs display in message after removal fails

Phenomena In a system with DKU-00/01/02 were mounted, when DKU-02 was
removed, the removal failed due to SSW cable failure. At this time, only
SSWs in the top DKU (DKU-00) were displayed in a message
[ONL4189] to prompt SSW dummy replacement.
(1) DKU removal
(2) Operation other than removal from DKU minimum configuration in
DKC
(3) The above operation fails due to SSW hardware failure.
Changed Part SVP

194 Performance degradation and time-out error
Phenomena In all Storage Navigator operations, performance degraded or time-out
error (1-4011) might occur.
(1) Operation after logging into Storage Navigator
(2) A user program which logs into the same SVP via RMI executes log-
in and log-out many times.
Changed Part SVP
195 Incorrect performance value display

Phenomena By Performance Monitor, when monitoring data had been collected for
the maximum monitoring term, the performance value output was larger
than actual value.
(1) Monitoring data has been collected for the maximum monitoring term.
(2) The performance value is displayed from the oldest data or output by
Export tool.
Changed Part SVP
196 TC/TCz pair suspension with SSB=1042 output

Phenomena A TC pair/TCz pair in copy processing was suspended and SSB=1042
was output.
(1) True Copy/True Copy for Mainframe is in use on MCU.
(2) The pair status on RCU side is changed (including operations from
SVP) or a path failure occurs during update I/O to TC P-VOL/TCz M-
VOL.
(3) MCU side is overloaded. (overload likely causes LMJCB depletion)

197 Unintentional returning ownership to source MPB
Phenomena For XRC utility LDEV, ownership migration with user specified was
supposed to be enabled while a session was suspended, but the ownership
might be unintentionally returned to migration source MPB.
(1) There is a XRC pair
(2) HPAV is set to XRC utility LDEV.
(3) LDEV ownership migration of the utility LDEV is requested while a
session is suspended.
(4) After the above operation, session resync is executed.
198 Not shared upper limit by WWNs in group with non-priority

control
Phenomena When multiple WWNs were registered by Server Priority Manager
(WWN) or RMLIB (WWN), and then all of registered WWNs were
registered in one of groups with non-priority control and the upper limit
was set, but the upper limit was not shared by WWNs in the group.
(1) Multiple WWNs are registered by Server Priority Manager or
RMLIB.
(2) The registered multiple WWNs are registered in a group, which is set
as non-priority control target, and the upper limit is set.
(3) Among WWNs in the non-priority control group, there are some
WWNs to which I/Os are issued.
Category Open
199 Suspend or temporary high JNL usage rate (70%)

Phenomena When online micro-program was exchanged in UR, UR delta resync or
UR Mainframe 4x4 environment, the following might occur and
SSB=BBAC was output.
(1) Suspend
(2) In case of delta resync, JNL usage rate became 70% temporarily.
(1) UR, UR delta resync or UR Mainframe 4x4 environment.
(2) Online micro-program exchange is performed.
(3) Data transfer which occurs in the above environment takes time.

200 Disabled TC/UR pair operation
Phenomena LDEVs in a device group could not be referred from RAID Manager and
TC/TCz and UR/URz pair operations (paircreate, pairresync, pairsplit)
were disabled.
(1) Volatile power ON or offline micro-program exchange is performed
while a device group exists.
(2) After the above operation, RAID Manager is rebooted.
201 Memory leak at communication failure during pool

name/LDEV nickname setting
Phenomena At pool name or LDEV nickname setting, if communication between
SVP and DKC fails, memory leak occurred (about 233KB).
Conditions of Occurrence The problem occurs when communication between SVP and DKC fails at
pool name or LDEV nickname setting.
Changed Part SVP
202 Disabled upper limit control after LDEV ownership migration

Phenomena When the upper limit was set by Server Priority Manager (port, WWN) or
RMLIB (WWN) and the ownership of LDEV which would receive I/Os
from the registered port or WWN was migrated, the upper limit control
was disabled.
(1) The upper limit is set by Server Priority Manager (port, WWN) or
RMLIB (WWN).
(2) The ownership of LDEV which receives I/Os from the registered port
or WWN is migrated.
(3) The ownership of the above LDEV is returned to the previous MP
PCB.
Category Open

203 Memory leak with invalid LDEV specified
Phenomena During Shadow Image setting operation, if a resource group of specified
LDEV# was invalid, memory leak (about 2MB) occurred.
Conditions of Occurrence The problem occurs when a resource group of specified LDEV# is invalid
at Shadow Image setting operation.
* Resource group of LDEV# will not be invalid actually.
Changed Part SVP
204 SSB=59F0 output during FCv2 copy processing

Phenomena During FCv2 copy processing, SSB=59F0 (byte 0x44-0x45: 0x1c00) was
output.
(1) Mainframe system
(2) Flash Copy version2
(3) FCv2 copy is in process.
Category Flash Copy version2
205 No display of WWNs logged in

Phenomena When multiple WWNs were connected with a port and then the WWN
connected first was disconnected, all of WWNs which were being logged
in by test_getrminfo_PPC_LOGIN were not displayed.
(1) Multiple WWNs are connected with a port.
(2) Among connected WWNs, WWNs other than that connected last are
disconnected.
Category Open
206 No SSBs for overload output at cache overload

Phenomena When cache was overloaded, SSB=D354, D355, D356, D35C, E669,
E66A, and E66C indicating overload were not output.
(1) Open
(2) Cache overload
Category Open

207 Delay in I/O response to host after SSB=14DD output
Phenomena In the system with multiple-CLPR configuration where a CLPR whose
Write Pending was over 70% existed, when a MP PCB was replaced,
SSB=14DD for waiting available segment was output and I/O response to
host was delayed.
(1) More than one CLPRs are defined.
(2) There is a CLPR whose Write Pending is over 70%.
(3) Any of the following operations accompanied with ownership
migration is executed.
- MP PCB maintenance/failure
- LUSE connection/release
- SI pair creation/release
- CoW Snapshot pair creation/deletion
- JNL VOL addition/deletion
- Ownership migration from CLI or Storage Navigator
208 SSB=13D9 output

Phenomena SSB=13D9 was output.
Conditions of Occurrence The problem may occur when SATA-E drive or OSW function is used.
209 Disabled TC pair creation with SSB=C310 output

Phenomena At TC Mainframe pair creation, SSB=C310 was output and pair creation
might be disabled.
(1) PCM
(2) TC Mainframe pair creation or resync
(3) NVS is OFF.
(4) CMF PCB is mounted in the second module only.

210 HDD blockade with SIMs output
Phenomena An HDD was blocked after the threshold was exceeded and SIM=
DF6XYY, DF7XYY, DF8XYY, and DF9XYY were output.
(1) An HDD failure occurs.
(2) LU reset which is post-processing of the HDD failure turns to time-
out.
(3) The HDD is not blocked immediately after the failure.
(4) The threshold is exceeded.
Category HDD
211 TC failure suspension with SIM/SSB output after cache PCB

blockade
Phenomena When a cache PCB was blocked during host I/O to a TC P-VOL,
SIM=0xd41003 and SSB=B839 were output, and only one of TC pairs
was suspended by failure.
(1) True Copy or True Copy for Mainframe.
(2) A host I/O is issued to a TC pair.
(3) Cache failure blockade occurs.
212 Failure of UR/TC pair creation with SSBs output

Phenomena In 3DC configuration with direct Point-to-Point connection, when a UR
pair was created between RAID700 and RAID600, SSB=D004, EBEF
were output and the pair creation failed.
(1) Direct Point-to-Point connection.
(2) TC or UR connection.
(3) Initiator port is on RAID700 side.
Category True Copy, Universal Replicator

213 Degradation of maximum performance when LDEV ownership
is not equally assigned
Phenomena If LDEV ownership was not equally assigned to LDEVs in a PG, the
multiplicity of commands to drives tended to excessively increase.
If LDEV ownership was equally assigned to LDEVs in a PG, the
multiplicity of commands to drives tended to decrease.
For this, the maximum performance when LDEV ownership was not
assigned slightly degraded.
(1) SATA drive is mounted, or SOM862 is set to ON.
(2) LDEV ownership is not equally assigned to LDEVs in a PG. (At
PDEV installation, LDEV ownership is automatically assigned)
Category HDD
214 Taking longer time to block drive port

Phenomena The time to block a drive port when command time-out occurred was
longer than that in the specification. (SSB=A4C2)
(1) Command transfer at the first request ends abnormally.
(2) Command time-out occurs at retry request.
Category HDD
215 Taking longer time to execute SI pair split and resync

Phenomena Split and resync operation of SI/SIz pair took longer time.
(1) SI copy for 3 or more pairs is executed.
(2) SI pair split or resync is executed. (*)
* The problem likely occurs when there is no difference in data.
Category Shadow Image, Shadow Image for Mainframe

216 WCHK1 occurrence in MP different from blocked MPs with
SSBs and SIMs output
Phenomena During LDEV format for a mainframe volume, if a failure which caused
all MPs (4MP) in an MPB to be blocked occurred, WCHK1 occurred in
an MP of another MPB. In this case, SSB=1644 and 32FE, and
SIM=3080 and 3073 were output one time.
(1) Mainframe LDEV format is executed.
(2) A failure leading to blockade of all MPs in an MPB occurs.
Category Mainframe
217 Wrong drive blockade when SOM862 is set to ON

Phenomena When time-out occurred while System Option Mode 862 was set to ON,
LU Reset failed and a drive was wrongly blocked. (SSB= A4C2 or A4C5
and SIM= EFXX-xx)
(1) SOM862 is set to ON.
(2) I/O is overloaded.
(3) Command time-out occurs. (LU Reset fails)
Category HDD
218 Install CV command reject with SSBs output

Phenomena When Install CV (raidcom add ldev) was executed from CLI, SSB=2ECD
and 0000 were output and the command was rejected.
(1) Install CV is executed from CLI.
(2) The above processing is stopped by reset.
(3) Install CV is executed from CLI again while the same RAID group# is
specified.

219 Creation of LDEV with the same LBA start point
Phenomena When Install CV was executed more than 4 times in series from CLI,
LDEV with the same LBA start point might be created.
(1) The different RAID group# is specified in the first Install CV and the
second Install CV.
(2) In the second and later Install CV, the same RAID group# is specified.
(3) LBA start point of the third LDEV is smaller than that of the second
LDEV.
(4) LBA start point of the fourth LDEV is smaller than that of the second
LDEV.
220 Command reject and SSBs output

Phenomena When external group deletion was executed from CLI, the command was
rejected and SSB=2E11 and 0153 were output.
Conditions of Occurrence The problem occurs when a MP reset occurs in the synchronous
processing of Install CV command with external group specified.
Category Open
221 Command reject with SSBs output due to logical confliction

Phenomena The following commands from CLI were rejected and SSB=2E11 and
0153 were output.
- Install CV
- Volume to Space
- LDEV format (normal, quick)
- LDEV blockade/recovery
- DP-VOL deletion
- CoW Snapshot VOL creation
- CoW Snapshot VOL deletion
- Shredding
- External VOL creation
Conditions of Occurrence The problem occurs when a logical confliction occurs in DKC.
Category Open

222 Unable to complete asynchronous command and no result
returned
Phenomena Asynchronous command being executed could not be completed and get
command_status did not return the result.
Conditions of Occurrence The problem occurs when logical inconsistency occurs in DKC.
Category Open
223 Incorrect displayed or output Long range LDEV usage rate

Phenomena The displayed Long range LDEV usage rate or the Long range LDEV
usage rate with "PhyLDEV" command specified output by Export Tool
might be incorrect.
(1) A disk failure occurs.
(2) Memory depletion
Changed Part SVP
224 Wrong usage rate exceeding 100%

Phenomena Due to a bug, the usage rate displayed in graph on Performance Monitor,
or that output by Export Tool might exceed 100%.
(1) Monitoring switch is turned ON and monitoring data is being
collected.
(2) The cycle to collect monitoring data in several times becomes wrong.
Changed Part SVP
225 No display of monitoring data for 1 plot

Phenomena PS OFF and ON was performed while option monitor switch was ON and
the data was collected, the monitoring data for 1 plot was not displayed.
(1) Option monitor switch is ON.
(2) PS OFF and ON is performed.
(3) Option monitor data is displayed.
Changed Part SVP

226 Long response for host I/O with SSBs after frequent output of
SSB=1315
Phenomena After SSB=1315 was frequently output, long response occurred for a host
I/O and SSB=DD86, 14DD, 13F3 and 1315 might be output.
(1) Cache capacity is 128GB or larger.
(2) I/Os concentrate on a specific MPB.
(3) SSB=1315 are frequently output.
* The problem is more likely to occur if random property of host I/O is
strong.
227 SSBs output during backup from CoW V-VOL to tape device
Phenomena During backup from CoW Snapshot V-VOL to a tape device,
SSB=14DC, 14FF and DD88 were output.
(1) Read commands.
(2) Conflict at the same slot.
Category Open
228 Abend with SSBs output

Phenomena In FCoE environment (with TC/UR pair), if the power was turned OFF
during I/O to P-VOL, all I/Os issued to the TC P-VOL ended abnormally.
At the same time SSB=1699, D051 and B839 were output.
(1) TC P-VOL
(3) A write I/O is issued.
(4) Blockade or delay of path between DKCs
Category True Copy

229 Delay in host I/O response increase of MP operating rate
Phenomena During a resync operation for a UR pair, MP operating rate of JNL owner
MPB where the UR pair belonged to increased and host I/O response was
delayed.
(1) UR P-VOL belongs to RAID700.
(2) Resync is executed for the UR pair.
(3) A host I/O is issued to the above RAID700.
230 Slowed item selection and scrolling operation

Phenomena On Main window of Storage Navigator, selecting item on a table and
scrolling became slow. Depending on the spec of PC being used, browser
didn't respond. (No Responding was displayed at the top of window)
Conditions of Occurrence The problem may occurs if a lot of items on the table are selected. (no
response time is about 4 seconds for 5000 items)
The degree of performance degradation varies depending on PC spec and
the number of items selected.
Changed Part SVP
231 SSBs output at FCv2 pair creation

Phenomena Because numbers after the decimal point are truncated on Storage
Navigator Subscription (Current) display, if the total capacity of DP-VOL
for the pool capacity is over 100% and under 101%, the display is 100%
and it seems for users that the pool capacity is equal to the DP VOL
capacity.
Under the above condition, when FCv2 pair was created (COPY from
TSO) using non DP-VOL (external VOL) and DP-VOL, SSB=AFB0 and
AF83 were output.
(1) The total capacity of DP-VOL for the pool capacity is over 100% and
under 101%.
(2) Pair creation is executed for all DP-VOLs associated with a pool.
Changed Part SVP

232 WCHK1 in MP causing WCHK1 in another MP
Phenomena When WCHK1 occurred in an MP due to a hardware failure, WCHK1
might occur in another MP in some cases.
Conditions of Occurrence The problem may occur when WCHK1 occurs in an MP due to a
hardware failure.
233 XRC pair suspension after SSBs output following CHK2

occurrence
Phenomena After CCW chain was received, CHK2 occurred, SSB=3289, 3570,
B2FF, B21B, 5871, B2C8, 481E and 4732 were output, and XRC pair
was suspended.
(1) Compatible XRC
(2) There is an FCv2 pair whose source VOL is XRC pair primary VOL.
(3) In a command to write data to multiple records in the same track, retry
to wait for FCv2 copy occurs while there is a record written by the same
CCW chain.
234 TC pair suspension or Check Condition with SSB

Phenomena A TC Sync pair was suspended due to SSB=B826, or Check Condition
was returned due to SSB=D034.
(1) OPEN VOL
(2) A host I/O is issued to P-VOL of a TC Sync pair or HAM pair.
(4) Host I/Os concentrate on the neighboring block area.
(5) The following (a) or (b) occurs.
(a) ECC group where the VOL belongs to is in correction copy
processing.
(b) One side of CM or SM of MCU where the VOL belongs to is
blocked.
Category True Copy

235 Abend of LDEV quick format with SSB=1548 output
Phenomena When LDEV quick format was executed, SSB=1548 was output and the
format might end abnormally.
(1) HDD is SATA-E.
(2) Emulation type is 3390-A (without DP-VOL attribute)
(3) Cache is overloaded (Write Pending rate is 60% or higher).
(4) LDEV quick format is executed.
Category Mainframe
236 Taking longer time for resync operation

Phenomena When group resync was executed for a Mainframe Sync CTG and then
group suspend was executed before the internal processing of the resync
was completed, the following occurred.
(1) The resync operation took time.
(2) The pair status did not change to Suspend.
(1) True Copy for Mainframe
(2) Sync CTG
(3) Group resync is executed.
(4) Group suspend is executed while some pairs in Suspend status exist in
the group after the above group resync operation.
237 Incorrect indication of pool VOL for LDEV

Phenomena After pool shrink was executed for an LDEV (pool VOL), the LDEV was
deleted on the Pools window but LDEV window continued to show that
the LDEV was a pool VOL.
(1) Shrink Pool is executed but not completed.
(2) For LDEVs other than the above Shrink Pool target LDEV, one of the
following maintenance operations is performed.
- LDEV installation
- LDEV removal
- PDEV installation
- PDEV removal
- System option setting change

238 Failure of login command with error message
Phenomena During login processing, if an MP failure occurred, a login command of
RAID Manager failed and a RAID Manager command error message,
[EX_ENAUTH] Authentication failed with User, appeared.
Conditions of Occurrence The problem occurs when one of the following conditions are met.
(1) Communication between SVP and DKC is disabled due to an MP
failure and so on.
(2) Login and logout of SMIS are executed many times.
Changed Part SVP
239 Continued SSBs output after FCv2 relationship creation

Phenomena When FCv2 relationship was established while a PIN failure occurred in a
VOL to be used as FCv2 S-VOL, SSB=9C1D and AE63 were
continuously output.
(1) Mainframe VOL
(2) A PIN failure occurs in a VOL to be used as FCv2 S-VOL and then
FCv2 relationship is created.
Category Flash Copy version2
240 XRC session suspend with SSBs output after CHK1 and CHK3
Phenomena During an XRC operation, CHK1 and CHK3 occurred, SSB=65EA,
65EB and 65EC were output, and the XRC session was suspended.
(1) Mainframe
(2) Compatible XRC
(3) CHK1 and CHK3 occur during RD RECORDSET command
processing on XRC MCU.
(The problem does not occur by WCHK1)

241 Failure of cache maintenance during CFW I/O
Phenomena During CFW I/O processing, if cache maintenance (installation, removal,
replacement) was performed while the cache was overloaded, the cache
maintenance might fail.
(1) CFW I/O is issued from Mainframe host.
(2) Cache is overloaded.
(3) Cache maintenance (installation, removal, replacement) is performed.
Category Mainframe
242 Failure of micro-program exchange

Phenomena Micro-program exchange failed. (SVP message SMT2433 E)
(1) Version before exchange is earlier than 70-02-03-00/00 (before V02).
(2) The version exchanged with the above is 70-02-03-00/00 or higher
(V02 and higher).
(3) The combination of CHA configuration and selected reboot type is
either one of (a) or (b).
(a) CHA is BASIC only, the selected type is 1/4, 1/8, or By One.
(b) CHA is OPTION1 and later, and the selected type is By One.
243 Extremely large response time and transfer length

Phenomena When RMF (Resource Measurement Facility) was used with ESS option
specified on an IBM host, the values of response time and data transfer
length which were displayed on [PPRC SEND] and [PPRC RECEIVE] of
[ESS LINK STATISTICS] were extremely large.
(1) RMF is used with ESS option specified.
(2) Initial copy or update copy of TC/TCz pair is in process.
(3) During the measurement of (1), the integrated value of data transfer
length of a port used for TC pair M-R connection exceeds 4 bytes (2,047
Gbytes) or the integrated value of data transfer time exceeds 4 bytes
(4,294 seconds).
* The problem occurs only at the time when each integrated value
exceeds 4 bytes. Once the value has exceeded 4 bytes, the problem does
not occur until the exceedance occurs again.

244 SVP message display when Auto Plan tab opens
Phenomena When Auto Plan tab on Volume Migration window was opened, SVP
message [5205 6023] appeared.
(1) No parity group on DKC is mounted.
(2) Auto Plan tab on Volume Migration window is opened.
Changed Part SVP
245 Wrongly returned setting of SSID or cache mode

Phenomena Phenomenon1
SSID setting (raidcom modify ldev) made from RAID Manager returned
to the previous setting.
Phenomenon2
Cache mode setting of external VOL (raidcom modify external_grp)
made from RAID Manager returned to the previous setting.
Phenomenon1
(1) An LDEV whose provisioning type is BASIC is created or deleted
(2) SSID setting is performed from RAID Manager during the time period
from execution to completion of the above operation.
Phenomenon2
(1) An LDEV whose provisioning type is BASIC is created or deleted
(2) Cache mode setting of external VOL is performed from RAID
Manager during the time period from execution to completion of the
above operation.
Category RAID Manager
246 SSB=9680 output by Withdraw during FC background copy

Phenomena During FC background copy, if Withdraw (DDSW=NO) was executed,
pair was deleted but SSB=9680 might be output.
(1) Mainframe
(2) Background copy is in process.
(3) Withdraw (DDSW=NO) is executed.
Category Mainframe

247 Failure of pair deletion and command reject
Phenomena During FC background copy, if Withdraw (DDSW=NO) was executed,
the pair was not deleted and commands to the VOL were rejected.
(1) Mainframe
(2) Background copy is in process.
(3) Withdraw (DDSW=NO), Restore, or Fast Reverse Restore is
executed.
Category Mainframe
248 SSBs when LDEV deletion command is sequentially executed

Phenomena LDEV command (raidcom delete ldev) was sequentially executed from
RAID Manager or CLI, SSB=B9CD and B904 were output.
Conditions of Occurrence The problem occurs when "raidcom delete ldev" command is sequentially
executed for the same LDEV from RAID Manager or CLI.
249 Failed TC pair creation in DKC configuration

Phenomena When DKC configuration contained external connection, TC pair creation
after MP PCB failure might fail.
(1) Mainframe VOL
(2) TC pair creation is executed after MP PCB failure occurs.
(3) DKC configuration contains external connection (regardless of Open
or Mainframe)
Category Mainframe
250 Port offline occurrence during hazard test

Phenomena During a hazard test from HP-UX, port offline occurred. "Fatal error" was
reported on the host.
(1) Open connection.
(2) Operating rate is over 50%.
Category Open

251 Unable to return LS_ACC and SSB output
Phenomena After CHK2 occurrence, PLOGI was received from a host, but LS_ACC
could not be returned and SSB=BC29 was output.
(1) A LOGO command is received from a host connected to a FCoE port.
(2) Reset occurs to release resource.
(3) A PLOGI command is received from the host while the reset is sent.
(4) By the reset, IOCB (Login/Logout Port IOCB) for resource release is
issued to a protocol chip.
(5) Because of the resource release IOCB issued to the protocol chip, the
resource of PLOGI received from the host is released.
(6) Due to the release of (5), LS_ACC of PLOGI cannot be returned,
time-out occurs, and then the job stops.
Category Open
252 Link down with SSB=B6C0 after MP failure

Phenomena After an MP failure occurred, link down occurred and SSB=B6C0 was
output.
(1) MP is blocked.
(2) Resource release is notified to a protocol chip.
(3) ABTS is received from a host.
(4) BA_ACC of ABTS is issued to the host.
(5) PLOGI command is received from the host.
(6) LS_ACC of PLOGI is issued to the host but it turns to an error in the
protocol chip.
Category Open
253 Frequent output of SSB=9F02 and 9853

Phenomena When the status of SI/CoW Snapshot pair was changing, SSB=9F02 and
9853 were frequently output.
(1) SI P-VOL is used as CoW Snapshot P-VOL.
(2) The SI pair status is PAIR.
(3) The Snapshot pair status is PSUS.
(4) A write I/O is issued to the SI P-VOL and the Snapshot P-VOL.
(5) SPLIT is executed for the SI pair.
Category Shadow Image

254 Unable to block the failed MP if CHK1B occurs
Phenomena If an MCH-DMA error occurred and CHK1B failure due to another factor
occurred before MP was blocked, the blockade processing for the MP
where the MCH-DMA error occurred was not executed, and SSB=32FD
and 1607 were output.
(1) An MCH-DMA error occurs.
(2) Before MP is blocked, CHK1B due to another factor occurs.
255 Not collected CHK1C information in LM dump

Phenomena When CHK1C occurred, the CHK1C information was not collected in
LM dump.
Conditions of Occurrence The problem occurs when CHK1C occurs.
256 Incomplete display of serial#

Phenomena When "raidcom get path" was executed from CLI, only 11 digits of
serial# was displayed.
(1) UVM configuration with NEXSAN connected.
(2) "raidcom get path" is executed from CLI.
257 Failed Volume Migration or unchanged pair status

Phenomena Volume Migration failed and SSB=212B was output, or the status of SI
Quick Restore did not change to PAIR but remained in R-COPY.
Conditions of Occurrence The problem may occur when the following conditions (1) and (2), or
only (3) are met.
(1) Volume Migration is executed.
(2) Random read access to migration source VOL
(3) SI Quick Restore is executed for OPEN volume.
* More likely to occur if VOL size or mounted cache capacity is large.
Category Shadow Image, Volume Migration

258 Incomplete alternate path addition with SSBs output
Phenomena While 2048 external groups were mapped in the same path group, if the
8th path was added as external path addition from CLI (raidcom add
path), alternate paths were only added to 1024 groups out of 2048 groups
and SSB=2E23 and 4303 were output at executing GetCommandStatus.
(1) The number of alternate paths in a path group is 7.
(2) There are 1025 or more external groups in the same path group.
(3) External path addition is executed from CLI. (raidcom add path)
Category Open
259 ESW PCB internal failure with SSB=3250 leading to WCHK1

Phenomena When an ESW PCB internal failure occurred, SSB=3250 was
continuously output and WCHK1 occurred (SIM=3073XY, SSB=1663 or
32FA)
(1) The storage system is in ready status.
(2) An ESW PCB internal failure occurs. (SSB=3250)
260 WCHK1 occurrence due to ESW PCB internal failure leading

WCHK1 in all MP
Phenomena When an ESW PCB internal failure occurred (SSB=3250), WCHK1
occurred (SSB=3585).
In the worst case, WCHK1 occurred in all MPs except 1MP in 1DKC.
(SIM=3073XY, SSB=3250 and 3585)
(2) An ESW PCB internal failure occurs (SSB=3250).

261 Failure of DKAF micro-program update in configuration
without DKA
Phenomena At micro-program upgrade in a configuration without DKA, if DKAF
was also checked on Micro-program Exchange dialog box and the
upgrading was executed, the operation itself was completed normally, but
[MP Ver. (Curt./FM)] on Version window of SVP Maintenance window
showed abnormality. All the information on [MP Ver. (Curt./FM)] was in
red. Besides, * (asterisk) was added to the end of version of DKAF.
(1) Configuration without DKA
(2) On Micro-program Exchange dialog box, DKAF is checked.
Affected Products/Version DKCMAIN: All SVP: All
SVP: 70-02-53/00
262 "raidcom get command_status" response

Phenomena Before the completion of asynchronous processing, response of "raidcom
get command_status" was returned.
(1) Multiple commands are executed.
(2) Before the completion of the command executed first, a command
executed later is completed.
Category Open
263 Abend of DKA replacement/installation or DKA blockade

Phenomena When micro-program downgrade was executed while DKCMAIN was
selected and DKAF was not selected, micro-program consistency of
DKCMAIN and DKAF was not checked, and micro-program downgrade
ended normally. (SVP message=SMT2434i, SSB=1Axx)
After that, the following problem might occur.
(1) DKA replacement ended abnormally.
(2) DKA installation ended abnormally.
(3) After turning power OFF or PS OFF, when the system was activated,
DKA was blocked.
(1) Micro-program downgrade
(2) DKCMAIN is selected.
(3) DKAF is not selected.
Changed Part SVP

264 FCoE port blockade
Phenomena An FCoE port was blocked and SSB=2120 was output.
Conditions of Occurrence Occurs when Qlogic chip sequentially receives PLOGI over a short time.
Category Open
265 Wrong SSB output at CHK3 occurrence

Phenomena When CHK3 due to micro-program failure occurred, SSB=1663 was
output instead of SSB=3585 which was supposed to be output as error
code for WCHK1.
(SIM=3073, SSB=3250 and 1663)
(2) CHK3 accompanied with micro-program failure is detected in micro
processor of MP PCB1, 2, 3, 5, 6 and 7.
266 Omitted volume identifier field

Phenomena When "raidcom discover lun" was executed from CLI, the field of volume
identifier (E_VOL_ID_C) was omitted when displayed.
Conditions of Occurrence The problem occurs when "raidcom discover lun" is executed from CLI
in UVM configuration where any of the following devices is connected.
MSA1000, DMX1000, CX600, Symm8830, SUN, EVA, E3000, iStrage,

MSA, STK, Gateway, E8000, E4000, DMX-4, NEXSAN, IFT, Toshiba,
Xiotech, ST6920, S400, ST2540, Evolution II, Ultimate III, DS4700, HP
MSA2000, CX600, IBM SVC, E4000, FUJITSU DX8000, MSA2000G3
or FUJITSU DX400

267 Internal logical error when command device is set to LU of
external VOL
Phenomena When command device including User Authentication Device Group
Definition was set for external VOL LU, and logical error occurred.
(Storage Navigator message 01005-00196, SVP message SEC-333E)
Conditions of Occurrence The problem occurs when command device (User Authentication, Device
Group Definition) is set for an external VOL LU.
Changed Part SVP
268 Host I/O stop with SSB=D034 output

Phenomena When a failure occurred during host I/O processing, the host I/O might
stop and SSB=D034 was output.
Conditions of Occurrence The problem occurs when a failure occurs during host I/O processing.
269 No message for error cause at communication failure or

Windows error
Phenomena Phenomenon 1: When a communication failure or Windows error
occurred during SSW replacement, a message (ONL3325E) which just
indicated abnormal processing appeared but an SVP message to show the
cause of error was not displayed.
Phenomenon 2: When a communication failure or Windows error
occurred during MPB installation, a message (ONL0813E) which just
indicated abnormal end appeared but an SVP message to show the cause
of error was not displayed.
Conditions of Occurrence For phenomenon 1:
The problem may occur when any of the following occurs during SSW
replacement.
(1) A communication failure between SVP and DKC.
(2) A Windows error.
For phenomenon 2:
The problem may occur when any of the following occurs during MPB
installation.
(1) A communication failure between SVP and DKC.
(2) A Windows error.
Changed Part SVP

270 Abend of YKQUERY from BCM to RCU
Phenomena In UR Mainframe configuration, YKQUERY issued from BCM to RCU
side ended abnormally. (BCM message: 0C9)
(1) Universal Replicator for Mainframe
(2) C/T TIME MODE of BCM Copy Group Attributes is JOURNAL or
ASIS.
(3) System Option Mode530 is set to ON.
(4) An I/O is issued while a URz pair is in DUPLEX status.
(5) YKQUERY is executed from BCM to RCU side.
271 Unnecessary one-byte space added at the end of PORTs line

Phenomena When "raidcom get ldev" command was executed without - key option,
unnecessary one-byte space was added at the end of the line of PORTs.
(1) An LDEV is configured with alternate paths from several ports.
(2) Some of the host groups connected with the LDEV in (1) via different
ports have the same host group name.
(3) Raid Manager issues the "raidcom get ldev" command, which
includes a parameter: "PORTs".
(4) When the last Host Group name in the "PORTs" is the same as that in
(2), the problem will occur.
RAID Manager: All
RAID Manager: 01-25-03/11
Category RAID Manager
RAID Manager
272 Incorrect space included in serial#

Phenomena When any of the following commands was executed from CLI, a space
might be included in serial#.
- raidcom discover lun
- raidcom get path
(1) UVM configuration with any of the following storages connected.
SUN, FAStT, STK, Gateway, DS4800, Xiotech, NetApp, ST6920, S400,
ST2540, DS4700, DS5000 or IBM SVC
(2) "raidcom discover lun" or "raidcom get path" is executed from CLI.

273 PA error with SSBs output by Write Track Data command for
cylinders
Phenomena During TC pair resync processing, if a Write Track Data command was
issued from a host to 2 cylinders, a PA error occurred at the data writing
to the second cylinder and SSB=5860 and 6855 were output.
(1) MF TC Sync
(2) The pair status is Pending Duplex.
(3) A host issues Write Track Data or Write Full Track command.
(4) A write I/O which is multiple track write for cylinders and does not
write data to head# 0x0e is received.
274 Job abend with SSB=673A output at MP-2MC removal

Phenomena In RAID700 and RAID600 configuration, when MP-2MC on RAID700
was removed, a job being executed (Write Full Track command) ended
abnormally and SSB=673A was output.
(1) Mainframe TC Sync
(2) Write Full Track command is executed.
(3) The write command processing detects exclusive bit of write slot and
an incomplete update copy is stopped. (SSB=8631)
(4) Write Full Track command is created using data chain.
Category Mainframe
275 CHK2 occurrence in MCU with SSBs output

Phenomena In pair configuration with EAV and DP coexisted, when MP replacement,
DKA replacement or MP installation/removal was performed on MCU or
RCU, CHK2 occurred in the MCU and SSB=B21B, 8BEC, 8BEA, 3570,
B2FF and B2C8 were output.
(1) Mainframe TC Sync
(2) Write Track Data command
(3) Multiple track write
(4) Temporary abnormal end occurs in copy job (it occurs by path failure
(including micro-program exchange), CHK2 or receiving attention)
Category Mainframe

276 Failure suspension with SSB=8FCC after all MPs blockade by
WCHK1
Phenomena While a UR pair was in initial copy processing, if all MPs of JNL
ownership PCB where the pair belonged to were blocked on MCU due to
WCHK1, SSB=8FCC was output and the pair was suspended by failure.
(1) UR pair initial copy processing.
(2) All MPs of a JNL ownership PCB to which the pair belongs are
blocked due to WCHK1.
277 Wong SIM output

Phenomena Even though, SVP-BASIC JP1 was placed, SIM=BFE3A2 for dual SVP
setting failure was output.
* The SIM is supposed to be output when there is an error in SVP high
availability kit setting.
Conditions of Occurrence The problem occurs when one of the following operations is executed
while SVP-BASIC JP1 is placed.
(1) SVP high availability kit setting without setting SVP-OPTION
(2) SVP high availability kit setting release while SVP-OPTION is set.
Changed Part SSVP
278 LDEVs wrongly created with the same LBA start point
Phenomena If Install CV (raidcom add ldev) was sequentially executed more then 3
times from CLI, LDEVs with the same LBA start point might be created.
Conditions of Occurrence The problem may occur when Install CV is executed from CLI under the
conditions below.
(1) The LBA start point of the second LDEV is smaller than that of the
first LDEV.
(2) The LBA start point of the third LDEV is smaller than that of the first
LDEV.

279 Failure suspension with SSB=BBAC output
Phenomena In OPEN MxN or Mainframe MxN configuration, if I/O load was high, a
JNL on MCU became full, SSB=BBAC was output and failure
suspension occurred.
(2) OPEN MxN or Mainframe MxN configuration
(3) An I/O is executed while a UR pair is in DUPLEX status.
(4) JNL usage on RCU is 512MB or more.
(5) Operating rate of the Initiator port on RCU is 40% or more.
(6) Write pending rate on RCU is 25% or more.
280 Invalid number of issued frames with SSB=B70A output at

path creation
Phenomena In N-port connection, when path between CUs shared by TC/UR was
created, the number of issued frames became invalid and SSB=B70A was
output.
(1) Fabric OFF/Point to Point connection
(2) TC/UR/external configuration
(3) Port attribute MCU/external
Category Open
281 START PENDING occurrence in host after busy report

Phenomena During I/O processing in multiple hosts connection, Busy was reported to
a specific host and START PENDING (SSB=1603) occurred in the host.
(1) Multiple Mainframe hosts connection
(2) A path is connected to port#0.
(3) Busy is reported to a host during I/O processing from multiple hosts.
Category Mainframe

282 Temporary 90% of MP operating rate
Phenomena During TC pair initial copy processing, MP operating rate on MCU side
might temporary increase to 90%.
(1) TC pair initial copy processing
(2) Initial copy multiplicity is set to 256 or more.
(3) Pair creation of 256 or more volumes is executed.
283 Response failure with SSB=DDA1 at transfer time-out

Phenomena When transfer time-out occurred due to high load, the response could not
be returned temporarily and SSB=DDA1 was output.
(1) Target/RCU-Target port
(2) High load environment where transfer time-out or reset frequently
occurs
Category Open
284 Failures of SVP/SN operation and Audit Log Buffer function

Phenomena [Phenomenon1] The following Storage Navigator or SVP operation might
fail. (Operation from SVP: SVP message 2728 W, operation from Storage
Navigator: Storage Navigator message 3305 2015)
- Make Volume
- Volume To Space
- Volume Initialize
- LDEV maintenance blockade
[Phenomenon2] The following function using system disk might be

disabled. (Operation from SVP: SIM=1801-00, operation from Storage
Navigator: Storage Navigator message=8005 65783, 8005 68761)
- Audit Log Buffer function
[Phenomenon3] WCHK1 might occur by the following operations.

(SIM=3073)
- Operations of Phenomenon1
- Enabling the function of Phenomenon2
Conditions of Occurrence The problem may occur when 9 or more system disks are defined.

285 Delay of restore and increase in JNL usage rate on RCU
Phenomena In configuration where URz S-VOL was also shared by SIz, if an update
I/O was issued to URz P-VOL while SIz was changing to SPLIT, restore
was delayed and JNL usage rate on RCU side increased.
(1) Universal Replicator Mainframe pair.
(2) Shadow Image for Mainframe uses the URz S-VOL.
(3) SIz is changing to SPLIT.
(4) An update I/O is issued to URz P-VOL.
286 RAID700 SCHIP FW change

Phenomena A drive may be blockaded when SAS Link failure occurred between
DKA and SSW and the drive is accessed through both ports.
Conditions of Occurrence SCHIP FW version 07-00-0E
Causes and Updates The version of SCHIP FW is changed to "07-00-10".
SCHIP firmware is modified to improve the response of SCHIP when
accessing through both ports.
Affected Products/Version SCHIP FW: 07-00-0E and higher
Fixed Product/Version SCHIP FW: 07-00-10
Changed Part SCHIP FW
287 Abend with SSBs output by ESW removal during I/O

processing
Phenomena During I/O processing to TC pair (P-VOL and S-VOL were DP-VOLs), if
ESW was removed, the job ended abnormally and SSB=5527, 6149 and
5860 were output.
(1) An I/O (write I/O) is issued.
(2) ESW is removed.
Category Mainframe

288 SSB=1548 output on RCU during update I/O to MCU side
Phenomena When an update I/O was issued to URz MCU side, SSB=1548 was output
on RCU side.
(1) RCU is RAID700.
(2) Universal Replicator for Mainframe pair
(3) An update I/O is issued to MCU side.
289 Increased processing time and insufficient LM dump

information
Phenomena When an update I/O was issued to URz MCU side, the processing per
JNCB took additional time (14μs) and LM dump information was
insufficient.
(1) RCU is RAID700.
(2) Universal Replicator for Mainframe pair
(3) Initial copy or I/O to MCU of the pair
290 Invalid collected information after SSB output and failure

suspension
Phenomena When SSB=EF40 was output and failure suspension occurred during UR
pair creation, the collected information of SSB=EF40 was invalid.
(1) RCU is RAID700.
(2) Universal Replicator or Universal Replicator for Mainframe pair
(3) Initial copy or update I/O to MCU of the pair
(4) SSB=EF40 is output.

291 Suspend on host side and wrong SSB=1603 output on DKC side
at pair creation
Phenomena In Mainframe environment, at pair creation (initial copy) of TCz, FC,
URz, SIz or VM VOL, suspend occurred on host side and SSB=1603 was
wrongly output on DKC side.
(1) Mainframe
(2) TCz, FC, URz, SIz or VM VOL
(3) Pair creation (initial copy)
(4) Online host and offline host coexist.
Category Mainframe
292 Host MIH and SSB=7A20 occurrence by cache removal during

host I/O
Phenomena When a cache PCB on MCU was removed during host I/O processing to a
TCz pair, host MIH occurred and then SSB=7A20 was output.
(1) A host I/O is issued to a TCz pair.
(2) A cache PCB on MCU is removed.
Category Mainframe
293 SSBs output by forcible S-VOL deletion during I/O processing

Phenomena In configuration where the consistency of TC Sync CTG was guaranteed,
if S-VOL was deleted during I/O processing to Sync P-VOL, SSB=1699,
16A1, 16AD, D030 and D031 were output.
(1) OPEN VOL
(2) A host write I/O is issued to P-VOL in TC Sync CTG consistency
guaranteed configuration.
(3) Transfer length of a command is 1Kbyte or longer.
(5) S-VOL forcible delete during I/O processing
Category True Copy

294 Frequent MIH after setting HMO51 to ON
Phenomena When HMO51 setting was changed from OFF to ON, MIH frequently
occurred and SSB=1602 was output.
(1) Version 70-02-08-00/00 or earlier is used.
(2) Online micro-program exchange is performed.
(3) One of the following operations is performed.
(a) HMO51 setting is changed from OFF to ON during I/O processing.
(b) An I/O is executed after HMO51 setting is changed from OFF to
ON.
Affected Products/Version DKCMAIN: 70-02-08-00/00
295 FCv2 pair suspend due to slot confliction in highly loaded

environment
Phenomena In highly loaded environment, if TC/SI copy and FCv2 copy to the same
slot conflicted, FCv2 pair might be suspended and SSB=960C was
output.
Conditions of Occurrence The problem may occur when TC/SI copy and FCv2 copy to the same
slot conflicts in highly loaded environment.
Category Mainframe
296 PS status disagreement (SIM)

Phenomena In the system with DKC-1 mounted, if SSVPMN was replaced,
SIM=BFB2A0 (DKC-0 PS status disagreement) and SIM=BFB2A4
(DKC-1 PS status disagreement) might be reported.
(1) Configuration where DKC-1 is mounted
(2) Ready status
(3) SSVPMN PCB is replaced.
Changed Part SSVP

297 Time-out on MCU with SSBs output
Phenomena During I/O processing between MCU and RCU, as a response from the
RCU could not be received correctly, time-out occurred on MCU
(SSB=C861). If the time-out occurred during pair creation, SSB=B90A
and B944 were output.
(1) MP PCB basic module CL1 is mounted.
(2) TC/UR configuration.
(3) An I/O is executed for the TC pair.
298 MP operating rate over 90%

Phenomena In highly loaded environment with a large number of FC copy
relationships, MP operating rate might become over 90%.
(1) There are a large number of FC copy relationships.
(2) Highly loaded environment.
Category Mainframe
299 Increase in Write Pending rate and incomplete LDEV format

Phenomena The following phenomena might occur.
- Write Pending rate increased.
- LDEV format was not completed.
(1) DP/DT configuration
(2) Normal VOL and pool VOL coexist in a parity group.
(3) LDEV format is executed for the normal LDEV in the above parity
group.
(4) A write I/O is issued to a DP-VOL associated with the pool VOL in
the above parity group.

300 Job abend due to CM failure
Phenomena When a CM failure occurred, a mainframe job might end abnormally.
(Host message IOS000I, IOS020I)
(1) An I/O is issued to Mainframe VOL.
(2) A CM failure occurs.
Category Mainframe
301 Wrongly enabled V-VOL creation

Phenomena V-VOL of OPEN-V creation with cylinder specified from CLI (raidcom
add ldev) was enabled.
Conditions of Occurrence The problem occurs when V-VOL of OPEN-V emulation is created with
cylinder specified from CLI. (raidcom add ldev)
Category Command Control Interface
302 Failure of rebalance initiation

Phenomena The rebalance initiation was disabled at the following operations.
(1) Pool expansion
(2) Pool shrink
(3) Tier relocation
(1) An MP PCB is removed in a maintenance operation.
(2) After executing any of the following operations, you will not be able
to execute the same operation again.
(a) Pool expansion
(b) Pool shrink
(c) Tier relocation

303 Stopped host I/O after I/O performance degradation and Start
Pending occurrence
Phenomena Due to a CM PCB failure, backend processing occupied the processor for
a long time (40 msec). Because of it, I/O processing performance of
Mainframe host degraded and Start Pending occurred, causing the
Mainframe host I/O to stop.
SSB=1602, 1603 and 1607.
Host message: Start Pending, MIH
(1) Mainframe host I/O is in process.
(2) A cache failure occurs or cache maintenance is performed.
Category Mainframe
304 Rejected journal volume creation/deletion command with SSBs

output
Phenomena During journal volume creation by CLI command (raidcom add journal),
if journal volume creation was executed by CLI command (raidcom add
journal) while specifying the same journal group#, SSB=2EE4 and 06EA
were output and the command might be rejected.
(1) Journal volume creation or deletion is executed by CLI command
(raidcom add journal/raidcom delete journal).
(2) Journal volume creation or deletion is executed while specifying the
journal group# which is specified in the operation (1).
305 Data transfer time-out between host and storage system

Phenomena When a host/TC/UR I/O was executed, data transfer time-out occurred
between the host and storage system and SSB=B6A9, B6AA and DDA1
were output.
Conditions of Occurrence The problem occurs when a host/TC/UR I/O is executed for a port.
Category Open

306 Sending incorrect data to host with SSB=BC91 output
Phenomena During I/O processing in FCoE connection, when a read command was
received, the storage system might send incorrect data to a host. In this
case, SSB=BC91 was output.
(1) A host is connected with FCoE.
(2) While receiving a read command, a host issues reset command.
(3) When the reset target command is stopped, a protocol chip detects
abnormal end.
(4) Internal buffer area which is used by the abend command is used by
another command.
Category Open
307 Incorrectly enabled or disabled external VOL/V-VOL

migration
Phenomena On Virtual Partition Manager, DP V-VOL or CoW Snapshot V-VOL
migration by a user without access right to a resource group of the target
LDEV# was enabled or the migration by a user with access right to the
resource group of the target LDEV# was disabled.
Storage Navigator messages: 8505-75015, 8505-75026
Conditions of Occurrence The problem occurs when any of the following conditions is met.
(1) In an environment where an external VOL whose parity group number
is 16384-xxx (xxx is within the range from 1 to 4096) exists, the external
VOL with 16384-xxx is migrated to another CLPR.
(2) In an environment where 64,389 or more DP V-VOLs exist, the
64,390th or later DP V-VOL is migrated to another CLPR.
(3) In an environment where 64,389 or more CoW Snapshot V-VOLs
exist, the 64,390th or later CoW V-VOL is migrated to another CLPR.

Category Virtual Partition Manager
Changed Part SVP
308 I/O performance degradation

Phenomena When an I/O was issued to drives of CDEV#:0x0B and later, the I/O
performance degraded by 8KIOPS.
Conditions of Occurrence The problem occurs when the following condition is met.
(1) An I/O is issued to drives of CDEV#:0x0B and later.

309 MP blockade during Mainframe host I/O processing
Phenomena When a cache failure occurred during I/O processing from a Mainframe
host to TCz/URz/FCv2 pair, an MP might be blocked and SSB=1644 was
output.
(1) TCz/URz/FCv2 pair
(2) A Mainframe host I/O is in process.
(3) A cache failure occurs.
Category Mainframe
310 Output of non-existent host group information

Phenomena Host group information obtained by RMAPI API: dsvp_GetHostGroupInf
the information of host group which did not exist was output as the host
name of "xx-Gyy"(xx=Port Location, yy=Host Group#).
Conditions of Occurrence The problem occurs when the host group IDs are not continuous.
* Host IDs are sequentially assigned from 0 in ascending order, but if
any host group ID is deleted, the ID may not be continuous.
Changed Part SVP
311 I/O processing stop with SSB=B801 output at pair deletion

Phenomena When a UR pair using LUSE volumes was deleted during I/O processing,
the I/O processing stopped and SSB=B801 was output.
(1) Open
(2) There is a UR pair using an LDEV used for LUSE.
(3) An I/O is executed.
(4) The UR pair is deleted.
312 Application error when creating 256 or more URz pairs

Phenomena 256 or more URz pairs created from CFL, application error might occur.
Conditions of Occurrence The problem may occur when 256 or more UR for Mainframe pairs are
created from CFL.
Changed Part SVP

313 Checkout failure in delta resync configuration
Phenomena In delta resync configuration, even though an LDEV belonging to a
resource group that the user had no permission existed, checkout might
fail.
(1) UR Delta Resync configuration.
(2) 2,048 or more pairs exist.
Changed Part SVP
314 Incorrectly enabled JNLG registration and deletion due to no

resource group check
Phenomena When a JNLG was registered or deleted on EXCTG window, resource
group check was not executed, which wrongly enabled a user with no
access right to an LDEV belonging to the JNLG to register or delete the
JNLG to/from the EXCTG.
Conditions of Occurrence The problem occurs when a JNLG is registered or deleted on EXCTG
window.
Changed Part SVP
315 Incorrect drive number display on Alerts window

Phenomena When the details of drive-related SIM was displayed on Alerts window,
the drive number in Location was incorrect.
For example, in case of SIM=EF1397, CDEV#/RDEV#=07/17 was
displayed while 03/97 was correct.
SIM=DF0xxx, DF8xxx, DF9xxx, DFAxxx, DFBxxx, EF0xxx, EF1xxx,

EF2xxx, EF9xxx, 43Bxxx, 43Cxxx, 451xxx, 452xxx, 453xxx, 455xxx,
461xxx, 462xxx, 463xxx, 465xxx
Conditions of Occurrence The problem occurs when drive-related SIM is displayed on Alerts
window of Storage Navigator.
Changed Part SVP

316 Performance degradation due to unnecessary SM access
Phenomena Due to unnecessary SM access during any I/O processing including
random read or random read and write, the performance degraded.
(1) Simplex VOL
(2) A host issues any of random read I/O or random read and write I/Os.
(3) MP operating rate of all MPs is over 80%.
Category Open
317 TC pair suspension with SSB=B8ED

Phenomena A TC pair was suspended and SSB=B8ED was output.
(1) MCU of a TC Open pair.
(2) CM failure blockade occurs.
Category True Copy
318 Failure of mode change

Phenomena During SVP mode change from Modify to View, if a user logged out
from SVP while mode change button was inactive, the mode could not be
changed from Modify to View after logging into SVP and changing the
mode from View to Modify.
Conditions of Occurrence The problem may occur when a user logs out from SVP while mode
change button is inactive during SVP mode change from Modify to View.
Changed Part SVP

319 I/O stop resulted from disabled response to host command
Phenomena During I/O processing from a host connected with FCoE to a TC pair, if
the TC pair was blocked (SUSPEND) due to a link failure between MCU
and RCU, response to the command issued from the host could not be
returned and the I/O stopped.
(1) FCoE connection
(2) An I/O is issued to TC P-VOL.
(3) The TC pair is blocked (SUSPEND).
(4) Storage system returns Check Condition to the command received
from the host.
(5) After ABTS is received from the host, the same port receives a
command from the host.
Category Open
320 Unable to complete FCv2 processing in highly loaded

environment
Phenomena In highly loaded environment with a large number of FCv2 relationships,
copy processing might not end.
(1) Highly loaded environment with a large number of FCv2
relationships.
(2) Establish or Withdraw is executed.
Category Compatible Flash Copy V2

VSP 70-02-54-00

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

VSP 70-02-54-00

Transféré par

Droits d'auteur :

Formats disponibles

VSP

MICROCODE VERSION 70-02-54-00/00

Newly supported features and functions for Version 70-02-54-00/00

1-1 Support for CCI configuration report

1-2 Support for per-PCB battery life warning SIM setting

1-4 Support for SIM syslog report

1-5 Support for 2 TB NL-SAS HDD of 7 Krpm

HDS Confidential 1 of 107

1-7 Support for True Copy OPEN and Mainframe consistency

1-8 Improvement for dual SVP configuration

HDS Confidential 2 of 107

1-10 GUI improvement of DP/DT

1-11 New storage support

1-12 Support for new SIM for pool volume blockade

1-13 Support for new CCI commands

For details on each command, see "RAID Manager Command Reference”.

HDS Confidential 3 of 107

1-16 PIN Deletion Tool support for Solaris 10

2-1 Support for EAV, MF-DP and DVE functions

HDS Confidential 4 of 107

3-1 Support for resource ID takeover function (Virtual ID function)

The information to show to the host OS as old model storage is as follows.

3-2 Support for Server Priority Manager GUI

3-3 Support for Tiering Policies per V-VOL in DT

HDS Confidential 5 of 107

3-5 Support for all-page discarding during LDEV format

3-6 Support for vStorage PP combination

3-7 Improvement to keep previous I/O information

HDS Confidential 6 of 107

3-9 RAID Manager 01-25-03/11

3-10 Support for Snapshot combination in UR 3DC delta configuration

3-11 Support for host group option 59

HDS Confidential 7 of 107

2 Unable to open detailed error information window

3 LDEV blockade and disabled access to MCU

HDS Confidential 8 of 107

5 Unexpected DP pool initialization and failure of SI initialization

Phenomenon2: SI initialization was disabled if any TC/TCz/UR/URz pair

6 SSB=EF50 output and failure suspension of UR pair

HDS Confidential 9 of 107

8 Failure suspension with SSB=2A30

9 Unable to refresh display information

10 Correction copy delay when Full Speed Mode ON

HDS Confidential 10 of 107

12 Prolonged periodical processing with SSBs output

HDS Confidential 11 of 107

15 Unexpected EPW check after track over run

16 Unable to cancel update copy after receiving SelReset

HDS Confidential 12 of 107

18 Invalid scroll box position after clicking Add or Remove on

19 Incorrectly active ADD button on Create LDEVs window

HDS Confidential 13 of 107

21 Non-display of error list on the Task Properties window

22 SSBs output after cache maintenance or a cache failure

HDS Confidential 14 of 107

24 Display of an empty error list after clicking Apply

HDS Confidential 15 of 107

26 Incorrect CDEV# indicated in SIM (501XYY)

27 SSBs output at read/write I/O issued to a DP/DT volume

HDS Confidential 16 of 107

29 Inadequate meaning of dialog displayed

HDS Confidential 17 of 107

31 No display of detailed error information at an error in MP

32 XRC session suspend with SSBs output