VSP 70-03-08-00-Mo93

VSP
MICROCODE VERSION 70-03-08-00/00-MO93

RELEASED 03/24/2012
New supported features and functions for Version 70-03-08-00/00-MO93

1. Mainframe & OPEN System
1-1 Support for external connection path information sorting

Description A function to sort and return the external connection path information according to the order
of external connection path priority when external volume information is obtained from
RMI-API is supported.
Changed Part SVP
2. Mainframe System
NONE
3. OPEN System
NONE
The change of contents for Version 70-03-08-00/00-MO93

1 Data inconsistency in data migration from EMC storage
Phenomena After data migration is performed from EMC to RAID700 using FICON
Data Migration, a host job may end abnormally on the target volume due
to data inconsistency. The following phenomena may occur.
- When DB2 is executed, the error message DSNB224I or DSNB226I is
generated. (No Rec Found or Invalid track Format)
- When a host I/O is received, EQC (Format’x8’, Message’x9’, Byte18-
19:x6388) occurs, and the host job ends abnormally.
(Note) Even if the above phenomena do not occur, the volume for which
data migration is performed using FICON Data Migration may already
have a data inconsistency.
Severity (High, Medium, Low) High
Conditions of Occurrence The failure may occur when all the following conditions are met.
A. RAID700 Ver.70-01-62-00/00 and later
B. Data is migrated using FICON Data Migration
C. The source external storage is EMC
D. A link failure occurs while mapping a registered path during data
migration
Note: The link failure in D. is not a link down, but is a bit error caused by
a signal problem.
Affected Products/Version DKCMAIN: 70-01-62-00/00 and higher
HTP: 70-01-63 and higher
Fixed Product/Version DKCMAIN: 70-03-08-00/00
HTP: 70-03-04
Category Mainframe
Changed Part DKCMAIN, HTP
HDS Confidential 1 of 7
2 Data inconsistency Copy-on-Write Snapshot P-VOL or S-VOL
Phenomena One of the following phenomena may occur.
a) When the pairsplit operation is performed for a Copy-on-Write
Snapshot (hereinafter referred to as “CoW”) pair and data is read from S-
VOL, the updated P-VOL data after the pairsplit operation is read instead
of the P-VOL data before the pairsplit operation. As a result, a file system
problem occurs, or applications detect errors.
b) When the pairresync –restore operation is performed for a CoW pair,
and P-VOL data is read while the CoW pair is in the COPY(RS-R) status
or in the PAIR status, the P-VOL data before the pairresync –restore
operation is read instead of the S-VOL data before the pairresync –restore
operation. As a result, a file system problem occurs, or applications detect
errors.
Conditions of Occurrence Phenomenon a) may occur when all the following conditions A, B, and C
are met.
A. RAID700: All the current versions
B. System Option 737 is set to OFF
C. The following shows the conditions for each CoW pair configuration.
C1. Multiple CoW pairs are defined for one P-VOL
C2. One or more CoW pairs described above are in the PSUS status
C3. During P-VOL data update (*1), the pairsplit operation is
performed for the above-described CoW pair in the PAIR status
*1) Data update that occurs in following four environments C3-1 to C3-4
C3-1. Configuration that contains only CoW pairs Write I/O is issued to
P-VOL from the host
C3-2. Configuration where a CoW pair is combined with a TrueCopy pair
P-VOL is TrueCopy S-VOL. While the TrueCopy pair is in the COPY or
PAIR status, initial copy or update copy of TrueCopy pair is performed
C3-3. Configuration where a CoW pair is combined with a Universal
Replicator pair P-VOL is Universal Replicator S-VOL. While the
Universal Replicator pair is in the COPY or PAIR status, initial copy or
update copy of the Universal Replicator pair is performed
C3-4. Configuration where a CoW pair is combined with a ShadowImage
pair P-VOL is ShadowImage S-VOL. While the ShadowImage pair is in
the COPY(RS), PAIR, PSUS(SP), or COPY(SP) status, a copy operation
is performed for the ShadowImage pair.
C4. The CoW pair for which the pairsplit operation is performed does not
have the CTG configuration
Phenomena b) may occur with the following conditions A, B, H, I met.

A. RAID700: All the current versions
B. System Option 737 is set to OFF
H. While a read or write I/O is issued to CoW P-VOL, the pairresync –
restore operation is performed.
I. The above-described pairresync –restore operation is the second or later
pairresync –restore operation for the same P-VOL after the pair is created
Affected Products/Version DKCMAIN: All
Category Copy-on-Write Snapshot, TrueCopy, Universal Replicator, ShadowImage
Changed Part DKCMAIN
3 HDD may become blocked when SATA-E mode is used
Phenomena When the SATA-E mode is used for SATA HDD, CHK2 may occur due
to a write sequence error. Depending on the number of times the error
occurs a day, the following phenomena occur, and LDEV and/or MP are
blocked and data loss occurs in the worst case.
- It occurs four times in the same drive port -> SIM RC=df6xyy or df7xyy
is reported.
- It occurs eight times in the same drive port -> The drive port is blocked.
SIM RC=df8xyy or df9xyy is reported.
- Both ports of the same HDD are blocked -> HDD is blocked.
SIM RC=ef0xyy is reported.
- HDD is blocked by exceeding redundancy in same ECC -> LDEVs in
the same ECC group are blocked. SIM RC=dfaxyy or dfbxyy is reported.
- It occurs 128 times in the same logical DMA -> Logical DMA is
blocked.SIM RC=cf6xyy is reported.
- Multiple logical DMAs in the same DMA are blocked -> DMA is
blocked. SIM RC=cf83xx is reported.
- All logical DMAs in the same DKA PCB are blocked -> MP is blocked.
SIM RC=3073xx is reported.
In addition, if this error occurs when there is no redundancy in the same

ECC or when correction read is performed for recovery of a write
sequence error , PIN slot(s) occur(s) and SIM RC=ff4xyy is reported.
Conditions of Occurrence The WSEQ# information may become invalid when all the following
conditions A to C are met.
A. RAID700 micro-program version 70-01-01-00/00 and later
B. The SATA-E mode is used
C. SSB EC=13dc (Write Pending 65% or more) is reported
(Note): In reality, the phenomenon may occur when “Write Pending of
the CLPR to which the HDD that uses the SATA-E mode belongs is 68%
or more”. But in the case of monitoring data, a brief increase in Write
Pending may not be indicated in the data, so check if SSB is output to
determine whether the condition is met. When the WSEQ# information
becomes invalid, if the SATA HDD data is read using the WSEQ#
information, a write sequence error occurs.
Category Open or Mainframe
4 Volume deletion failure with SN message 3205-6535 output

Phenomena When a VOL without LUN path definition was deleted, Storage
Navigator message 3205-6535 was output and the operation was disabled.
Conditions of Occurrence The problem occurs when an MP reset occurs during LUN path deletion.
5 SCP remaining with SSB output and possible I/O stall
Phenomena When an MP failure (CHK1B, CHK3, or WCHK1) occurred during
SETCACHE command processing from IBM utility (IDCAMS) or
TDMF (Transparent Data Migration Facility) tool processing, SCP
remained and SSB=7321, 7330, 7328, 7343, 7353, 7373, 7383, 73B0,
73C0, 7393, 73A3, 7230, 7428 or 749F was output. In this case, I/O stall
might occur.
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Mainframe host connection
(2) SETCACHE command is executed from IDCAMS or the TDMF tool
is used.
(3) An MP failure occurs. (CHK1B, CHK3, WCHK1)
Category Mainframe
6 CHK3 with SSBs output during Mainframe I/O processing

Phenomena During Mainframe I/O processing, CHK3 occurred and SSB=35A0 and
160F were output. (In rare cases, WCHK1 occurred and SIM=3073xx
was output.)
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur during Mainframe I/O processing.
Category Mainframe
7 SSB=3289/A443 output and blockage of HDD port/HDD/ECC

Phenomena The following phenomena might occur:
- SSB=3289 and A443 were output due to CHK2.
- If the above phenomenon frequently occurred, HDD ports might be
blocked.
- If both of HDD ports were blocked, the HDD was blocked.
- If multiple HDDs within an ECC were blocked, the ECC was blocked.
Conditions of Occurrence The problem may occur when an LDEV defined on an SATA-E HDD is
used.
8 Unable to select 40 or higher CU#, or operation failure if 40 or
higher is selected
Phenomena During LDEV creation from Storage Navigator, the following phenomena
occurred.
Phenomenon 1:
40 and higher CU numbers could not be selected.
Phenomenon 2:
If 40 or a higher CU number was selected, Storage Navigator message
3305-001074 was output and the operation failed.
Phenomenon 1:
(1) SM is installed with "64KLDEV/SI/VM Extension1/
FCv2/FCSE/DP/CoW/TPF" of SM function checked.
(2) An LDEV is installed by VLL function of Storage Navigator.
Phenomenon 2:
(1) SM is removed with "64KLDEV/SI/VM Extension1/
FCv2/FCSE/DP/CoW/TPF" of SM function unchecked.
(2) An LDEV of CU number 40 or higher is installed by VLL function of
Storage Navigator.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-03-06/00
Category Storage Navigator
Changed Part SVP
9 Unable to receive failure logs due to deadlock

Phenomena Due to a deadlock in a background task during SVP online micro-
program exchange, a pop-up window of "Wait.. Ending Background
Task" remained displayed and no progress was made, which led to failure
information receiving module being unable to receive failure logs such as
SIM.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur in rare cases when a deadlock occurs between
failure information receiving module and SIM display window due to a
conflict between message transfer processing to SIM display window
executed every 10 seconds by the failure information receiving module
and logging off from SVP.
Changed Part SVP
10 Wrong Object ID returned by GET (sysObjectID
1.3.6.2.1.1.2.0) of standard MIB
Phenomena A value returned by GET (sysObjectID 1.3.6.2.1.1.2.0) of standard MIB
(Management Information Base) in SNMP was not the Hitachi Object ID
(1.3.6.1.4.1.116.3.11.4.1.1) but Microsoft Object ID
(1.3.6.1.4.1.311.1.3.1.1)
Conditions of Occurrence The problem occurs when standard MIB is obtained.
Changed Part SVP
11 MP blockage with SSB=1644 output

Phenomena With external path blocked, an MP was blocked with SSB=1644 output.
Conditions of Occurrence Unknown
Category Open
12 Unavailable "Remove JNL from EXCTG (Force)" operation

Phenomena "Remove JNL from EXCTG (Force)" could not be selected from a menu
displayed by right-clicking a JNL registered to EXCTG on Journal
Operation window of Universal Replicator for Mainframe.
(1) A UR for Mainframe pair is created from CCI.
(2) "0" is specified for CTG number at the pair creation.
(3) A menu is displayed by right-clicking a JNL.
Affected Products/Version SVP: 70-03-01/00 and higher
Category Universal Replicator for Mainframe
Changed Part SVP
13 Host command time-out with SSB=B237 output

Phenomena Host command time-out occurred and SSB=B237 was output.
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Initiator Port and Target Port coexist in the same CHA.
(2) A VOL, which is connected to a host and used for a TC pair, is paired
with a VOL connected to the Initiator port.
Affected Products/Version DKCMAIN: 70-03-01-00/00 and higher
Category Open
14 ABEND of LDEV format due to CHK3/WCHK1
Phenomena During Mainframe LDEV format processing, CHK3 (SSB=160F) or
WCHK1 (SSB=32FE) occurred and the format could not be completed.
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) Mainframe environment
(2) Multiple Mainframe LDEVs belong to the same MPB.
(3) A host I/O is being processed to the above LDEVs (as stated in (2)).
(4) LDEV Format is performed at the above LDEVs (as stated in (2)).
(5) A failure reset (CHK3, CHK1B, CHK4 or hang-up reset) occurs, or
WCHK1 MP blockage(s) occur at some MPs (not all the MPs) in the
above MPB (as stated in (2)).
Category Mainframe
15 Incorrect capacity of CVS volume

Phenomena During RAID group installation, if a CVS VOL was created with Block
and Division free space by number specified, a VOL in unexpected size
was created.
(1) A CVS VOL is created with Block and Division free space by number
specified at an operation of Define Configuration & Install, RAID group
installation, or Make Volume from SVP.
(2) The capacity of volume created by the above operation is "free
space/specified division number > 1.999TB (4294967295 blocks)".

Changed Part SVP

VSP 70-03-08-00-Mo93

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

VSP 70-03-08-00-Mo93

Uploaded by

Copyright:

Available Formats

VSP

MICROCODE VERSION 70-03-08-00/00-MO93

New supported features and functions for Version 70-03-08-00/00-MO93

1-1 Support for external connection path information sorting

The change of contents for Version 70-03-08-00/00-MO93

Phenomena b) may occur with the following conditions A, B, H, I met.

In addition, if this error occurs when there is no redundancy in the same

4 Volume deletion failure with SN message 3205-6535 output

6 CHK3 with SSBs output during Mainframe I/O processing

7 SSB=3289/A443 output and blockage of HDD port/HDD/ECC

9 Unable to receive failure logs due to deadlock

11 MP blockage with SSB=1644 output

12 Unavailable "Remove JNL from EXCTG (Force)" operation

13 Host command time-out with SSB=B237 output

15 Incorrect capacity of CVS volume

Affected Products/Version SVP: All

You might also like