A fix is available
APAR status
Closed as program error.
Error description
Was identified a potential issue when configuring an LCP profile with an SGC interval set to MINUTE(10). The system does not consistently honor the configured 10-minute interval due to a conflict with the minimum allowed time between captures, which is also defined as MINUTE(10). As a result, some SGC executions are silently skipped because the required minimum time between captures has not yet elapsed. This behavior prevents SGCs from being taken at the expected 10-minute frequency, leading to gaps in data collection.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: GDPS Metro and GDPS Global - GM users * * exploiting LCP Manager * **************************************************************** * PROBLEM DESCRIPTION: LCP scheduled Safeguarded Captures may * * be skipped when the Minimum Interval * * and Capture Interval management profile * * fields are set to the same value. * **************************************************************** When the Minimum Interval and Capture Interval Safeguarded Copy management profile fields are set to the same value, slight timing changes may cause captures to be skipped due to the Minimum Interval not having elapsed. The Minimum Interval should be set to a lower value than the Capture Interval, but when the Capture Interval is set to MINUTE(10), it is impossible to set the Minimum Interval lower since both values have MINUTE(10) as their lowest possible value.
Problem conclusion
This PTF corrects the reported problems by allowing the Minimum Interval of Safeguarded Copy and FlashCopy management profiles to be set as low as MINUTE(5). DOCUMENTATION CHANGES The GDPS Logical Corruption Protection Manager Installation and Customization Guide (ZG24-6763) and Stand-alone LCP Manager Installation and Customization Guide (ZG24-6765) are updated with the new Minimum Interval value range for FlashCopy and Safeguarded Copy management profiles. Minimum Interval The minimum amount of time that must elapse before a new capture is permitted. The value specified must be equal or less than the retention period. The minimum capture interval can be specified as: MINUTE(n) Where n is a value between 5 and 9999 HOUR(n) Where n is a value between 1 and 999 DAY(n) Where n is a value between 1 and 999 KEYWORDS: GDPSLCPMGR/K
Temporary fix
Comments
APAR Information
APAR number
PH71218
Reported component name
GDPS
Reported component ID
694235B00
Reported release
480
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2026-05-07
Closed date
2026-06-05
Last modified date
2026-06-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UO08157 UO08158 UO08159 UO08160 UO08161 UO08162
Modules/Macros
GEOGUIUS VPCEMP00 VPCPHL07
Fix information
Fixed component name
GDPS
Fixed component ID
694235B00
Applicable component levels
R470 PSY UO08161
UP26/06/09 I 1000
R47B PSY UO08162
UP26/06/09 I 1000
R480 PSY UO08159
UP26/06/09 I 1000
R48B PSY UO08160
UP26/06/09 I 1000
R490 PSY UO08157
UP26/06/09 I 1000
R49B PSY UO08158
UP26/06/09 I 1000
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSET85","label":"GDPS (Geographically Dispersed Parallel Sysplex)"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"480","Line of Business":{"code":"LOB66","label":"Technology Lifecycle Services"}}]
Document Information
Modified date:
09 June 2026