IBM Z System Automation

Expand all | Collapse all

BCPii Health Check Errors GEOH049E Trying to Retrieve LPAR Information

  • 1.  BCPii Health Check Errors GEOH049E Trying to Retrieve LPAR Information

    Posted Fri July 02, 2021 02:49 AM
    I recently upgraded a customer to GDPS 4.4 and am receiving health check alerts on BCPII connections.  GDPS shows the BCPii connection as operating and we are successful in all IPL, Load etc. functions.  I've searched the SA manual and don't see any changes in the HMC/SE or security setup to eliminate these errors.  Can anyone tell me what is required to resolve this on either a z/14 or z/15?


    GEOH049E VPC8C006 GDPS_CHECK_K_SYS_LPAR The LPAR(K1T4) configuration

    definitions are not available.

       Explanation:  The health check is not able to retrieve the LPAR

        initial capped settings from the CPC Service Element.

       System Action:  Processing continues if appropriate.

       Operator Response:  Inform your System Programmer.

       System Programmer Response:  Check your BCP Internal Interface

        communication and execute GDPS Monitor3 to collect LPAR definitions.

       Problem Determination:  n/a

       Source:  GDPS

     

    GEOH049E VPC8C006 GDPS_CHECK_K_SYS_LPAR The LPAR(K1T4) configuration

    definitions are not available.

       Explanation:  The health check is not able to retrieve the LPAR

        workload manager settings from the CPC Service Element.

       System Action:  Processing continues if appropriate.

       Operator Response:  Inform your System Programmer.

       System Programmer Response:  Check your BCP Internal Interface

        communication and execute GDPS Monitor3 to collect LPAR definitions.

    Thanks,
    Sue Douglass

    ------------------------------
    Susan Douglass
    ------------------------------


  • 2.  RE: BCPii Health Check Errors GEOH049E Trying to Retrieve LPAR Information

    Posted Fri July 02, 2021 05:27 AM
    Hello Sue,

    did you address this issue to GDPS support as well ? I see that GDPS in the past provided fixes for issues in that area (see e.g. PI46036).

    regards,
    Thomas

    ------------------------------
    Thomas Braitmaier
    ------------------------------