GDDR: Upgrade to z/OS 2.5 Causes abends and GDDR Control SYSTEMS to Run in Degraded Mode
Summary: Upgrade to z/OS 2.5 causes abends in Geographically Dispersed Disaster Restart (GDDR), and GDDR Control SYSTEMS (C-SYS) runs in Degraded Mode.
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
The mainframe operating software is updated to z/OS 2.5 software level with maintenance tolerance. z/OS 2.5 is used for a new IBM z16 CPU.
GDDR GDDRMAIN started up with several ABENDs after the z/OS maintenance was applied:
- HBM reports the below error at GDDRMAIN startup, GDDR host is in degraded mode:
ABEND S0E0-29
- GDDRRPT reports the below error at GDDRMAIN shutdown:
ABEND S0E0-28
The following error message posts in GDDR Event Monitor (EVM) and Heartbeat Monitor (HBM) output:
GDDUG86E No matching GDDR systems found
If ABEND S0E0-28 occurs on GDDRMAIN shutdown, then an Abend S067-04 may occur if GDDRMAIN is brought back up.
Cause
An
In addition, an
ABEND S0E0-29 may occur upon GDDRMAIN startup in the HBM subtask at module GDDREVMI, offset 0005AF74.
PSW 183158F0 0010D507 3000F154This causes the HBM subtask to terminate and leaves GDDRMAIN without heartbeat monitoring capabilities. The GDDR host runs in degraded mode. GDDREVMI is updated to clear REGISTER AR15 before using the register to avoid an
ABEND S0E0-29.
In addition, an
ABEND S0E0-28 may occur in GDDRRPT upon GDDRMAIN shutdown at GDDRMAIN, offset 0006EAB2.
PSW D24FD37A 1000D207 D37D5004GDDRRPT is updated to clear REGISTER AR1 to avoid an
ABEND S0E0-28. GDDRMAIN is updated to verify that the data space 2 Access List Entry Token (ALET) is valid. This action is done before accessing the data space for another GDDR instance. This action helps avoid an Abend S067-04 in the GDDRMAIN startup due to another GDDR instance not shutting down cleanly.Resolution
Workaround:
- None for ABEND S0E0-29 but the GDDR hosts continue to run in degraded mode.
- An Initial Program Load (IPL) of the Logical Partition (LPAR) is required to clear memory if an
Abend S067-04occurs.
Permanent Fix:
- For GDDR 6.0, Program Temporary Fix (PTF) GD60004 and GD60005 are available for download from Dell Support.
- For GDDR 6.1, the issue is resolved in the base product. It is available to download from Dell Support.
Additional Information
Program Temporary Fix (PTF) Description -
++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.