Documente Academic
Documente Profesional
Documente Cultură
2. Mainframe System
NONE
3. OPEN System
HDS Confidential 1 of 8
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.
Severity (High, Medium, Low) High
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
HDS Confidential 2 of 8
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
- 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.
Severity (High, Medium, Low) High
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.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-02-80-00/00
Category Open or Mainframe
Changed Part DKCMAIN
HDS Confidential 3 of 8
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. SSB=7321, 7330, 7328, 7343, 7353, 7373, 7383, 73B0, 73C0,
7393, 73A3, 7230, 7428 or 749F was output and I/O stall might occur.
Severity (High, Medium, Low) High
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Mainframe host connection
(2) SETCACHE command executed from IDCAMS or the TDMF tool.
(3) An MP failure occurs. (CHK1B, CHK3, WCHK1)
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-02-80-00/00
Category Mainframe
Changed Part DKCMAIN
HDS Confidential 4 of 8
8 Failure of resync operation for UR for Mainframe pair
Phenomena A resync operation for a UR for Mainframe pair that used 3390-A failed
with SSB=8F78 output. At the time, SSB=D996 was output on RCU side.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem occurs when all the following conditions are met.
(1) Universal Replicator for Mainframe
(2) Emulation type is 3390-A.
(3) Volumes whose volume size falls into the following ranges are used.
7792Cyl to 8183Cyl, 15583Cyl to 16366Cyl, 23374Cyl to 24550Cyl,
32278Cyl to 32733Cyl, 40069Cyl to 40917Cyl, 47860Cyl to 49100Cyl,
56764Cyl to 57284Cyl, 64555Cyl to 65467Cyl, 72346Cyl to 73651Cyl,
81250Cyl to 81834Cyl, 89041Cyl to 90018Cyl, 96832Cyl to 98201Cyl,
105736Cyl to 106385Cyl, 113527Cyl to 114568Cyl, 121318Cyl to
122752Cyl, 130222Cyl to 130935Cyl, 138013Cyl to 139118Cyl,
145804Cyl to 147302Cyl, 153595Cyl to 155485Cyl, 162499Cyl to
163669Cyl, 170290Cyl to 171852Cyl, 178081Cyl to 180036Cyl,
186985Cyl to 188219Cyl, 194776Cyl to 196403Cyl, 202567Cyl to
204586Cyl, 211471Cyl to 212770Cyl, 219262Cyl to 220953Cyl,
227053Cyl to 229137Cyl, 234844Cyl to 237320Cyl, 243748Cyl to
245504Cyl, 251539Cyl to 253687Cyl, 259330Cyl to 261870Cyl
Affected Products/Version DKCMAIN: 70-02-54-00/00 and higher
Fixed Product/Version DKCMAIN: 70-02-80-00/00
Category Universal Replicator for Mainframe
Changed Part DKCMAIN
HDS Confidential 5 of 8
11 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.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-02-80-00/00
Category Mainframe
Changed Part DKCMAIN
12 Operation failures
Phenomena Any of the following phenomena might occur.
(1) PS OFF was disabled and SIM=388F00 was output.
(2) MPB replacement failed and SVP message ONL2788E was output.
(3) MPB removal failed and SVP message ONL2788E was output.
(4) Parity group migration in a CLPR failed.
(5) Cache maintenance (replacement, installation, removal) failed and
SVP message ONL2788E was output.
(6) An I/O to an LDEV that was a target of following operations turned
time-out by an operation accompanied with LDEV ownership migration
(such as MPB maintenance/ failure, LUSE connection/release, SI pair
creation/release, Snapshot pair creation/deletion, JNL VOL
addition/deletion, ownership migration by CCI/Storage Navigator).
Severity (High, Medium, Low) Low
Conditions of Occurrence Problem may occur when any of the following operations is performed.
(1) PS OFF
(2) MPB replacement
(3) MPB removal
(4) Parity group migration in CLPR
(5) Cache maintenance (replacement, installation, removal)
(6) An operation with ownership migration such as MPB
maintenance/failure, LUSE connection/release, SI pair creation/release,
Snapshot pair creation/deletion, JNL VOL addition/deletion, and
ownership migration by CCI/Storage Navigator.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-02-80-00/00
Category Open or Mainframe
Changed Part DKCMAIN
HDS Confidential 6 of 8
14 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 above phenomena 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.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when an LDEV defined on an SATA-E HDD is
used.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 70-02-80-00/00
Category Open or Mainframe
Changed Part DKCMAIN
HDS Confidential 7 of 8
17 No action code displayed on SVP
Phenomena SIM=307600 was output and the action code was not displayed on SVP.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when SIM=307600 is output. (When FM SUM value
error is detected by periodical diagnosis due to a FM failure in MPB.)
Affected Products/Version SVP: All
Fixed Product/Version SVP: 70-02-77/00
Category Open or Mainframe
Changed Part SVP
HDS Confidential 8 of 8