GDDR：升級至 z/OS 2.5 會導致中止和 GDDR 控制系統以降級方式執行
Summary: 升級到 z/OS 2.5 會導致地理位置分散的災難重新啟動 （GDDR） 中止，並且 GDDR 控制系統 （C-SYS） 以降級方式運行。
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
大型機操作軟體已更新到具有維護容忍度的 z/OS 2.5 軟體級別。z/OS 2.5 用於新的 IBM z16 CPU。
GDDR GDDRMAIN 在套用 z/OS 維護後，啟動時具有數個 ABEND：
- HBM 在 GDDRMAIN 啟動時回報以下錯誤，GDDR 主機處於降級模式：
ABEND S0E0-29
- GDDRRPT 在 GDDRMAIN 關機時回報以下錯誤：
ABEND S0E0-28
GDDR 事件監視器 （EVM） 和活動訊號監視器 （HBM） 輸出中出現下列錯誤訊息：
GDDUG86E No matching GDDR systems found
如果 ABEND S0E0-28 GDDRMAIN 關機時發生，然後 Abend S067-04 如果 GDDRMAIN 重新連線，可能會發生。
Cause
透過提供邏輯區塊介面到快閃記憶體裝置，
此外，一個
ABEND S0E0-29 可能發生在 GDDRMAIN 啟動時，在模組 GDDREVMI 的 HBM 子任務中，偏移 0005AF74。
PSW 183158F0 0010D507 3000F154這會導致 HBM 子任務終止，並使 GDDRMAIN 失去檢測信號監控功能。GDDR 主機以降級模式執行。GDDREVMI 已更新，可在使用寄存器前清除寄存器 AR15，以避免
ABEND S0E0-29。
此外，一個
ABEND S0E0-28 GDDRPMAIN 於 GDDRMAIN 關機時，可能會發生於 GDDRRPT 中，偏移 0006EAB2。
PSW D24FD37A 1000D207 D37D5004GDDRRPT 已更新以清除註冊 AR1，以避免
ABEND S0E0-28。GDDRMAIN 已更新，以驗證資料空間 2 存取清單項目權杖 （ALET） 是否有效。此操作在訪問另一個 GDDR 實例的數據空間之前完成。此操作有助於避免 Abend S067-04 在 GDDRMAIN 啟動中，因為另一個 GDDR 例項未完全關閉。Resolution
因應措施：
- 無中止 S0E0-29，但 GDDR 主機繼續以降級模式執行。
- 在出現以下情況時，需要邏輯磁碟分割 （LPAR） 的初始程式載入 （IPL） 才能清除記憶體：
Abend S067-04發生。
永久修正：
Additional Information
程式臨時修正 （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.