IBM Support

PH65077: GDPSIVP doesn't recognize FB1 as a valid SAPL parameter

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • GDPS Installation Verification Program (GDPSIVP)
    doesn't correctly recognize "FB1" as a valid VM SAPL
    parameter, when the parameters are not in the order that
    GDPS expects;
    
    In an MGM3SITE topology, with these parameters defined:
    
    FN: A1 (PDVOL=3B02) FN:A2(PDVOL=CB02) FN:FB1 (PDVOL=7B02)
    FN:B1 (PDVOL=9B02)
    
    The following messages were observed:
    
    CURRENT IPL PARAMETERS
    FN:A1(PDVOL=3B02)FN:A2(PDVOL=CB02)FN:FB1(PDVOL=7B02)
    
    Expected Selector is FN:A1(PDVOL=XXXX),FN:A2(PDVOL=XXXX),
    FN:B1(PDVOL=XXXX)
    
    In MGM4SITE neither "FA1" nor "FB1" is correctly recognized,
    and the observed message is:
    
    Expected Selector is FN:A1(PDVOL=XXXX),FN:A2(PDVOL=XXXX),
    FN:B1(PDVOL=XXXX),FN:B2(PDVOL=XXXX).
    

Local fix

  • In MGM3SITE topology, order the parameters in the sequence
    A1, A2, B1, FB1.
    
    In MGM4SITE topology, order the parameters in the sequence
    A1, A2, B1, B2, FA1, FB1
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: GDPS Metro Multiplatform Resiliency          *
    *                 for IBM Z (xDR)                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: GDPS Installation Verification Program  *
    *                      (GDPSIVP) doesn't correctly recognize   *
    *                      "FA1" or "FB1" as valid VM SAPL         *
    *                      parameters when the parameters are not  *
    *                      in order that GDPS expects.             *
    ****************************************************************
    In MGM3SITE topology, GDPS expects the order of parameters to
    be A1, A2, B1, FB1. In MGM4SITE topology, GDPS expects the order
    of parameters to be A1, A2, B1, B2, FA1, FB1. However the z/VM
    SET IPLPARMS does not require that order.
    

Problem conclusion

  • GDPSIVP has been changed to accept parameters in any order.
    
    KEYWORDS: GDPSXDRGUE/K
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH65077

  • Reported component name

    GDPS

  • Reported component ID

    694235B00

  • Reported release

    460

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-01-31

  • Closed date

    2025-05-16

  • Last modified date

    2025-07-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UO03275 UO03276 UO03277

Modules/Macros

  • VPCLIVHP
    

Fix information

  • Fixed component name

    GDPS

  • Fixed component ID

    694235B00

Applicable component levels

  • R460 PSY UO03277

       UP25/05/17 P F505

  • R470 PSY UO03276

       UP25/05/17 P F505

  • R480 PSY UO03275

       UP25/05/17 P F505

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":"460","Line of Business":{"code":"LOB66","label":"Technology Lifecycle Services"}}]

Document Information

Modified date:
15 July 2025