IBM Support

PI91999: GDPS FIX PACKAGE 2018-01

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This APAR provides miscellaneous minor fixes.
    See problem summary for details.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: GDPS/PPRC GDPS/MTMM GDPS/XRC GDPS/MZGM       *
    *                 GDPS/HYPERSWAP MANAGER                       *
    *                 Keywords:                                    *
    *                 GDPSPPRC/K GDPSPPRCHM/K GDPSXRC/K            *
    *                 GDPSMTMM/K                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: Miscellaneous GDPS fixes                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Problems addressed in GDPS release 3.14 only
      - Reduce the length of the reason text in message GEO252E to
        prevent the WTO text exceeding the single line WTO length.
      - GEO000I erroneously issued as a pink SDF alert by topology
        monitoring following the issuance of message GEO096I
      - SDF alerts GEO2649W and GEO2648W may be erroneously issued
        stating that GDPS AUTOC rules were found inactive and have
        been restored.
      - Incorrect color used for GDPS level in panel VPCPSTA1 when
        at least one system has been upgraded to GDPS 4.1.
      - GDPS Health Check returns false GEOH076E due to the wrong
        site indicator being used in a GDPS/MTMM single leg
        configuration.
    
    Problems addressed in GDPS release 3.13 & 3.14
      - Unless the NOFLASH parameter is specified, START SECONDARY
        will attempt to capture a FlashCopy prior to restarting
        replication. GDPS maintains a flag for each replication site
        indicating whether FC devices are configured. These flags
        are used to determine whether a FlashCopy should be
        attempted. A defect exists where START SECONDARY tests the
        wrong replication site flag. For clients with FC devices
        defined in only one site, START SECONDARY processing may
        incorrectly conclude that FC devices are not available and
        not attempt to capture a FlashCopy. A circumvention to this
        defect is to use the FCESTABLISH script to capture the
        FlashCopy and to then specify NOFLASH on the START SECONDARY
        script.
      - The DASD=RECOVER script and the HYPERSW RECOVER command may
        generate unnecessary SDF trace entries indicating CDELPAIR
        failures with RC=7140. This may occur when the recover is
        requested with the SIMPLEX option. These trace entries
        should be suppressed since they can legitimately occur as
        part of the recovery process.
      - Increased CPU utilization in the master controlling system
        may be experienced due to "Soft Fence" monitoring scheduled
        by Monitor1. This monitoring has now been moved to Monitor3
        therefore reducing frequency and CPU utilization.
      - The GDPS XRC SPOF and PAV configuration health checks were
        no longer being executed following a change to the format of
        message ANT8283I introduced by SDM support for 5-digit
        device numbers.
      - Implements changes to reduce NetView processing and logging
        associated with SDF alerts.
      - GDPS Health Check GDPS_Check_XCF_CDS rc=4 rsn=405 may occur
        indicating that the answer area for the ISGQUERY request is
        too small to contain all of the requested data. Health Check
        processing continues.
    

Problem conclusion

  • Problems have been fixed in the specified releases
    

Temporary fix

  • PI91999
    

Comments

  • ×**** PE18/04/18 FIX IN ERROR. SEE APAR PI96827  FOR DESCRIPTION
    ×**** PE18/06/21 FIX IN ERROR. SEE APAR PI98774  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PI91999

  • Reported component name

    GDPS-GEO DISP P

  • Reported component ID

    694235B00

  • Reported release

    3E0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-01-03

  • Closed date

    2018-04-03

  • Last modified date

    2018-09-06

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

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

    UI54946 UI54947 UI54948 UI54949

Modules/Macros

  • GEOCB005 GEOCME00 VPCEACTA VPCEALRT VPCEAMTA
    VPCEAOMS VPCEDASD VPCEHPXA VPCEINIT VPCEIPCO VPCEMDAS VPCEMON3
    VPCEMSGB VPCESTA1 VPCETAKE VPCETOPO VPC8C009 VPC8C012 VPC8C013
    

Fix information

  • Fixed component name

    GDPS-GEO DISP P

  • Fixed component ID

    694235B00

Applicable component levels

  • R3DA PSY UI54948

       UP18/04/05 P F804

  • R3DH PSY UI54949

       UP18/04/04 P F804

  • R3D0 PSY UI54946

       UP18/04/04 P F804

  • R3E0 PSY UI54947

       UP18/04/04 P F804

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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3E0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
06 September 2018