IBM Support

PM22720: SYSLOGD FAILS TO ACTIVATE WHEN WRITING TO A REMOTE SERVER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Syslogd is configured to send data to a remote syslogd
    server by coding a hostname in syslog.conf. When syslogd is
    activated the hostname resolution fails because TCPIP is not
    active.  Syslogd should keep trying to resolve the hostname
    unitl the stack becomes active.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release(s) 10, 11, and    *
    *                 12 IP: SYSLOGD                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Should SYSLOGD be started before TCPIP  *
    *                      is available and SYSLOGD references a   *
    *                      host destination, the IP address of     *
    *                      that host is not resolved and SYSLOGD   *
    *                      does not attempt to resolve the host    *
    *                      again.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    SYSLOGD was not attempting to resolve hostnames after the first
    failure when the hostname was a destination for log messages.
    +-------------------------------------------------------------+
    + 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

  • SYSLOGD is amended to retry hostname resolution until all the
    hostnames have been successfully resolved.
    
    * Cross Reference between External and Internal Names
    EZASLOGD (SYSLOGD )  EZASLOGD (SYSLOGD )  EZASLOGD (SYSLOGD )
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM22720

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    1A0

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-09-17

  • Closed date

    2010-10-08

  • Last modified date

    2011-02-01

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

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

    UK61185 UK61186 UK61187

Modules/Macros

  • EZASLOGD
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R1A0 PSY UK61185

       UP11/01/08 P F101

  • R1B0 PSY UK61186

       UP11/01/08 P F101

  • R1C0 PSY UK61187

       UP11/01/08 P F101

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

Document Information

Modified date:
01 February 2011