IBM Support

PK49047: Function getaddinfo() fails when run through the MVFS on Vista

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • The standard Windows API call getaddrinfo will fail with a 11003
    return code when called in an application, which equates to:
    This is a nonrecoverable error.
        This indicates that some sort of nonrecoverable error occurr
    ed during a database lookup. This may be because the database fi
    les (for example, BSD-compatible HOSTS, SERVICES, or PROTOCOLS f
    iles) could not be found, or a DNS request was returned by the s
    erver with a severe error.
    This only fails when the following are true:
     - Windows Vista OS
     - Executable located in a view vob context
     - Dynamic views
    No problem if:
     - XP, 2003
     - Executable located outside the mvfs
    

Local fix

Problem summary

  • The standard Windows API call getaddrinfo will fail with a
    11003 return code when called in an application, which
    equates to:
    
    This is a nonrecoverable error.
        This indicates that some sort of nonrecoverable error
    occurred during a database lookup. This may be because the
    database files (for example, BSD-compatible HOSTS, SERVICES,
    or PROTOCOLS files) could not be found, or a DNS request was
    returned by the server with a severe error.
    
    This only fails when the following are true:
     - Windows Vista OS
     - Executable located in a view vob context
     - Dynamic views
    
    No problem if:
     - XP, 2003
     - Executable located outside the mvfs
    

Problem conclusion

  • This is a low priority APAR and would not fit into our 18
    month fix cycle.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK49047

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    700

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-07-16

  • Closed date

    2009-04-09

  • Last modified date

    2009-04-09

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
09 April 2009