GDDR: Uppgradering till z/OS 2.5 gör att abends och GDDR-kontrollsystem körs i degraderat läge
Summary: Uppgradering till z/OS 2.5 orsakar avvikelser i GDDR (Geographically Dispersed Disaster Restart) och GDDR Control SYSTEMS (C-SYS) körs i degraderat läge.
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
Programvaran för mainframes uppdateras till z/OS 2.5-programvarunivå med underhållstolerans. z/OS 2.5 används för en ny IBM z16-processor.
GDDR GDDRMAIN startade med flera ABENDs efter att z/OS-underhållet tillämpades:
- HBM rapporterar nedanstående fel vid GDDRMAIN-start, GDDR-värden är i degraderat läge:
ABEND S0E0-29
- GDDRRPT rapporterar nedanstående fel vid GDDRMAIN-avstängning:
ABEND S0E0-28
Följande felmeddelande visas i utdata från GDDR Event Monitor (EVM) och Heartbeat Monitor (HBM):
GDDUG86E No matching GDDR systems found
Om ABEND S0E0-28 inträffar vid GDDRMAIN-avstängning, då en Abend S067-04 kan inträffa om GDDRMAIN tas upp igen.
Cause
En
Dessutom har en
ABEND S0E0-29 kan inträffa vid GDDRMAIN-start i HBM-underuppgiften vid modul GDDREVMI, offset 0005AF74.
PSW 183158F0 0010D507 3000F154Detta gör att HBM-underaktiviteten avslutas och lämnar GDDRMAIN utan funktioner för pulsslagsövervakning. GDDR-värden körs i degraderat läge. GDDREVMI uppdateras för att rensa REGISTER AR15 innan registret används för att undvika en
ABEND S0E0-29. – Herr talman,
Dessutom har en
ABEND S0E0-28 kan förekomma i GDDRRPT vid GDDRMAIN-avstängning vid GDDRMAIN, offset 0006EAB2.
PSW D24FD37A 1000D207 D37D5004GDDRRPT uppdateras för att rensa REGISTER AR1 för att undvika en
ABEND S0E0-28. GDDRMAIN uppdateras för att verifiera att datautrymmet 2 Access List Entry Token (ALET) är giltigt. Den här åtgärden utförs innan du får åtkomst till datautrymmet för en annan GDDR-instans. Den här åtgärden hjälper till att undvika en Abend S067-04 i GDDRMAIN-starten på grund av att en annan GDDR-instans inte stängs av rent.Resolution
Alternativ lösning:
- Ingen för ABEND S0E0-29 men GDDR-värdarna fortsätter att köras i degraderat läge.
- En initial programbelastning (IPL) av den logiska partitionen (LPAR) krävs för att rensa minnet om en
Abend S067-04Uppstår.
Permanent lösning:
- För GDDR 6.0 kan du ladda ner GD60004 och GD60005 från Dells support för GDDR 6.0.
- För GDDR 6.1 är problemet löst i basprodukten. Den kan laddas ner från Dells support.
Additional Information
Beskrivning av Program Temporary Fix (PTF) –
++PTF(GD60004) REWORK(2022315) .
++VER(Z038) FMID(GDDR600)
/*
*-------------------------------------------------------------
* PROBLEM DESCRIPTION(S):
* ------------------------------------------------------------
*
* PROBLEM FIXED: GDDR-3459
* USERS AFFECTED: GDDR users
* PROBLEM DESCRIPTION: Warning message GDDUG24W results in
* RC 8 on pre-script and post-script
* configuration displays
*
* DESCRIPTION DETAIL:
*
* During GDDR scripts, warning message GDDUG24W could result
* in an RC 8 on the pre-script and post-script configuration
* displays, for example:
*
* GDDUG24W 2 external RDF groups indicate SRDF/A active
* GDDR639I GDDR Completed pre-script configuration display
* with rc 8
*
* This is simply a messaging issue, as a non-zero RC on the
* configuration displays does not affect the outcome of the
* script.
*
* PROBLEM RESOLUTION:
*
* Warning message GDDUG24W will now result in an RC 4 on the
* configuration displays, as expected.
*
* MODULES: GDDRMCMD
*
* ------------------------------------------------------------
*
* PROBLEM FIXED: GDDR-3460 GDDR-3472
* USERS AFFECTED: GDDR users
* PROBLEM DESCRIPTION: ABENDS067-04 upon GDDRMAIN startup due
* to another GDDR instance not shutting
* down cleanly
*
* DESCRIPTION DETAIL:
*
* An S067-04 abend could occur upon GDDRMAIN startup at
* GDDRMAIN offset 000006AC (data at PSW 4038B219 02009540
* 50E8B219) if another GDDR instance was not shut down
* cleanly. This causes GDDRMAIN to terminate.
*
* PROBLEM RESOLUTION:
*
* An S067-04 abend should no longer occur upon GDDRMAIN
* startup if another GDDR instance was not shut down cleanly.
*
* In addition, the GDDRMAIN ESTAE routine has been improved to
* ensure that GDDRMAIN is shut down cleanly in case of an
* abend.
*
* MODULES: GDDRMAIN
* GDDRMCMD
*
* ------------------------------------------------------------
*
* PROBLEM FIXED: GDDR-3499
* USERS AFFECTED: GDDR users
* PROBLEM DESCRIPTION: New PRIMARY command to display primary
* C-system name
*
* DESCRIPTION DETAIL:
*
* A new command is needed to display the primary C-system name
* from any system in the GDDR-plex, including managed systems.
*
* PROBLEM RESOLUTION:
*
* A new PRIMARY command has been created to display the
* primary C-system name from the point-of-view of one or more
* C-systems. By default, the point-of-view from all C-systems
* is shown. The SYSTEM parameter may be used to narrow the
* scope to the specified C-system, and the SITE parameter may
* be used to narrow the scope to the C-system at the specified
* site. This command may be issued from any system where
* GDDRMAIN is active, including managed systems. It can be
* issued as a GDDRMAIN modify command (e.g., F GDDRMAIN,PRI),
* as a Perform Health Check panel primary command (e.g., PRI),
* or using the GDDRMCMD batch interface (see GDDRMCMD in
* SAMPLIB).
*
* Syntax:
*
* PRImary
* [,SITE={DC1|DC2|DC3|DC4}]
* [,SYStem={<system_name>|LoCaL|ALL}]
* [,TiMeOut=<seconds>]
* [,CONsole[={Yes|No}]]
* [,SysMSG[={Yes|No}]]
* [,SysPRinT[={Yes|No}]]
* [,DeBuG[={Yes|No}]]
*
* Example:
*
* GDDUC04I Primary C-system as seen from the indicated
* site/system
* ---------------------------------------------------------
* Site System Value
* ---- -------- -----------------------------------------
* DC1 N247 N247
* DC2 X99 N247
* DC3 X98 N247
* ---------------------------------------------------------
*
* MODULES: GDDRMCMD
* GDDRMCON
*
* ------------------------------------------------------------
++PTF(GD60005) REWORK(2023012) .
++VER(Z038) FMID(GDDR600)
/*
*-------------------------------------------------------------
* PROBLEM DESCRIPTION(S):
* ------------------------------------------------------------
*
* PROBLEM FIXED: GDDR-3463 GDDR-3465
* USERS AFFECTED: GDDR users
* PROBLEM DESCRIPTION: ABENDS0E0-29 upon GDDRMAIN startup or
* ABENDS0E0-28 upon GDDRMAIN shutdown
*
* DESCRIPTION DETAIL:
*
* An S0E0-29 abend could occur upon GDDRMAIN startup in the
* HBM (heartbeat monitor) subtask at GDDREVMI offset 0005AF74
* (data at PSW 183158F0 0010D507 3000F154). This causes the
* HBM subtask to terminate and leaves GDDRMAIN without
* heartbeat monitoring capabilities.
*
* In addition, an S0E0-28 abend could occur in GDDRRPT upon
* GDDRMAIN shutdown at GDDRMAIN offset 0006EAB2 (data at PSW
* D24FD37A 1000D207 D37D5004).
*
* PROBLEM RESOLUTION:
*
* An S0E0 abend should no longer occur upon GDDRMAIN startup
* in GDDREVMI or upon GDDRMAIN shutdown in GDDRRPT.
*
* MODULES: GDDREVMI
* GDDRRPT
Affected Products
Geographically Dispersed Disaster Restart (GDDR)Article Properties
Article Number: 000203766
Article Type: Solution
Last Modified: 07 Aug 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.