IBM Support

PI09477: ASCII MODE GETADDRINFO CALL FAILS IF ONLY VALID HEX CHARACTERS ARE IN HOSTNAME

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Unpredictable results occur with ASCII mode caller
    GETADDRINFO when called with a host name that contains valid
    hex values.  The resolver code handling the getaddrinfo is
    attempting to figure out if the value passed is an IPv6 address
    or a hostname, but during this processing incorrect ascii ti
    ebcdic transtaion is being done causing a bad value to be
    passed on the getaddrinfo call.
    
    an example of a host name that would fail would be BBA1 or
    AABBCCD1 and a working hostname would be BBS1 or AABBCCZ1
    
    
    
    
    
    
    
    Additional Symptom(s) Search Keyword(s): ASCII mode GETADDRINFO
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server                   *
    * for z/OS Version 2 Release 1: IP Resolver                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When getaddrinfo() is called to                              *
    * translate an ASCII hostname the                              *
    * hostname becomes mangled and a host                          *
    * name not found is returned to the                            *
    * caller.                                                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply PTF                                                    *
    ****************************************************************
    The hostname is translated from ASCII to EBCDIC to perform a
    test for an IPv6 address.  The host name is not an IPv6 address.
    The host name is left in EBCDIC where it is translated again
    from ASCII to EBCDIC resulting in a mangled name that cannot be
    found.
    +-------------------------------------------------------------+
    + Please check our Communications Server for z/OS homepages  +
    + for common networking tips and fixes.  The URL for these    +
    + homepages can be found in Informational APAR II11334.       +
    +-------------------------------------------------------------+
    

Problem conclusion

  • The getaddrinfo() function will be amended to translate the host
    name to EBCDIC in a temporary work area.
    
    After applying the maintenance, use the following guidelines to
    stop and restart the resolver:
    
    1. If you have LLA running, then refresh it with the system
       operator command
          MODIFY  LLA,REFRESH
    
    2. Stop the resolver
       a. If you have not customized the resolver, issue the system
          operator command
             STOP RESOLVER
       b. If you have customized the resolver, issue the system
          operator command
             STOP <procname>
             where <procname> is the name of your PROCLIB member
    
    3. Restart the resolver
       a. If you have not customized the resolver, issue the system
          operator command
             START IEESYSAS.RESOLVER,PROG=EZBREINI,SUB=MSTR
       b. If you have customized the resolver, issue the system
          operator command
             START <procname>  or  START <procname>,SUB=MSTR
             where <procname> is the name of your PROCLIB member
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI09477

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-13

  • Closed date

    2014-02-04

  • Last modified date

    2014-04-02

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

    PI07707

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

    UI14793

Modules/Macros

  • EZBREGAI
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R210 PSY UI14793

       UP14/03/28 P F403

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":"210","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":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 April 2014