IBM Support

PM77038: HEALTHCHECKER FAILS TO CREATE SOCKET WHEN STARTED BY AUTOMATION AFTER MESSAGE EZAIN11I

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • HealthChecker fails to create socket when started after TCPIP
    message EZAIN11I. The TCPIP stack being used is also configured
    for ATTLS but the message EZZ4250I AT-TLS SERVICES ARE
    AVAILABLE FOR xxx had not been issued yet. The following
    message is issued by Health Checker when the erro occurs
    EZBH900I INTERNAL ERROR: Function BPX1SOC RC 000 00070 RSN
    74610296
    
    
    
    
    
    
    
    
    Additional Symptom(s) Search Keyword(s): HealthChecker health
    checker
    

Local fix

  • Grant read access to the HealthChecker address space for the
    EZB.INITSTACK.sysname.tcpname resource profile in the SERVAUTH
    class or start The HealthChecker address space after message
    EZZ4250I
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release(s) 13 IP:         *
    *                 AT-TLS                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: z/OS Health Checker fails the initial   *
    *                      TCP/IP health checks with diag code     *
    *                      00000070_74610296 when TCPCONFIG TTLS   *
    *                      is configured.                          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    z/OS Health Checker fails the initial TCP/IP health checks with
    diag code 00000070_74610296 when TCPCONFIG TTLS is configured.
    
    The TCP/IP stack initialization process detects TCPCONFIG TTLS
    is configured in the profile and blocks access to sockets
    until Pagent has installed the TTLS policy.  The blocking of
    sockets is accompanied by message "EZZ4248E TCPCS2 WAITING FOR
    PAGENT TTLS POLICY".  The stack initialization continues and
    when all core functions are initialized message "EZB6473I
    TCP/IP STACK FUNCTIONS INITIALIZATION COMPLETE" is issued.
    The stack initialization performs an internal Health Checker
    initialization now that the core stack functions are
    available.  Health Checker drives a TCP/IP health checking
    function that opens a socket, however the socket call fails
    if Pagent has not completed the installation of the TTLS
    policy.
    
    HZS1002E CHECK(IBMCS,CSTCP_SYSPLEXMON_RECOV_tcpname):
    AN ERROR OCCURRED, DIAG: 00000070_74610296
    HZS1002E CHECK(IBMCS,CSTCP_IPMAXRT4_tcpname):
    AN ERROR OCCURRED, DIAG: 00000070_74610296
    HZS1002E CHECK(IBMCS,CSTCP_TCPMAXRCVBUFRSIZE_tcpname):
    AN ERROR OCCURRED, DIAG: 00000070_74610296
    HZS1002E CHECK(IBMCS,CSTCP_CINET_PORTRNG_RSV_tcpname):
    AN ERROR OCCURRED, DIAG: 00000070_74610296
    HZS1002E CHECK(IBMCS,CSTCP_IPMAXRT6_tcpname):
    AN ERROR OCCURRED, DIAG: 00000070_74610296
    
    Granting the z/OS Health Checker read access to the SERVAUTH
    resource EZB.INITSTACK.sysname.tcpname.
    +-------------------------------------------------------------+
    + Please check our Communications Server for OS/390 homepages +
    + for common networking tips and fixes.  The URL for these    +
    + homepages can be found in Informational APAR II11334.       +
    +-------------------------------------------------------------+
    

Problem conclusion

  • EZBTIINI has been amended to defer the initialization call to
    HealthChecker until Pagent has installed the AT-TLS policy
    when TCPCONFIG TTLS is configured.
    
    * Cross Reference between External and Internal Names
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM77038

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    1D0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-13

  • Closed date

    2012-12-30

  • Last modified date

    2013-03-04

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

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

Modules/Macros

  • EZBCTFME EZBITTRC EZBMODID EZBTIINI EZBTIPFS
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R1D0 PSY UK90669

       UP13/02/02 P F302

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":"1D0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1D0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 March 2013