Usp 50-05-06-00-00

USP
MICROCODE VERSION 50-05-06-00/00

RELEASED 12/09/05
Newly supported features and functions for Version 50-05-06-00/00

1. Common
1-1 Support for Double Concatenated Configuration of RAID5 (7D+1P)

Description Double concatenated configuration of RAID5 (7D+1P) has been supported.
Changed Part DKCMAIN/SVP
Note Not allowed to downgrade micro-program to unsupported version (lower than 50-
05-00-00/00) when double concatenated configuration of RAID5 (7D+1P) exists.
1-2 Enhancement for RAID Level and Emulation Type of 300 GB HDD
Description 1. USP Model
Following RAID levels have been supported for 300 GB HDD (DKR2F-J300FC,
DKS2D-J300FC).
RAID5 (3D+1P), RAID1 (2D+2D)
2. NSC Model
Following RAID levels have been supported for 300GB HDD (DKR2F-J300FC,
DKS2D-J300FC).
RAID5 (7D+1P, 3D+1P), RAID1 (2D+2D)
3. USP & NSC Model

Following emulation types have been supported for 300GB HDD (DKR2F-J300FC,
DKS2D-J300FC).
OPEN-3, OPEN-8, OPEN-9, OPEN-E, OPEN-L, 3380-3, 3390-3
Changed Part Configuration
1-3 Improved Sequential Write Performance at the time of Correction

Access
Description The sequential write performance at the time of correction access in RAID6 has
been improved.
Changed Part DKCMAIN
1-4 Support for SFP Revision Information

Description The following functions for SFP (Small Form Factor Pluggable) have been
supported.
Information display on SVP (PCB Revision panel),
Dump information gathering (Auto Dump function),
Interface name of RM API: dsvp_GetPcbInfEx
1-5 Improved GUI for SM Addition

Description At the time of SM addition, when the checkbox is selected and then cleared,
“Equip” is changed to “Not Equip” automatically.
Changed Part SVP
HDS Confidential 1 of 49
1-6 UR/URZ Enhancement
Description 1. Support for UR/URZ Cascading Configuration
Data can be copied from the Production site to the Local site by using True Copy
Sync/ True Copy for z/OS Sync, then JNL data can be obtained at the secondary
volume and the replica can be created at the Remote site by using Universal
Replicator/ Universal Replicator for z/OS.
2. Support for UR/URZ Multi-Target Configuration

(1) Universal Replicator Multi-Target Configuration
In case of changing the multi-target configuration of True Copy and Universal
Replicator to the cascade configuration by performing True Copy Takeover, the
Universal Replicator pair will be suspended.
(2) Universal Replicator for z/OS Multi-Target Configuration
Data can be copied from the Production site to the Local site by using True Copy for
z/OS Sync. As the same time, the JNL data can be obtained at the Production site
and the replica can be created at the Remote site by using Universal Replicator for
z/OS.
3. Same functions as True Copy/True Copy for z/OS

(1) Using the P-VOL of Universal Replicator/ Universal Replicator for z/OS as the
S-VOL of Shadow Image/ Shadow Image for z/OS is supported.
(2) Coordination of Universal Replicator/ Universal Replicator for z/OS and Volume
Migration is supported.
(3) When specifying a volume that has a Volume Retention Manager setting as a
Universal Replicator for z/OS P-VOL, the Volume Retention Manager attribute is
reflected to the Universal Replicator for z/OS S-VOL as well.
4. Support for Online Addition of UR/URZ JNL Volumes

Journal volumes of Universal Replicator/ Universal Replicator for z/OS have been
available to be added into the journal group online.
5. Expanded Number of UR/URZ JNL Groups

The number of journal groups (JNLG) that can be registered has been expanded
from 16 (JNLG#0-15) to 256 (JNLG#0-255).
Note For No.5
(1) Add SM after exchanging the micro-program with a supported version.
(2) The expansion does not apply to the NSC model.
1-7 Support for LDEV Range Specifying Function

Description When setting LDEV IDs on SVP, if an LDEV Range is specified, the LDEV IDs
outside of the range will not be set. In case of LDEV being across CUs, the function
is valid as well.
LDEV Range | Setting Range of LDEV ID

-----------------------------------------------------------------------------------
3F | 00-3F (40-FF not to be set）
-----------------------------------------------------------------------------------
7F | 00-7F（80-FF not to be set）
-----------------------------------------------------------------------------------
FF | 00-FF（default and same as the current spec）
Changed Part SVP
1-8 Improved Configuration Information Backup
Description All data under C:\DKC200\Config was backed up in the past, but the initial install
data (min500c.dat and min500d.dat) has been removed from the backup data.
The reason for eliminating them is they are not required for recovering
configuration information etc. By eliminating the files, the size of backup data of
configuration information decreases.
Changed Part SVP
1-9 Hid HUR Journal Volume on Feature Panels

Description Hid HUR Journal Volume on the following Feature panels.
Cache Residency, Volume Migration, Compatible HAV, Volume Security, Volume
Retention Mainframe
Journal VOL displayed on VLL tab, but volume setting not available on GUI.
Changed Part SVP (JAVA)
1-10 Improved Reliability in case of HDD Failure

Description Reduced the chance of drive blockade during HDD copy.
In the RAID1 HDD copy, data is read from the normal HDD by default. This will
reduce the chance of source HDD blockade.
Improved the performance of RAID1 HDD copy/correction copy in the Cache
Residency cache area.
Dirty slot is recovered in ORM staging (HDD problem detected  Recovery). This
will improve the reliability of the HDD.
1-11 SVP Support for WINXP SP2

Description 1. SVP has supported Windows XP SP2.
2. XP SP2, various security features, such as Windows Firewall, are supported.
3. TCP ports that are not used on SVP will be closed.
Changed Part SVP
Note If the update to Windows XP SP2 is required, please refer to Apx-a_WinXP_SP2 for
the update procedure.
1-12 Support for PCI Feature

Description The NSC model has supported the hardware PCI feature (Controlling RAID
subsystem power from the mainframe host) as follows.
Replacement of PCI-BOX,
Replacement of SSVP/MN that supports the PCI feature,
Replacement of SSVP/MN between the types of the conventional products and the
ones that support PCI-BOX,
When SSVP/MN has a failure, the failed part is displayed and reported.
Changed Part SVP
1-13 Improvement for Retry Number of Volume Migration Copy

Description The retry number of differential copy caused by the write I/Os of Volume Migration
has been changed from a fixed number to a value being changeable according to the
volume capacity. By this improvement, the migration that has to be discarded so far
will be successful.
Note This improvement applies to write I/O rate 50 IOPS or lower. The migration may
fail if the writer I/O rate is over 50 IOPS.
1-14 SM Backup with Mode 460 when Volatile PS ON
Description When turning off PS, the control information of the following program products
stored in SM will be backed up in SVP. After that, when performing volatile PS ON,
the control information will be restored into SM from SVP.
1. True Copy/ True Copy for z/OS/ Shadow Image/ Shadow Image for z/OS/
Volume Migration/ Flash Copy Version 1/ Flash Copy Version 2/ Universal
Replicator/ Universal Replicator for z/OS
2. Set system option mode 460 on is required to enable function.
Note 1. Support only applies to volatile PS ON after PS OFF. As usual, Power outage,
offline micro-program exchange, DCI and System Tuning are not supported.
2. The maximum time for PS-OFF is 30 minutes. In case of using power monitoring
devices (PCI, etc.), resetting the monitoring time is recommended.
1-14 FAL (HP-UX Reserve Retry)

Description A retry processing for Read or Write in the following case has been available.
A Reserve Conflict error is detected during Read and Write processing onto the
intermediate volume, when performing the MTO (Mainframe to OPEN) transfer or
OTM (OPEN to Mainframe) transfer by using Cross-OS File Exchange on HP-UX.
Changed Part FAL/FCU
1-15 NSC Enhancements

Description 1. Universal Replicator/ Universal Replicator for z/OS External Connection
A UR/URZ pair can be paired with an external volume.
2. Support for ESCON HODM
HODM (Hitachi Online Data Migration) with ESCON connection has been
supported as follows.
- Data can migrate from external subsystems to RAID500 with ESCON connection.
- The migration is supported only in case of the static mode.
- The host I/Os performed on the target migration volume is CC=3.
- Others are same as the RAID450.
3. External Volume Available for Secondary Volume of FCv2
External volume used as a Target Volume (T-VOL) of a Flash Copy Version 2 pair.
4. Scheduled Scans Support for Symantec Antivirus
Scheduled Scans has been supported for Symantec Antivirus Corporate Edition on
SVP. The setting is as follows.
The time of virus scan is right after SVP periodic reboot.
The drive to be scanned is “C:”,
Check “Selected Extensions” in File Types of Scan Options.
Note For No.2:
For more information, please refer to Hitachi Online Data Migration Operation
Manual.
For No.3:
- In case of downgrading the micro-program to an unsupported version, it is
required to withdraw all the FCv2 pairs who’s T-VOL are external ones.
- Before performing the Disconnect operation on an external volume that is used as
a T-VOL of FCv2, make sure to release the FCv2 pair first. (However, if the FCv2
pair is in the suspend status, the Disconnect operation can be performed without
releasing the pair.)
- Before performing the Delete LU operation on an external volume that is used as a
T-VOL of FCv2, make sure to release the FCv2 pair first.
2. Mainframe System
2-1 Support for 1 M Relations of Flash Copy Version 2

Description The maximum number of relations of Flash Copy Version 2 has been increased from
32,768 to 1,048,575.
Note 1. In case of NSC model, the extension function is not available if the check box of
“VFS SYS Area” on the SM setting panel is checked.
2. Extension setting/releasing for the number of relations is not available if any
Flash Copy V2 relations and Copy-on-Write Snapshot pairs exist.
3. It is not allowed to downgrade the micro-program to an unsupported version
(lower than 50-05-06-00/00) if the check box of “Flash Copy V2 Extension” on the
SM setting panel is checked.
2-2 Performance Improvement for Shadow Image for z/OS

Description I/O performance has been improved when using Shadow Image for z/OS volumes.
For example, the performance has been improved for about 7-8% in the following
case:
Number of paths: 1
Package: FICON
Shadow Image for z/OS pair: Primary : Secondary = 1:1
Command 63/47/06: performance improved about 7%.

Command E7/06: performance improved about 8%.
2-3 Support for PPRC Link Information

Description The feature to display the path statistics information of PPRC by using RMF has
been supported. In other words, the information of the Fibre link path between DKC
of True Copy for z/OS can be displayed by using RMF.
2-4 Function Switch 21

Description Function Switch 21 has been available to set the copy pace as follows when
executing PPRC ESTPAIR (Initial copy/Resync of True Copy for z/OS/ True Copy
for z/OS Async) for the volumes of emulation type 2105.
Function Switch 21 = ON : copy pace = 3Trk

Function Switch 21 = OFF : copy pace = 15Trk
2-5 Support for N: 1 Connection of True Copy for z/OS Async

Description The N: 1 connection of True Copy for z/OS Async has been supported as follows.
MCU:RCU = N:1 or 1:N (N=1-4)
Note As for True Copy Sync/ True Copy for z/OS Sync/ True Copy Async, RAID450 and
RAID400 do not support the N:1/1:N connection.
In case of N: 1 connection of True Copy for z/OS Async, if you want to downgrade
the micro-program to an unsupported version (50-04-xx-xx/xx or lower), it is
required to release the N: 1 connection first.
2-6 Support for Replacing Different FICON Type
Description It has been available to replace the mainframe FICON of 8-port adapter (8ML/8MS)
to the one of 16-port adapter (16ML/16MS) or vice versa with the same replacement
procedure. However, it is required to set CHA Mode to ON in SVP.
Note If the mainframe fibre adapters are intermixed (8 ports/16 ports) at the pair location,
the micro-program exchanged will not be available.
2-7 Support for Mainframe Restart Switch

Description In the case of a Mainframe port (FICON/ESCON) being blocked, basically, the
recovery action is to replace the PCB. However, if the PCB replacement affects
other normal ports seriously, a recovery using Restart Switch is available as needed
after asking advices from the Technical Support Center.
The parts to be recovered by using Restart Switch are as follows:
FICON port
ESCON port
Internal path between HTP-CHP.
Internal path between LCP-CHP.
For details, please refer to the Trouble Shooting section of the Maintenance Manual.
Changed Part FICON/ESCON
Note In case of following failures, since the recovery using Restart Switch does not work,
the PCB replacement is required for the recovery as usual.
RCP is defined and it is blocked.
CHP WCHK1 occurs.
2-8 Emulation Type Expansion for URZ (JNL/Data Volume)

Description Universal Replicator for z/OS data volumes
Emulation type 3380 series have been usable.
Universal Replicator for z/OS Journal volumes
Emulation type 3390/3380 series have been usable.
-For details, please refer to the Available Data Volume Emulation Type per Pair for
Universal Replicator for z/OS in actual ECN
Note It is required to perform the LDEV format for the volumes (emulation type 3390/
3380 series) that are removed after having been registered as journal volumes,
except that the volumes are registered as journal volumes again.
2-9 Support for Hyper Swap on GDPS 3.2 and PPRC V4

Description The Hyper Swap function on GDPS 3.2 and PPRC V4 has been certified and has
been available for USP & NSC True Copy - for z/OS.
Note Both MCU and RCU should have DKCMAIN Version. 50-05-06-00/00 or later.
3. Open System
3-1 Universal Replicator Support for NAS
Description Volumes belonging to the NAS port are available to be created as Universal
Replicator pairs,
The update I/O processing is available for the Universal Replicator volumes
belonging to the NAS port.
3-2 Copy-on-Write Snapshot Enhancement
Description Copy-on-Write Snapshot has been enhanced as follows:
1. Supported the volume of UVM as the P-VOL of Snapshot,
A Copy-on-Write Snapshot pair whose P-VOL is defined to an external volume and
whose S-VOL is a virtual volume can be created.
2. Supported the pairresync command,
3. Supported NSC,
4. Supported the volume sharing for the P-VOL of Snapshot and the P-VOL/ S-VOL
of True Copy/True Copy Async/Universal Replicator,
5. Supported the pair operation with DRU attributes set on the volumes, but VMA is
not supported yet,
6. Number of pools has been extended from one to 128,
7. Restore is available from any secondary volumes.
8. Consistency rate for each Copy-on-Write Snapshot pair has been supported.
9. Initialization and optimization of VFS SYSAREA have been supported.
10. LDEV can be restored without removing the pairs after blockade.
The status of SMPLPND changed from “PAIR” to “SMPL” on RAID Manager.
Note In case of item 1 above, the Pool volume cannot be used as the external volume.
SM is required for VFS SYS Area. When downgrading the micro-program to an
unsupported version, it is required to remove the SM for VFS SYS Area.
3-3 DB Validator Enhancement

Description It has been enhanced so that Oracle can use the following command for DB
Validator. (raidvchkset -vbf bne)
3-4 Performance Improvement for Open Connection

Description Random write performance improved up to 10% when the DKA is in the bottle neck
condition. Random read hit performance improved up to 5%. The response
performance has been improved when Read and Write are intermixed.
3-5 Support for Command Device of External Volume

Description It has been available to issue requests on the command device of the external
storage (RAID400/450/500/DF600/700) directly via RAID Manager if the
command device of the external storage has been mapped on the subsystem.
Any additional license is not required to use the function.
Note When the command device of the external volume is mapped (Remote Command
Device exists), it is not allowed to downgrade the micro-program to an unsupported
version. It is required to downgrade the micro-program to an unsupported version
after having performed Delete LU for all the Remote Command Devices.
If a failure occurs between the RAID500 and an external storage, or CHECK is
responded from the command device of an external storage, Remote Command
Device will send Aborted Command to the host, instead of sense data of the external
storage command device.
If registering 2,048 pairs or more to the Configuration file for Remote Command
Device, “HORCM inst 0 has failed to start” might be displayed without causing any
problems when RAID Manager is on start-up.
The function is not supported for RAID300.
The change of contents for Version 50-05-06-00/00
1 MPs Blockade during SVP Rebooting

Phenomena A hardware failure (CHK1B) occurred during SVP rebooting. The MPs
without the hardware failure were blocked one after another due to invalid
access.
Severity (High, Medium, Low)
Conditions of Occurrence This problem occurs when all the conditions are met.
1. In case of a LAN failure, or the status of resource being locked due to
anyone of following operations:
SVP reboot/SVP replace/CSW replace/PS-OFF/Def & Inst,
2. A hardware failure (CHK1B/CHK3/WCHK1).
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 50-05-06-00/00
Category LAN
2 Path disconnection delayed in TCA/TCZA when no I/O is issued

(Mode12 ON)
Phenomena In the TCA/TCZA configuration, when RCU was powered on while no I/O
operation was in progress and the Mode12 was ON, the SIM indicating the
path disconnection occurred every 10 minutes or so. In the end, all paths
were disconnected, and the pairs were suspended (Suspend is expected, but
the time until suspend is not proper).
Severity (High, Medium, Low) Low
1. TCA/TCZA (Initial copy completed)
2. No Host I/O
3. Mode12 ON
4. All paths between MCU and RCU are disconnected
Category True Copy Async/ True Copy for z/OS Async
3 PDEV correction access display is added to LDEV panel

Phenomena When correction copy and correction access take place at the same time in
the case of 6D+2P, the correction access status is not displayed in
maintenance LDEV panel.
Conditions of Occurrence This problem occurs when correction copy and correction access occur at
the same time in the case of 6D+2P.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 50-05-05/00
Category SVP
Changed Part SVP
4 SSB=C709 occurs many times when paths between MCU and
RCU are disconnected during TC/TCZ operation
Phenomena When a TC/TCZ operation was in progress, all paths between MCU and
RCU were disconnected, and the pair was suspended in RCU due to a
failure. In this case, SSB=C709 (Logical inconsistency in obtaining path
information during Async attention) occurred many times in the initiator to
which the paths between subsystems are connected.
1. TC/TCZ/UR/URZ operation is in progress (Initial copy, update copy, or
pair operation.),
2. CU free paths and CU paths are defined between MCU and RCU,
3. The same RCU is shared by the CU free paths and the CU paths,
4. All CU paths in #2 are disconnected/ or have a failure,
5. The pair is suspended (Async only)/ or suspend operation is performed.
Category Universal Replicator/ Universal Replicator/ for z/OS/ True Copy/ True
Copy for z/OS
5 SSB=413e occurs during Cache/SM maintenance operation

Phenomena If a maintenance operation of cache/SM is performed during I/O operation,
SSB=413e (invalid cause of wait at the time timeout is detected) may
occur.
1. OPEN PCB is installed.
2. A maintenance operation is performed or failure occurs in cache/SM
during I/O operation with heavy workloads.
3. During the maintenance operation/failure in the above 2, the resource
used for data transfer is not available for 15 seconds.
Category Cache
6 Power failure in DKU in NSC model

Phenomena Normally, when a DKU power failure occurs, only HDD port is blocked,
but HDD is not. However, when a power failure occurs in DKU in the
NSC model for a short period, PDEV may be blocked.
Severity (High, Medium, Low) Medium
1. NSC model
2. Power failure does not occur in DKC, but it occurs only in DKU.
3. Power failure continues for about 100ms to 1.2 seconds
Affected Products/Version DKCMAIN: 50-03-89-00/00 and higher
Category DKU
7 Change the results of shredding operation displayed in
confirmation dialog
Phenomena When a shredding operation is performed, the result is displayed as
follows.
The shredding operation ended normally. --> Normal
The shredding operation was not performed. --> Not Execute
The shredding operation was cancelled. --> Discontinuation end
The shredding operation was ended abnormally. --> Shredding Failed
Conditions of Occurrence This problem occurs when a shredding operation is performed, and a
confirmation dialog is displayed.
Causes and Updates The micro-program has been modified so that following will be displayed.
The shredding operation ended normally. --> Shredding operation normal.
The shredding operation was not performed. --> Shredding operation not
executed.
The shredding operation was cancelled. --> Shredding operation cancelled.
The shredding operation was ended abnormally. --> Shredding operation
failed.
Category Volume Shredder
Changed Part SVP
8 Cache Maintenance Improvement

Phenomena When an SM replacement failed during maintenance due to a cache PCB
failure, the cache failure was not reported.
Conditions of Occurrence Same as phenomena.
Causes and Updates The micro-program has been modified to fix the problem.
When an SM replacement fails due to a cache PCB failure, a new SIM －
RC: FFF9-0 ｘ (ｘ０: CL-1, １: CL-2) will be reported.
Category SM
9 Display External Volume in spreadsheet

Phenomena Even if external volumes are included in the configuration, they are not
displayed in the spreadsheet.
Conditions of Occurrence This problem occurs when external volumes are included in the subsystem.
Category SVP
Changed Part SVP
10 Failed to unlock resource due to CHK3
Phenomena When an SHSN failure occurs, the resource can not be unlocked.
Conditions of Occurrence This problem occurs when an SHSN path failure occurs at the time of SM
write access in a resource unlock processing.
Category SM
11 Dirty data is not de-staged to External VOL and remains in

RAID500
Phenomena An external subsystem was powered off first, and then RAID500 was
powered off. Since the external volume was blocked first, the dirty data
could not be de-staged to the external VOL, and it remained in the cache
memory in RAID500. However, since the external VOL was blocked, the
P/S OFF was performed successfully even if dirty data remained, and the
cache memory was powered off. As a result, when RAID500 was powered
on next time, the dirty slot became pinned slot.
Severity (High, Medium, Low) High
1. An external volume exists
2. The path set to the external volume is blocked (Including the case where
external volume is powered off first)
3. After PS-OFF, non-volatile PS-ON
Category Universal Volume Manager
12 HTP failure SSB generated at the time of FICON online micro

program exchange
Phenomena During FICON online micro program exchange, the HTP failure SSB
(SSB=0x7A20/HTPLOG=0x5118) may be generated.
- FICON
- Online micro program exchange
- MP reboot and a host I/O do not take place concurrently
Category Mainframe
13 I/O not processed due to emergency de-stage

Phenomena When an emergency de-stage is performed due to cache/SM installation,
replace, or failure, the Host I/O to UVM volume is not processed.
1. I/O operation is performed to UVM volume
2. Cache/SM installation, replace, failure
When all of the conditions are met, the host I/O cannot be processed
because the emergency de-stages occupies the processor and uses transfer
resources.
14 Input allowed falsely at the time of Refer Configuration

Phenomena In Refer Configuration, if you select [System Option] in the DKC
Configuration panel and then [Mode…] in the System Option panel, all
items in the Mode panel are grayed out when you select "System" for LPR
(LPR: System). However, if you change the LPR to "LPR01" (example)
and change it to "System" again, the "Cache Tuning" and "Command
Control" are not grayed out.
Conditions of Occurrence This problem occurs when you change "LPR: System" to "LPR: LPRXX",
and then to "LPR: System" again in Refer Configuration.
Since data is not changed in Refer Configuration, this is the problem in
display only (No impact on data etc.).
Affected Products/Version SVP: 50-03-02/00 and higher
Category SVP
Changed Part SVP
15 SM path blocked due to PS ON

Phenomena When PS ON is performed, or when a package is replaced, SM path may
be blocked.
In such a case, the following SIM is displayed.
SIM=760200 (CUDG3 DETECTED ERROR)
SIM=3287XX (LOGICAL PATH BLOCKADE[CHA])
Conditions of Occurrence This problem occurs when PS ON of the DKC is performed, or when a
package other than DKF and CHN is replaced.
Chance of occurrence: Approximately 1/40000
Category SM
16 Failed to Make LUSE Volume with Maximum LDEV Number

Phenomena When combining LDEV with the maximum number (16,384 LDEV) to
make an LUSE volume at a time, a logical error occurred.
SVP: "Logical error has occurred."
Storage Navigator: "(3, 3003) An error occurred during processing. If this
problem persists, please call the XXX"
Conditions of Occurrence This problem occurs when 16,384 LDEV (maximum number of Open
LDEV) are combined to make an LUSE at a time. Since such
configuration is rare, the chance of occurrence is very low.
If at least one command device is included, it cannot be combined with
other LDEV to make an LUSE volume at a time. Therefore, this problem
will not occur.
Category SVP
Changed Part SVP
17 Problem in checking max LUSE size

Phenomena An LUSE volume larger than the maximum size (64,424,505,600 KB) can
be created.
Conditions of Occurrence This problem occurs when the total size of LDEV that constitute an LUSE
exceeds 64,424,505,600 KB.
Category SVP
Changed Part SVP
18 EC=CC14 after power cycle in Async MCU

Phenomena After a power cycle in Async MCU, the pair was suspended with
EC=CC14.
Conditions of Occurrence This problem may occur when all the conditions are met.
- TCZ/TC Async
- Power cycle is performed in MCU when the pair is in the
Duplex/Pending state
Category True Copy Async/True Copy for z/OS Async
19 Invalid Display for SIM Details

Phenomena When the details of SIM (bf7x1y) of a FAN failure in the NSC model are
displayed, a wrong part is displayed as a failed part in the LOCATION.
1. NSC model
2. A FAN failure occurs in other than FFAN11/FFAN22
3. The details of the SIM are displayed
Category SVP
Changed Part SVP
20 Confirmation message at time of SM installation/un-installation

Phenomena When the checkbox of the Install function is not set properly at the time of
SM installation/un-installation, you need to perform the installation/un-
installation again, and it will take an hour or longer.
Conditions of Occurrence This problem occurs when the checkbox of Install function is not set
properly at the time of SM installation/un-installation.
Causes and Updates The micro-program has been modified so that, in this case, the following
message will be displayed to draw CE's attention. Please make sure that
the "Install function" is set properly. Do you want to continue?
Category SM
Changed Part SVP
21 UR/URZ Pair Failure Suspend during Initial Copy

Phenomena UR/URZ pair suspend due to reset other than WCHK1 during initial copy.
1. UR/URZ initial copy (Copy all data (Initial job start only)/Resync (Not
all data is differential data))
2. Reset during UR/URZ initial copy
Category Universal Replicator/ Universal Replicator for z/OS
22 Invalid SIM Report

Phenomena When the side file sleep waiting time exceeded the threshold while using
TCZ, SIM was not reported for each CLPR.
Conditions of Occurrence SIM=490x is reported when the side file sleep waiting time exceeds the
threshold while using TCZ Async or HXRC.
Category True Copy for z/OS
23 [UVM] Message indicating insufficient licensed capacity is

displayed when Add LU is performed
Phenomena When setting Add LU in the [LU Operation] panel in Universal Volume
Manager and selecting the [Apply] button, an error message (605 56521)
was displayed, and the Add LU operation could not be performed.
Conditions of Occurrence This problem occurs when either of the following conditions is met.
1. The Add LU operation is performed when the licensed capacity is
exceeded.
2. The licensed capacity will be insufficient because of the Add LU
operation.
Changed Part SVP
24 Communication error (STW0117W)

Phenomena When trying to open the SVP maintenance panel, a communication error
(STW0117W) occurs.
- MF package is installed
- High I/O workload (MP operating rate=80% and Cache hit rate=100%)
Category SVP
25 MCU SSB=d1ea, d2c9, 1470 when Replacing SM or CM

Phenomena If a dummy replacement of CACHE-1CA or SM-1SA package was
performed at MCU while an I/O operation was in progress in the True
Copy + UR configuration, MCU SSB=d1ea, d2c9, 1470 occurred.
Conditions of Occurrence This problem occurs when either SM or CM is replaced during an I/O
operation in the True Copy + UR configuration.
Category OPEN
26 SVP reboots repeatedly

Phenomena SVP reboots repeatedly.
Conditions of Occurrence Invalid log file data is detected when reading monitor data files.
Category SVP
Changed Part SVP
27 Same SIM occur at the same time

Phenomena Another SIM, with same Reference Code as completed SIM is recorded.
Conditions of Occurrence When the SIM complete operation is carried out during the polling
processing for a remote SIM report function.
Category SVP
Changed Part SVP
28 SSB=13c6, b845 in ENAS

Phenomena When an I/O is issued to an ENAS volume of a TC Sync pair, SSB=13c6,
b845 occur.
1. I/O is issued to the True Copy Sync pair volume.
2. The target PVOL is an ENAS volume
3. PCR is set to the ENAS volume
Category Universal Replicator
29 After Reverse _ resync during copy operation, Pending remains

Phenomena Initial copy of TC Sync does not progress.
- TC Sync
- Swap-Suspend/Reverse _ Resync is performed to the pair in the Duplex-
Pending state (copying)
- The operation is performed from the RAID Manager library
Category True Copy
30 Error is not output in Audit Log Basic information

Phenomena When Relationship Expansion/delete in Flash Copy Mirror Version2 of
Shadow Image z/OS fails in Storage Navigator, the error is not output to
the basic information in the Audit Log. "Normal End" is output, instead.
Conditions of Occurrence This problem occurs when all the conditions are met in Shadow Image
z/OS in Storage Navigator.
- Relationship Expansion and delete failed in Flash Copy Mirror Version2.
- Option setting failed.
Category Storage Navigator
Changed Part SVP
31 LDEV Emulation 3390-3B Misjudged as Mainframe VOL

Phenomena When assigning LUN to a 3390-3B volume (multiplatform volume) using
Storage Navigator, “3390-3B” LDEV is not displayed in the LDEV list in
the LUN Manager panel.
Conditions of Occurrence When both of the following conditions (A and B) are met, this problem
occurs.
A. RAID500
V04 DKC 50-04-06-00/00 (SVP 50-04-06/00) and later
V04+1 DKC 50-04-28-00/00 (SVP 50-04-27/00) and later
V04+2 DKC 50-04-40-00/00 (SVP 50-04-40/00) and later
B. The following emulation types are installed.

3380-3B, 3380-3C, 3380-KB, 3380-KC,
3390-3B, 3390-3C, 3390-9B, 3390-9C,
3390-LB, 3390-LC, 3390-MB, 3390-MC
Category LUN Manager/ Universal Replicator for z/OS/ True Copy for z/OS/ True
Copy for z/OS Async/ Shadow Image for z/OS/ Volume Security
Changed Part SVP
32 UR/URZ pair suspends at the time of Resync-Swap/takeover

Phenomena A UR/URZ pair suspended at the time of Resync-Swap/takeover due to a
failure.
- UR/URZ pair
- Mirror# is other than 0 (Mirror#1-3 are used)
- Resync-Swap is performed
33 Problem in the displayed number of Flash Copy Mirror

Version2 relationships
Phenomena If you open the Shadow Image z/OS Flash Copy Info panel while Copy-
on-Write Snapshot pair exists, the total number of Flash Copy Mirror
Version 2 relationships and Copy-on-Write Snapshot pairs is displayed as
the number of relationships.
Conditions of Occurrence This problem occurs when a Copy-on-Write snapshot pair exists.
Category Shadow Image for z/OS/ Flash Copy V2
34 Pair deleted in JNL group in the Halting/Stopping state

Phenomena When the following procedure was performed, an error message (6505-
8753) "internal error" was displayed.
1. Delete a pair from the JNL operation panel of UR/URZ. The JNL group
status is changed to "Halting".
2. Wait for a while, and delete a pair again in the same JNL group. (The
JNL group status has been already changed from "Halting" to "Initial".
However, since the panel is not refreshed, "Halting" is displayed in the
panel.)
3. A message (6505-8753) is displayed.

Conditions of Occurrence This problem occurs when the following condition is met.
- Delete a pair when the actual JNL group is in the Initial state, but the JNL
group status is not displayed as "Initial".
35 Invalid ACC Parts Kind Code (PKC1)

Phenomena A failure occurred in the cache memory module or in the shared memory
module. When the SIM was generated, the ACC PKC1 was (00), which is
not a defined value).
Conditions of Occurrence This problem occurs when either of the following conditions is met.
1. A failure occurred in the cache memory module installed in the option
CACHE PCB
2. A failure occurred in the shared memory module installed in the option
SM PCB
Category SVP
Changed Part SVP
36 SSB=9680 occurred in Flash Copy Mirror Version2

Phenomena SSB=9680 may occur right after PS/ON or when a relationship is
established/deleted. If it does not cause Job ABEND etc., it will not cause
any problem.
Conditions of Occurrence This problem occurs when any of the conditions is met.
- Right after PS/ON
- A relationship is established.
- A relationship is deleted.
Category Flash Copy Version 2
37 TCZA Initial Copy progress remains 99%

Phenomena When an initial copy is performed and an update I/O is issued in TCZA,
the pair suspends. The copy progress of the initial copy pair in the same
CT group remains 99%, and the pair status is not changed to Duplex.
1. True Copy for z/OS
2. When creating a pair with volumes and the suspend range specified.
3. Initial copy or pair resync is in progress
4. The copy convert process detects logical inconsistency and the pair is
suspended, and the last RSCB of the initial copy is scheduled in the same
schedule.
38 LUSE volumes displayed in UR/URZ panels wrongly

Phenomena Though UR/URZ does not support LUSE, LUSE volumes are displayed in
the Free Volumes list in the Edit JNL Volumes panel and in the UR pair
operation panel.
When LUSE volumes are registered as JNL volumes or pairs, the main
program returns errors.
Conditions of Occurrence This problem occurs when LUSE volumes exist.
Changed Part SVP
39 SSB=23C9 occurred when Relationship Expansion (Disable-

>Enable) is performed
Phenomena When INITIALIZE or Relationship Expansion (Disable->Enable)/(Enable-
>Disable) is in progress, FCv2 relationship creation/deletion is performed
by FCv1. (SSB=23C8, 23C9)
Conditions of Occurrence This problem occurs when a relationship is created or deleted under the
following conditions.
1. FCv2 and FCv1 Program Products are installed.
2. INITIALIZE or Relationship Expansion (Disable->Enable)/ (Enable-
>Disable) is in progress.
40 SIM not displayed in Status panel in Storage Navigator

Phenomena After SVP is rebooted, SIM are not displayed in the Status panel in Storage
Navigator.
Conditions of Occurrence This problem occurs when SVP is rebooted after all SIM are completed.
Category SVP
Changed Part SVP
41 After Reverse Resync in cascading configuration, data is not

copied
Phenomena In a cascading configuration (TC/TCZ Synchronous->UR/URZ), when the
Sync pair was suspended, Takeover was executed to UR/URZ to reverse
the copy direction. After that, an I/O was issued, but the data was not
copied to Sync.
1. Cascade configuration (Site1-TC/TCz Sync -> Site2-UR/URz -> Site3)
2. Suspend the sync pair
3. Execute Takeover to the UR/URZ pair (Site1 -> sync (SUS) -> Site2 <-
UR-Site3)
4. Issue I/O from Site3
5. Change the copy direction (Site1 <- sync (SUS) <- Site2) and resync
In this case, the data is not copied to Site1 (by I/O in 4).
Category True Copy/ True Copy for z/OS/ Universal Replicator/ Universal
Replicator for z/OS
42 Logical Inconsistency Error

Phenomena When deleting the FCv2 relationship by specifying TDEVN/DDSW (no),
9681 (Failed to lock) occurred.
Conditions of Occurrence This problem may occur when you delete multiple relationships at a time.
Since the retry is successful, the problem does not cause any damage.

43 Timeout error occurred when FCv2 Info panel was refreshed

Phenomena Storage Navigator panel was displayed during an initial copy of FCv2
relationship (the FCv2 Info panel was refreshed), "A Timeout error
occurred, and panel could not be displayed. SSB=22be was output.
1. One or more of following program products are performed:
Shadow Image, Shadow Image for ZOS and Compatible Mirroring for
IBM Flash Copy, Cross System Copy, or Volume Migration operation
2. Compatible Mirroring for Compatible Mirroring for IBM Flash Copy
Version 2 operation is performed.
44 Pair Suspend when TC/TCZ Pair Resync

Phenomena Resync operation was performed to TC/TCZ SUSPEND pair during host
I/O processing, SSB=cb92 occurred, and the pair was suspended.
1. TC/TCZ or TCA/TCZA
2. While executing a host I/O whose processing time is long to a TC/TCZ
SUSPEND pair, perform a Resync operation to the pair.
Category TC/ TCZ/ TCA/ TCZA
45 TCA/ TCZA Performance Degradation and Pair Suspend.

Phenomena A delay in completing the write operation, host performance degradation,
and a TCA/ TCZA pair suspend occurred.
Conditions of Occurrence Problem occurred when updated I/O is issued to a certain M-VOL and the
TCA/ TCZA R-VOL includes HDD that has a problem.
46 WCHK1 occurred when VOS3 refers to SIZ pair status

Phenomena When a command (query, vary on/off, CHP on/off) was issued from a
mainframe host, a WCHK1 occurred, and the MP was blocked.
Conditions of Occurrence This problem occurs when a command (query, vary on/off, CHP on/off)
which refers to SI status is issued from the M series host in such a
condition where a logical inconsistency occurs.
Category Shadow Image for z/OS
47 EC=4874 occurred when URZ timer type is LOCAL

Phenomena When "LOCAL" is specified as the Timer Type of the URZ journal group
option, if a time-stamp is not attached by the host, EC=4874 is output.
1. URZ pair
2. Specify LOCAL as the timer type of the journal group option.
3. A timestamp is not attached by the host
Category Universal Replicator for z/OS
48 MF package MP is blocked, ongoing Jobs cannot be stopped

Phenomena When MF package MP is blocked completely during LDEV Format, the
LDEV format cannot be stopped.
1. Both MF package and OPEN package are included
2. MF PCB MP is completely blocked during LDEV Format, Cache/SM
replace, Cache/SM blockade, or Async job.
Category FICON/ESCON
49 SSB=ec41/ec44/ec17/ec01 URZ pair suspend at Intermediate site

Phenomena URZ pair was suspended due to a failure at the Intermediate site during an
initial copy in a cascading configuration, SSB=ec41/ec44/ec17/ec01 was
output, and all the data in the VOL became differential data.
1. URZ cascading configuration
2. URZ pair at the Intermediate Site was suspended due to a failure during
an initial copy operation
50 When Verify is stopped, an error (ONL2788E) is displayed

Phenomena When the Stop button was selected during the verify function was running,
an error (ONL2788E) was displayed.
Conditions of Occurrence This problem occurs when the NSC mode (MIX PCB) is used.
Category SVP
Changed Part SVP
51 Wrong SIM (D40x) Reported when TCZ Pair Suspend

Phenomena When a pair was suspended after Incomplete Locate Domain was detected,
SIM D40x (Suspend due to RIO path blockade) was reported wrongly.
- TCZ
- CCW which causes Incomplete Locate Domain is issued.
Causes and Updates The micro-program has been modified so that SIM D41x (Suspend due P-
VOL failure) will be reported in this case.
52 Relationships could not be established with SSB=9652

Phenomena Online micro program exchange performed while relationships were
established in units of FCv2 DS, SSB=9652 (function bit is not ON)
occurred in a CU, and the relationships could not be established.
Conditions of Occurrence This problem occurs when MP is rebooted and blocked at the same time
(Ex. online micro program exchange, multi PCBs replace etc.)
Category Function Bit
53 ONL0117E occurred when Verify/LDEV Format was stopped

Phenomena After the Verify/LDEV Format was selected, when the Stop button was
selected, an error (ONL0117E) is displayed.
Conditions of Occurrence This problem occurs when the Stop button is selected after the
Verify/LDEV Format is selected while the progress is being obtained.
(This problem seldom occurs)
Category SVP
Changed Part SVP
54 Invalid Copy Judgment

Phenomena When data was written to the P-VOL using the old type of CKD command,
the old data was not copied from the P-VOL to the S-VOL.
- FCV2 is used
- Issuing a WRITE command during chain command processing after a
SEARCH command has been issued.
55 SSB generated due to invalid parameter of demotion

Phenomena When DX/LOC/RDTRK/RDTRK/RDTRK/RDTRK/RDTRK command is
issued, SSB: 5760, 13b5 occurred in T-VOL (Demotion process ended
abnormally (Invalid parameter/Lock TOV etc.))
- No record (From R1) exists in the target track
- FCv2 S-VOL received sequential RDTRK command
- Demotion is performed in TRK SW
56 E7 command LOC_ERS track overrun

Phenomena When an E7 command LOC_ERS, whose starting point of ERASE
exceeds the end of the track, is issued, it should end with DSB=0E due to a
track overrun error. However, the track is switched, and the next track is
erased, and the command ends with DSB=0C.
In the case of 47,4B command LOC_ERS, a track overrun occurs and it
ends with DSB=0E.
- DKC emulation type: 2105
- When using the E7 command LOC_ERS; the starting point of ERASE
exceeds the end of the track.
Category Mainframe
57 Data Retention Utility (VMA) VOL can be registered as JNL-

VOL
Phenomena You can register a VOL that has a Data Retention Utility VMA setting and
has no LDEV Guard setting as a JNL-VOL (It should not be allowed
according to the specification).
Note: The volume can be used as a JNL-VOL normally. Since it is used as
a JNL-VOL, LDEV Guard cannot be set, and its attribute cannot be
changed to other than Read/Write. After JNL-VOL is deleted, the volume
can be used with the VMA setting.
Conditions of Occurrence This problem occurs when JNL-VOL is registered by selecting a volume
that satisfies the following conditions.
1. Data Retention Utility VMA is set.
2. The Data Retention Utility attribute is "Read/Write" (No setting)
3. No SCSI path is defined
Category Universal Replicator
58 Multiple Failed Parts Report when ACDC Alarm

Phenomena When ACDC alarm was detected in the NSC model, multiple failed parts
(both RK0 (RK1) and RK2 (RK3)) were pointed out.
- NSC model
- Additional DKU is installed
- ACDC alarm failure occurs
Category DKU
59 Performance degraded after TCZ Async initial copy

Phenomena After a TCZ Async initial copy is completed, the host I/O performance
degraded.
Conditions of Occurrence The host I/O performance to the DEV to which a TCZ Async initial copy
(including Resync) was performed.
60 Improper pair status displayed after MCU DKC PS-OFF

Phenomena After having powered off the MCU DKC while a UR/URZ pair existed,
the UR/URZ pair displayed as the COPY or PAIR status in the Pair
Operation panel of Storage Navigator was displayed wrongly as the PSUE
status in the Pair display panel.
- UR/URZ pair exists.
- Power off MCU DKC.
- Refresh the Pair display panel of Storage Navigator at RCU.
61 SSB=9680 occurred in Flash Copy Mirror Version2

Phenomena When a relation is established/deleted, SSB = 9680 may occur. The log is
output only.
- A relationship is established.
- A relationship is deleted.
62 Problem in monitoring path status

Phenomena When disconnecting an external storage (DF600H) path, it took long
(about 30 minutes) to block the path. Until it was blocked, the external
volume was 100% busy.
1. In the R500-Switch-External storage configuration, a path was
disconnected by a switch operation, and a panel (Storage Navigator)
refresh/discovery was performed.
2. In the R500-Switch-External storage configuration, a path between a
switch and external storage was disconnected, and a panel (Storage
Navigator) refresh/discovery was performed.
63 Problem in displaying operating information

Phenomena Invalid values are displayed in HUR USAGE (MCU/RCU Data Used Rate
and Meta Data Used Rate).
1. Suspend or delete a journal group, and delete a journal volume (Volume
A) from the journal group.
2. After 1, register the Volume A to a journal group (any journal group
number) as a journal volume.
64 Pending remains after HUR Resync

Phenomena The progress of initial copy remains at 0%.
Conditions of Occurrence Problem may occur when the following operations are performed in order.
1. Create the number of pairs equal to or more than the threshold of the
number of copies (Default: 64 pairs) without copying data (Storage
Navigator instruction).
2. Suspend or delete the devices paired in 1.
3. The number of pairs equal to or more than the threshold of the number
of copies by copying all data (Host instruction).
4. Execute the following operations during copy operation in 3.
4-1: Copy the differential data of the pairs suspended in 2 (host instruction)
or copy all the data after deleting it in 2 (host instruction).
4-2: Suspend the pairs created in 4-1.
4-3: Copy the differential data of the pairs suspended in 4-2 again.
65 Different DKC Emulation Types Cannot be Intermixed

Phenomena When setting different DKC emulation types for each 4 ports, the LCP or
HTP of the last 4 ports did not work with the set DKC emulation type.
1. ESCON (xx-8S) or FICON FIVE package (xx-16ML or xx-16MS),
2. Different DKC emulation types are set to the first 4 ports and the last 4
ports.
Category ESCON/FICON
66 Duplicated SCSI path definition

Phenomena 1. When Discovery is performed from HDVM, an error occurs.
2. In the LUNM panel in SVP and in the LUNM panel/common
information panel in Storage Navigator, two or more of the same SCSI
path are displayed.
Conditions of Occurrence This problem may occur in rare cases when the following operations are
performed in order.
1. Apply multiple LUNM setting changes from Storage Navigator
2. A communication error occurs during a setting update operation
3. The same setting is performed again, and it ends normally.
Category LUN Manager
Changed Part SVP
67 Copy Time displayed improperly in history panel when pair

suspended
Phenomena In the TC/UR History Operation panel, some of the Start Date/Time and
Copy Time may not be displayed (---/--/-- --:--:-- may be displayed).
1. TC/TCZ/UR/URZ pairs,
2. Operations are performed in the following order (Pair suspend -->Pair
create-->Pair create complete), but the logs were reported to the SVP in a
different order ("Pair create-->Pair suspend-->Pair create complete", or
"Pair create complete-->Pair suspend-->Pair create").
However, since the data with Start Data/Time and Copy Time is only kept
for one pair per LDEV, this countermeasure might not work in case of
different log orders.
Replicator for z/OS
Changed Part SVP
68 When last slot of External VOL is Pinned slot, SI pair suspends
Phenomena When an internal VOL and an external VOL are paired using Shadow
Image (Copy direction: Internal VOL =>External VOL), if the last slot of
the VOL is a pinned slot, data cannot be copied, and the pair will be
suspended.
- UVM is used
- A Shadow Image pair (Copy direction: Internal volume => External
volume)
- The external volume size cannot be divided by 256KB
- The last slot of the target external volume (in 2) contains pinned data
- OPEN-V
Category Shadow Image
69 MSG cells become insufficient because MSG are released

wrongly
Phenomena FCv2 I/O in progress, the pair Suspends, host job abend and SVP cannot
be communicated. SSB=12c4 ( PDEV message FIFO is full) occurs.
Conditions of Occurrence This problem may occur when any of the conditions is met.
- Maintenance operation of DKA/HDD (DKA/HDD
REPLACE/Installation/Micro program exchange) is performed
- SIZ pair exists.
- FCv2 pair exists.
- QS pair exists.
70 Shadow Image history not displayed when PSOFF is performed

Phenomena When volatile PSON is performed, some of the history information is not
displayed in History panel of Shadow Image/Shadow Image for z/OS in
Storage Navigator. (If Shadow Image FlashCopyV2, SSB: 969a is output.)
Conditions of Occurrence This problem occurs when the following operations are performed in order.
1. Nonvolatile PSOFF/ON is performed.

2. Shadow Image/Shadow Image for ZOS/Shadow Image Flash Copy V1
operation is performed.
3. After 2, volatile PSOFF/ON is performed.
Category Shadow Image/ Shadow Image for z/OS
71 Change "Copy central" to "BC Manager" in SVP message 2031

Phenomena In the SVP message (ID2031), "Copy central", which is the old name of
"BC Manager", is displayed.
Conditions of Occurrence This problem occurs when the SVP message (ID2031) is displayed.
Category SVP
Changed Part SVP
72 Details of Copy-on-Write Snapshot SIM not displayed properly

Phenomena When details of SIM related to Copy-on-Write Snapshot are displayed in
SVP, "QUICKSHADOW ERROR" is displayed in "Error Section".
Conditions of Occurrence This problem occurs when details of the following four SIM are displayed
in SVP.
- RC=47ec00
- RC=4b3xyy
- RC=6000xx
- RC=6001xx
Causes and Updates The micro-program has been modified so that "Copy-on-Write Snapshot
Error" will be displayed in this case.
Category SVP
Changed Part SVP
73 SSB=4874 when SUSPEND/DELPAIR for a TCZA Pair

Phenomena When a TCZA pair where an I/O operation was in progress was suspended
or deleted, SSB=4874 was reported.
1. TCZA pair
2. The pair is suspended or deleted when an I/O operation is in progress.
74 Problem in RECSET scheduling

Phenomena TC/TCZ Async used, SSB=C828 is reported, and the pair is suspended.
- True Copy/True Copy for z/OS Async is used
- Side File is overloaded at RCU
75 Retry SLEEP threshold exceeded due to target slot busy

Phenomena When copy operation of an FCv2 pair was performed in COPY mode, or
when copy operation performed when a relationship was being withdrawn,
slot contention repeatedly occurred, and relationship suspended.
- Flash Copy V2 pair
- I/O is issued to the area outside the FCv2 extent in the target device.
- Copy operation is performed in the COPY mode or with WITHDRAW
- Contention between Copy JOB and host I/O occurs in the same slot 256
times in sequence.
76 [TC/UR] Adding Recovery process after monitor error

Phenomena When a graph is displayed in the Usage Monitor panel of
TC/TCZ/UR/URZ, if the Install panel is opened from the SVP launcher,
the (2, 5510) error occurs. If you respond to the message, the panel will be
grayed out. After refreshing the display, the graph is displayed, but the
progress remains the same. The same phenomenon occurs also in the
TC/TCZ/UR/URZ Usage panel launched in the Performance panel.
Conditions of Occurrence - If a graph is displayed in Usage Monitor panel and a error occurs during
opening of Install panel from SVP launcher, Refresh is required to restore.
- The same phenomenon occurs also in the TC/TCZ/UR/URZ Usage panel
launched from the Performance panel.
Replicator for z/OS
77 DSB85 not reported when suborders 15/16 of F3 command

Phenomena When the suborder 15 (Suppress FCV2) or 16 (Lift suppression of FCV2)
of the Diagnostic Control (F3) command is received, State Change
Interrupt (DSB85) is not reported to the host. As a result, the following
phenomenon occurs after this command is received.
F3-15 received: FlashCopyV2 operation ends abnormally (FDMSDSS)
F3-16 received: FlashCopyV2 operation is not performed, and data may be
copied via the host (FDMSDSS).
Conditions of Occurrence The problem occurs when suborders 15 or 16 of the Diagnostic Control
(F3) command is received.
78 LA Error When Cache Failure

Phenomena During an initial copy of an HUR pair, when a cache package was blocked,
SIM=cf8143, cf8103 (DKA CHK2) occurred. There was no problem
though CHK2 occurred due to a cache failure. However, when writing data
to the SI S-VOL, an LA error occurred later.
1. A cache failure occurred
2. FCA/DX2 hangs
3. Padding is performed
79 PINNED SLOT & Failure Suspend when SM Failure

Phenomena SM failure occurred, the PINNED SLOT and failure suspend might occur.
1. URZ pair
2. When JNL data is being transferred, a reset (CHK3) occurs.
80 URZ pair suspend due to CHK2

Phenomena If CHK2 occurs during JNL/JNCB transfer, URZ pair may suspend.
1. URZ pair
2. Pair suspend due to SSB=BBXX
3. CHK2 occurs during JNL/JNCB transfer on the same MP as #2.
81 TCZ Pair Status Change Failure

Phenomena A volume suspend of TCZ was performed. After pairs were suspended,
Resync was started, and it took time to change the pair status. As a result,
MIH (RIO wait) occurred.
Conditions of Occurrence Problem occurs when a pair operation is performed if the number of pairs
or the number of CT groups is large, and the CHP operating rate is high.
82 HUR pair suspend due to SSB=8e11, JNCB ALL0

Phenomena During cache maintenance while an I/O operation was in progress, the pair
was suspended due to a failure.
1. I/O issued from same host path to P-VOL belonging to multiple JNLG.
2. Any of the following operations is performed
A. Pair creation or Resync in a JNL group
B. Maintenance operation of CM/SM
C. Collection copy of journal volume
D. CLPR change operation
83 Rollback Feature Support in TC-Async

Phenomena With rollback command issued to TC-Async pair group, new pair cannot
be added.
Conditions of Occurrence This problem occurs when a pair split -RB (rollback command) command
is issued from RAID Manager to the TC-Async pair in the SSWS status.
Category True Copy Async
84 Invalid SIM=BF81A3
Phenomena If power interruption exceeded power outage limit, SIM=BF81A3 (error in
DKC power alarm deterrence) was reported invalidly after power recovery.
Category SSVP
Changed Part SSVP
85 DRU Setting Failure when TCA in PAIR/COPY Status

Phenomena When a True Copy Async pair was in PAIR/COPY status, the setting of
Data Retention Utility could not be reflected on the secondary volume.
1. A TC Async pair is in the COPY or PAIR status,
2. Setting Read Only to Protect or Protect to Read Only for a volume in the
VMA area by using Data Retention Utility.
86 Throughput Degradation when Adding JNL VOL

Phenomena When adding JNL VOL of UR/URZ online, the throughput degraded
heavily (from 160 MB/S to 1 MB/S).
Conditions of Occurrence This problem occurs when conditions #1 and #2 are met or condition #3 is
met.
1. Capacity of JNL VOL is small,
2. Update I/Os on UR/URZ volumes are in progress,
3. When the JNL VOL is full due to a path failure between MCU and
RCU.
87 MPs Blockade due to Processor Cache Error Exception of

FICON PCB
Phenomena MPs were blocked due to processor cache error exception of FICON PCB.
Category FICON
88 TC/TC Async/UR Pair Suspend

Phenomena When an external storage path failure occurred, the TC/TC Async/UR pairs
were suspended.
SSB: c761, cd29, cd33, 12c9 occurred.
Conditions of Occurrence A. All versions of RAID500
B. An external subsystem is connected (either Universal Volume Manager
or Cross-System Copy is installed), and alternate paths are defined.
C. True Copy/True Copy for z/OS/True Copy Async/True Copy Async for
z/OS/Universal Replicator/Universal Replicator for z/OS are in use.
When all the conditions (A-C) are met, if any of the following failures
occurs, this phenomenon may occur.
a) A failure in a path between RAID500 and external storage
b) External device failure
c) RAID500 failure
d) Invalid response from the external device
Category True Copy/ True Copy for z/OS/ True Copy Async/ True Copy Async for
z/OS/ Universal Replicator/ Universal Replicator for z/OS/ Universal
Volume Manager/ Cross-System Copy
89 Invalid SIM "Error location" Display on SVP

Phenomena When displaying the SIM for the POOL failure of Copy-on-Write
Snapshot on SVP, the "Error location", which was in hexadecimal, was
different from the one displayed on the Copy-on-Write Snapshot panel
(decimal).
Conditions of Occurrence This problem occurs when displaying the following two SIM-RCS on the
SIM details panel of SVP.
RC=6000xx, RC=6001xx
Category SVP
Changed Part SVP
90 Invalid Restore JNL Group Status when Suspending UR/URZ

Pairs
Phenomena When suspending all the pairs belonging to a JNL group for each LU, the
restore JNL group remained in the "Stopping" status and did not change to
the "Stop" status on SVP.
Conditions of Occurrence Same as phenomena (occurs in rare cases).
91 ORM Staging ABEND

Phenomena The ORM staging ended abnormally with following SSB reported.
1. SSB=9815 (internal retry time over),
2. SSB=1470 (reserve failure due to logic inconsistency/ double reserve or
invalid reserve error)
In case the failed sectors detected by ORM could not be restored and the
above SSB occurred frequently, the HDD might be blocked.
Conditions of Occurrence This problem might occur when all the conditions are met.
1. RAID5 or RAID6,
2. ORM detects failed sectors on HDD,
3. CHK3 reset and WCHK1 reset occur,
Category ORM
92 Unavailable Pair split-S Operation Selectable Invalidly on

Storage Navigator
Phenomena On the Main tab of Shadow Image or C.O.W. Snapshot tab of Storage
Navigator, in the COPY or COPY (RS-R) status, in which Pair split-S
should be unavailable for the Snapshot pairs, the Pair split-S operation was
selectable.
Conditions of Occurrence Copy-on-Write Snapshot pairs are in the COPY or COPY (RS-R) status.
Changed Part SVP
93 Invalid UR/URZ Pair Status

Phenomena When displaying 16,379 UR/URZ pairs in the COPY status, some of them
were shown in the SMPL status.
Conditions of Occurrence When displaying 15,000 or more UR/URZ pairs in the COPY status.
94 Failed to Obtaining URZ Pair Status from BCM

Phenomena When obtaining the URZ pair information from BCM, invalid SSB was
logged at the primary site.
1. URZ pairs exist,
2. Obtaining the URZ pair information from BCM,
3. Errors (parameter error, etc) occur during the parameter transfer between
DKC.
95 URZ Pair Suspend due to Host I/Os without Time Stamps

Phenomena When mainframe host issues updated I/O during the initial copy of URZ
pairs, the pairs were suspended due to a DKC internal error.
Conditions of Occurrence When the host issues update I/O right after the URZ pairs are created, the
host I/Os do not have time stamps added since invalid information was
reported from the DKC to the host.
96 URZ Pairs Suspend during I/Os Processing

Phenomena When re-synchronizing URZ pairs that were in the Suspend status during
I/Os processing, the pairs might be blocked with SSB=CB92 reported.
1. URZ pairs,
2. Suspend pair status,
3. Pair re-synchronizing during I/Os processing.
97 URZ Pair Suspend in 1:1 Configuration
Phenomena A URZ pair in 1:1 configuration was suspended with SSB=481E reported.
As a result, WCHK1 (MP blockade) might occur.
1. URZ pair,
2. Splitting the pair or removing the pair,
3. The internal pair status changes after receiving write commands and
before update copy starts.
98 MIH and Pair Suspend when URZ Pair in Duplex Status

Phenomena Issuing I/O onto URZ pair in Duplex status a MIH occurred and pair was
suspended with SSB=4811, BBE3 reported. Pair may remain suspended.
1. URZ pair,
2. Retry occurs due to JNL slot busy, etc,
3. Reset (SELRESET) occurs during retry processing.
99 SVP Reboot Displaying Performance Monitor for a Long Time

Phenomena Displaying Performance Monitor for long time, SVP reboot occurred.
Conditions of Occurrence Performance Monitor is in operation for a long time. The handle resource
increases without being released.
Category Performance Monitor
Changed Part SVP
100 UR/URZ Pair Suspend with SSB=EF1C

Phenomena A UR/URZ pair was suspended with SSB=EF1C logged. SSB=EF39,
EF3A, EF3B, etc were also reported.
1. UR/URZ pair status is PAIR or COPY,
2. In case of the PAIR status, update I/Os are in progress,
3. heavy workload,
Category Universal Replicator/Universal Replicator for z/OS
101 Planned PS-OFF Failure after Creating TC Async/TCZ Async
Pairs
Phenomena After creating TC Async/TCZ Async pairs, the planned PS-OFF of RCU
did not end.
SIM=388F (PS-OFF failure) and SSB=80E6 (LCP/MCP blockade waiting)
occurred.
1. TC Async/TCZ Async,
2. Initially creating multiples pairs via the host or Storage Navigator.
(The problem does not occur when adding pairs.)
102 UR/URZ Pairs Suspend when Overloaded

Phenomena When RAID was in the overloaded status, UR/URZ pairs were suspended
without retry processing.
1. RAID is in overloaded status,
2. Reserving/releasing the JNCB slot,
3. When sending stage or de-stage messages, the processing result of
message sending function is buffer overflowed.
103 CTG Setting Failure

Phenomena When reserving CTG or releasing the reservation on the Shadow Image for
z/OS panel, the operation failed with SSB=2212, 23FF reported.
1. Operation to reserve CTG or to release the reservation,
2. CTG# is 0x40 or higher,
3. Specifying three or more CTG numbers for one operation.
104 JNL Group UR/URZ Pairs Suspend

Phenomena A JNL group of UR/URZ pairs were suspended with RCU SSB=EF25
reported.
Conditions of Occurrence In case the configuration does not meet the conditions of UR guideline
significantly.
(When JNL VOL belonging to multiple JNL groups is defined on the parity
group, and the cache overload status continues intermittently, the
processing is delayed due to micro exchange or cache failure. In this case,
the problem occurs easily.)
105 UR/URZ Pairs Suspend when Cache/SM Failure

Phenomena When a cache failure or a SM failure occurred at the RCU site, UR/URZ
pairs might be suspended with SSB=EF13, EF85 reported.
1. UR/URZ pair status is PAIR or COPY,
2. In case of the PAIR status, update I/Os are in progress,
3. A cache failure or a SM failure occurs at the RCU site,
4. Overloaded status (message buffer full).
106 Concurrent Copy ABEND after Micro-Program Upgrade

Phenomena After upgrading the micro-program to Version. 50-03-93-00/00 or higher,
the command was rejected with EC=7D5C reported. As a result, the
concurrent copy ended abnormally.
Conditions of Occurrence The problem occurs when all the conditions are met.
1. A Concurrent Copy job is executed,
2. Completion of SESSION and registration of SESSION take place at the
same time
(When a Concurrent Copy job is performed to multiple small DATASET,
the condition is likely to be met)
Affected Products/Version DKCMAIN: 50-03-93-00/00 and later
Category Concurrent Copy
107 DKC PS-OFF Failure after UR/URZ Pairs Suspend
Phenomena After UR/URZ pairs were suspended due to a DKC internal error, DKC
PS-OFF failed.
1. A DKC internal error occurs during UR/URZ pair initial copy,
2. After #1, a JNL group of UR/URZ pairs are suspended.
3. Rare cases.
108 UR/URZ Pair Suspend after Power Cycle

Phenomena When performing a power cycle during UR/URZ pair initial copy, the pair
was suspended with EC=BBE3 reported.
1. UR/URZ pair initial copy,
2. PS-OFF/ON
109 Invalid Displays on Storage Navigator when DKCMAIN

Timeout
Phenomena Case A. When displaying 16,379 UR/URZ pairs mostly in the COPY
status, some of them were shown in the SMPL status on the UR Pair
Operation panel of Storage Navigator.
Case B. Settings on the VPM panel of Storage Navigator were not
reflected.
Case C. Delete settings of Copy-on-Write Snapshot pairs on the Shadow
Image panel were not reflected.
Case D. When setting reserve volumes or migrating volumes on the
Volume Migration panel of Storage Navigator, the operation failed with an
error message.
Case E. On P.P. license SLPR panel, even though the usable capacity failed
to be obtained, the processing continued as if the operation was successful.
Conditions of Occurrence Case A. Displaying 15,000 or more UR/URZ pairs, which are in the COPY
status, on the UR panel.
Case B. Change the settings on the VPM panel when SM conflicts occur
frequently due to heavy workload,
Case C. Internal logic error.
Case D. In case of SVP version 50-03-21/00 or higher, perform settings on
the Volume Migration panel when DKC is in heavy workload state.
Case E. Open the SLPR panel when the multi-chain interface function is
timeout due to DKCMAIN overloaded state.
Causes and Updates When the DKCMAIN timeout occurs in the above cases, following error
messages will be reported.
Case A: (6505-8001)
Case B: (8505-8002)
Case C: (7005-8000)
Case D: (5205-8001)
Case E: (405-8003)
Category Universal Replicator/ Universal Replicator for z/OS/ Virtual Partition
Manager/ Shadow Image/ Volume Migration
Changed Part SVP
110 TCA/TCZA Pairs Suspend when CHT Failure

Phenomena When a RCU CHT failure occurred, TCA/TCZA CTG pairs were
suspended with SSB=CC62 reported.
1. TCA/TCZA pairs and UR/URZ pairs are in update copy,
2. CHK3/CHK1A/CHK1B/WCHK1 occurs at TCA/TCZA RCU and CHP
PCB of UR/URZ MCU-RCU.
Category True Copy Async/ True Copy for z/OS Async/ Universal Replicator/
Universal Replicator for z/OS
111 Shadow Image Pair Suspend when Quick Split

Phenomena When executing Split on the Shadow Image pairs, the pairs were
suspended with SSB=211F, 2115 reported.
1. Shadow Image pairs with update I/Os on P-VOL,
2. Execute Quick Resync on the Shadow Image pairs in splitting progress,
3. After #2, and before the update copy, execute Split on the Shadow
Image pairs in the PAIR status.
112 Emergency de-stage failed due to P/S ON after power off

Phenomena Emergency de-stage fails due to a power cycle. (The following SSB occur)
RC=327A (Occurred once)
RC=9852/9815/9f02 (Occurred many times)
Conditions of Occurrence This problem may occur when P/S ON is performed after power off.
Category PS-ON/OFF
113 UR/URZ Pairs Suspend when First Pair Fails to be Established

Phenomena When establishing UR/URZ pairs, SSB=8F3D occurred and the UR/URZ
pairs were suspended.
1. When establishing multiple UR/URZ pairs, the first pair cannot be
created due to inconsistent emulation type between M-VOL and R-VOL.
2. Other pairs are created normally.
114 SF monitoring exceeded 100%

Phenomena Side file amount displayed in SVP monitor or by BCM command is 100%
or larger.
1. Flash Access settings.
2. No access to Flash Access area.
3. TCZ-Async RCU
Category True Copy for z/OS Async
115 HUR pair resync failed (Failure suspend (SSB: EF41), Copy
stop)
Phenomena When re-synchronizing an HUR pair,
(1) The pair may suspend due to a failure (SSB=EF41).
(2) The copy operation stops (progress stops). The pair delete command
failed (stops with suspending).
1. HUR pair is in the PAIR or COPY state
2. An update I/O is in progress in the case of the PAIR state
3. Overloaded (Too many pairs, journal groups)
4. Resynchronize the pair after suspending it.
116 Invalid DSB=0x80 reported
Phenomena When PPRC ESTPAIR is issued with MSGREQ from TSO, it may be
hanged up.
- PPRC ESTPAIR is executed with MSGREQ from TSO (TC/TCA/SI)
- Use CU#1 or larger
Category Mainframe
117 Command rejected after CHK2

Phenomena After detecting CHK2 due to a hardware failure in the host path, the
command was rejected.
1. TCZ-Sync pair is in the Duplex state
2. Write operation in which the Sync performance enhancing logic runs
(Write operation within one track by UPWR command or FMTWR
command that does not include Record#1 or last record)
3. HALT I/O occurs during write data transfer (2) in the non Locate
domain or Locate Last domain.
118 Double restore jobs due to system overload

Phenomena During HUR operation, a restore job is started doubly in the environment
where DKA TOV occurs due to system overload.
1. HUR pair exists and Initial/update copy is in progress
2. Due to heavy workload on RCU, the staging waiting TOV occurs for 25
seconds or longer.
119 WCHK1 occurred after resetting logical inconsistency

Phenomena WCHK1 occurred after a logical inconsistency reset.
Conditions of Occurrence Problem occurs when I/O is processed after a logical inconsistency is reset.
Category OPEN
120 ABEND DUMP SIM after Cache Failure

Phenomena Invalid address was set in post processing of data transfer when a cache
failure occurred, ABEND DUMP SIM of EC=B6EE occurred in CHT.
- A read operation with a large transfer size (96K or larger) is executed
- CACHE/CM is blocked
- CHK2 occurs
Category OPEN
121 SSB=1644 occurred in CHK2 post processing of WDCP SM

nonvolatile process
Phenomena In the M series subsystem, PS/OFF was performed because one side of
SM/CACHE/CSW was blocked. During a WDCP SM nonvolatile
processing, SSB=1644 occurred.
- Async JOB
- Failure reset
- Uninstalled LDEV# in the JOB management area
Category ESCON/FICON
122 CHK2 threshold exceeded due to cache failure

Phenomena When a cache failure occurred, the address of the blocked side of cache
was used and the transfer was started repeatedly. As a result, the CHK2
threshold was exceeded, and the MP was blocked.
Conditions of Occurrence This problem may occur when CACHE/CM is blocked.
Category OPEN
123 Pair resync failed after LU specified pair suspend

Phenomena When a UR/URZ pair resync is performed after selecting all pairs in the
JNL group and suspending a pair by specifying the LU, EC=ef41 will be
output, and the pair resync will fail.
Conditions of Occurrence Problem occurs in rare cases when pair resync is performed after selecting
all pairs in the JNL group and suspending a pair by specifying the LU.
124 FCv2 Establishment of relationship failed

Phenomena When you try to establish many relationships one after another, a timeout
occurs in the host, and the relationships cannot be established.
Conditions of Occurrence Problem occurs when many relationships are established in succession.
125 PDEV type does not match due to invalid setting of spare HDD
Phenomena HDD was removed, and then PS ON was performed. After that, the
removed spare drive (R20-0F:DKS2D-K146) was replaced, but it failed
due to PDEV type inconsistency (SSB=a7e1). The configuration
information was checked; it said the model was DKR2E-J146.
- PS ON
- One/more data drives and one/more spare drives blocked due to a failure.
- The relationship between the blocked data drive and the spare drive is the
same HDD or HDD that can be a compatible PDEV.
Category HDD
126 Path Check Timeout when OS IPL

Phenomena Path Check was timeout when OS IPL was in progress.
1. FICON connection,
2. OS OPL,
3. Issuing the sense command right after the check report of reset notice,
4. Path group is not defined.
Category FICON
127 Different Performance between Ports

Phenomena When performing I/O on the HDD (128 parity groups) loaded in DKU L1
and L2, some CHP with significantly different usage rates of MPs were
displayed on the Performance Monitor panel of SVP.
Conditions of Occurrence In case DKA-Option 3 is installed.
Category OPEN
Changed Part CHT
128 Verify failed when RAID1 (4D+4D)

Phenomena When Verify is executed from the SVP in RAID1 (4D+4D), SSB=18bc is
output when the progress reaches 75%, and the Verify is terminated
abnormally. (You can start Verify either by selecting a parity group and
selecting the Verify button in the Logical device panel in the SVP
maintenance panel (Specify a parity group) or by selecting an LDEV in the
parity group and selecting the Verify button (Specify 1 LDEV).)
Conditions of Occurrence This problem occurs when the conditions 1,2,3,4 or 1, 2, 5 are met.
1. RAID1(4D+4D) (Concatenate two RAID1)
2. OPEN-V
3. Start Verify by specifying a parity group from the SVP
4. A blocked LDEV is included in the parity group, which is the target of
Verify
5. Start Verify by specifying 1LDEV from the SVP
Category SVP
129 DRR blocked due to a cache error when RAID5/6

Phenomena In the case of RAID5 or RAID6, when one side of the cache was blocked
due to a cache failure, the DRR was blocked.
1. RAID5 or RAID6
2. Only one side of the cache is available due to a cache failure
3. Timing
Category Cache
130 WCHK1 occurred when subsystem was restarted after planned

power off
Phenomena When an irregular power cycle operation (RCU P/S OFF-->MCU P/S
OFF-->RCU P/S ON-->MCU PS/ON) is performed, a WCHK1 may occur
at MCU.
1. HUR is used
2. Irregular power cycle operation is performed
(RCU P/S OFF-->MCU P/S OFF-->RCU P/S ON-->MCU P/S ON)
(The recommended procedure: MCU P/S OFF-->RCU P/S OFF-->RCU
P/S ON-->MCU P/S ON)
131 Invalid read data in the case of FICON Read truncation

Phenomena In a mainframe host FICON connection, the read data became invalid, and
ICC or JOB ABEND occurred.
Conditions of Occurrence This problem might occur when all the conditions are met.
1. Mainframe FICON connection
2. One command that reads multiple records
(MRDCKD/RDCKD/RDTRK/RDTRKD)
3. Truncation in the command processing in (2) (CCWCNT < Actual
record length>)
Category FICON Connection
Changed Part DKCMAIN/HTP
132 Initial TC Async Pair-Creating Failure with MCU SSB=4A33

Phenomena When creating True Copy Async pairs during the status changing progress
of True Copy/ Universal Replicator/ Shadow Image pairs and I/Os
processing, [EX_CMDRJE] occurred and the operation failed with MCU
SSB=4A33 reported.
1. True Copy Async pairs,
2. Performing initial pair-creating with CTG specified via RAID Manager,
3. Synchronizing waiting is detected from MCU.
133 Not copying old data from FCv2 S-VOL to T-VOL when
updating S-VOL
Phenomena An access error occurs on VTOC on T-VOL.
Expected data is not copied from S-VOL to T-VOL.
A. Establishing Flash Copy V2 relationship
B. Updating S-VOL by non-ECKD CCW or a CCW that chains Read and
Write commands on one track (e.g. DX/LOC/RDD/LOC/WRD).
Category Flash Copy V2
134 True Copy Async pair suspended

Phenomena When the True Copy Async S-VOL was also a Shadow Image pair volume,
the True Copy Async pair was suspended by the operation, and the Shadow
Image pair status was changed to SPLIT. After that, when the True Copy
Async pair was resynchronized, SSB#1470,cca9,1479,cce3,cc91,cc94
occurred, and the True Copy Async pair was suspended.
1. M/F
2. A True Copy Async (z/OS) S-VOL is also a Shadow Image (z/OS) or
FlashCopyVersion1 pair volume.
3. The True Copy Async (z/OS) copy operation and the Shadow Image
(z/OS) pair status transition to Split take place concurrently.
* In the case of Quick Split, since the split processing is performed in the
background, the condition is until the pair is completely Split.
Category True Copy Async z/OS
135 Several DKP Blocked with CHK3

Phenomena During SM installation of Cluster-1, the installation was failed by CUDG
detecting a hardware failure. After that, when SM was recovered by SM
dummy replacement, CHK3 frequent occurred and DKP blockaded (SSB
EC=32fe). As result of this, LDEV was blocked caused by multiple DKP
blockade.
Conditions of Occurrence This problem may occur when the following conditions A and B are all
satisfied or the following conditions A and C are all satisfied.
A. There is a parity group of RAID6.
B. When the SM installation or de-installation along with (1) or (2) below
is failed by a SM hardware failure. As result of this, SM capacity between
CL1 and CL2 is different.
(1) 　Configuration of the CM capacity, or the number of LDEV, or the
number of HDD, or the number of the external VOL is changed.
(ii) Configuration is changed from the SM Standard configuration to the
SM High Performance configuration.
C. When the configuration is changed from the SM High Performance
configuration to the SM Standard configuration. (In this case, this problem
may occur without the SM hardware failure.)
Category Cache
136 Server Down due to I/O Timeout

Phenomena The server went down due to I/O timeout (CHP hanged up in the post
process when the reserve command ended abnormally).
1. A server （MSCS/AIX/SUN (with Cluster soft) /True64/VMWare)
issues the reserve command,
2. A reset is received or a timeout occurs due to no response to the reserve
command,
3. A LUSE volume of LDEV0x2000 or more.
Category OPEN
137 Parity Group addition failure and abnormal configuration

information
Phenomena Addition of Parity Group failed. After that, Maintenance window on SVP
wrongly displayed original Parity Group 1-1 as 6-1 and RAID level 5 as 1,
which were also inconsistent with the original configuration information.
Conditions of Occurrence This problem occurs when all of the following are met.
1. Sum of the number of existing internal PDEV, external volumes, virtual
volumes, and the number of adding PDEV is more than 2560.
[Internal PDEV] + [External volume] + [Virtual volume(V-VOL)*] +
[Adding PDEV] > 2560
2. Additional installation of PDEV (Parity Group addition or spare drive
addition)
3. After the above additional installation of PDEV fails, the additional
installation is performed again.
(*)： Volume used by Copy-on-Write Snapshot
Category PDEV
Changed Part SVP
138 When LDEV is added to POOL, WCHK1 [SSB EC=1644]

occurs
Phenomena When an LDEV was added to a POOL, WCHK1 [SSB EC=1644]
occurred.
Conditions of Occurrence When all of the following conditions are met, this problem occurs.
A. Subsystem: RAID500 (USP model)
B. Micro-program version: DKCMAIN Ver.50-04-06-00/00 and later
C. Copy-on-Write Snapshot is used
D. VFS SYS Area Extension3 configuration is defined.
E. When an LDEV is added to POOL or a Copy-on-Write Snapshot pair is
created, the VFS SYS area is exhausted.
Affected Products/Version DKCMAIN: 50-04-06-00/00 and later

Category Copy-on-Write Snapshot

Usp 50-05-06-00-00

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Usp 50-05-06-00-00

Uploaded by

Copyright:

Available Formats

USP

MICROCODE VERSION 50-05-06-00/00

Newly supported features and functions for Version 50-05-06-00/00

1-1 Support for Double Concatenated Configuration of RAID5 (7D+1P)

3. USP & NSC Model

1-3 Improved Sequential Write Performance at the time of Correction

1-4 Support for SFP Revision Information

1-5 Improved GUI for SM Addition

2. Support for UR/URZ Multi-Target Configuration

3. Same functions as True Copy/True Copy for z/OS

4. Support for Online Addition of UR/URZ JNL Volumes

5. Expanded Number of UR/URZ JNL Groups

1-7 Support for LDEV Range Specifying Function

LDEV Range | Setting Range of LDEV ID

1-9 Hid HUR Journal Volume on Feature Panels

1-10 Improved Reliability in case of HDD Failure

1-11 SVP Support for WINXP SP2

1-12 Support for PCI Feature

1-13 Improvement for Retry Number of Volume Migration Copy

1-14 FAL (HP-UX Reserve Retry)

1-15 NSC Enhancements

2-1 Support for 1 M Relations of Flash Copy Version 2

2-2 Performance Improvement for Shadow Image for z/OS

Command 63/47/06: performance improved about 7%.

2-3 Support for PPRC Link Information

2-4 Function Switch 21

Function Switch 21 = ON : copy pace = 3Trk

2-5 Support for N: 1 Connection of True Copy for z/OS Async

2-7 Support for Mainframe Restart Switch

2-8 Emulation Type Expansion for URZ (JNL/Data Volume)

2-9 Support for Hyper Swap on GDPS 3.2 and PPRC V4

3-3 DB Validator Enhancement

3-4 Performance Improvement for Open Connection

3-5 Support for Command Device of External Volume

1 MPs Blockade during SVP Rebooting

2 Path disconnection delayed in TCA/TCZA when no I/O is issued

3 PDEV correction access display is added to LDEV panel

5 SSB=413e occurs during Cache/SM maintenance operation

6 Power failure in DKU in NSC model

8 Cache Maintenance Improvement

9 Display External Volume in spreadsheet

11 Dirty data is not de-staged to External VOL and remains in

12 HTP failure SSB generated at the time of FICON online micro

13 I/O not processed due to emergency de-stage

14 Input allowed falsely at the time of Refer Configuration

15 SM path blocked due to PS ON

16 Failed to Make LUSE Volume with Maximum LDEV Number

17 Problem in checking max LUSE size

18 EC=CC14 after power cycle in Async MCU

19 Invalid Display for SIM Details

20 Confirmation message at time of SM installation/un-installation

21 UR/URZ Pair Failure Suspend during Initial Copy

22 Invalid SIM Report

23 [UVM] Message indicating insufficient licensed capacity is

24 Communication error (STW0117W)

25 MCU SSB=d1ea, d2c9, 1470 when Replacing SM or CM

26 SVP reboots repeatedly

27 Same SIM occur at the same time

28 SSB=13c6, b845 in ENAS

29 After Reverse _ resync during copy operation, Pending remains

30 Error is not output in Audit Log Basic information

31 LDEV Emulation 3390-3B Misjudged as Mainframe VOL

B. The following emulation types are installed.