PK88426: ASCII APPLCATION'S GETADDRINFO FAILS WHEN /ETC/SERVICES IS TAGGED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An application copiled in ascii does a getaddrinfo.  When
  /etc/services is tagged, this call fails with return code 8 and
  error message:
  EDC9508I The service passed was not recognized for the specified
  socket type.
  An application copiled in ebcdic does not have a problem.
  .
  KEYWORDS: resolver sap services getservbyname
  .
  VERIFICATION STEPS:
  ls -T /etc/services shows:
  t IBM-1047    T=on  /etc/services.
  This means /etc/services is tagged.
  

Local fix

• Remove the tag on /etc/services by using chtag -r /etc/services
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release 11 IP:            *
  *                 Resolver                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: If a Native ASCII compiled C/C++        *
  *                      program uses resolver API calls the     *
  *                      call can fail if z/OS UNIX Auto         *
  *                      Conversion is active and the resolver   *
  *                      file system files are tagged with       *
  *                      EBCDIC IBM-1047.                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The resolver configuration files on z/OS must contain EBCDIC
  data. When a Native ASCII C/C++ program invokes resolver API
  calls (for example, getaddrinfo or getnameinfo) the resolver
  needs to read file system files (for example, /etc/hosts and
  /etc/services) to complete the API call. If z/OS UNIX auto
  conversion (AUTOCVT=ON) is active and the files are tagged
  with IBM-1047 the EBCDIC data will be converted to ASCII. This
  conversion causes the resolver to fail the API call as it
  can not process the ASCII character configuration data.
  A getaddrinfo() with a service name provided will fail with:
  EAI_SERVICE - EDC9508I The service passed was not recognized
  for the specified socket type.
  +-------------------------------------------------------------+
  + 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

• The resolver is amended to process a Native ASCII application
  API call that needs configuration data in a file system file
  that is tagged with IBM-1047.
  
  * Cross Reference between External and Internal Names
  

Temporary fix

Comments

APAR Information

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

  PK77955

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

  UK48106

Modules/Macros

• EZBREARR EZBRECMD EZBREFMT EZBRELST EZBREPRT
  EZBRERCD EZBRESRV
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R1B0 PSY UK48106

     UP09/08/05 P F908

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.