PM76512: SYSLOGD GENERATED ABEND DURING TERMINATION

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • The SYSLOGD address space takes a dump during termination.
    There was no prior abend that caused the dump to occur. A
    Timing scenario exists where the domark() function (a SIGALRM
    signal handler) was being invoked after the die() function
    during SYSLOGD termination.
    The following LE C traceback of routines is displayed when IPCS
    Verbx Ledata 'ceedump ntheads(*)'
    
    is issued against the dump:
    
    DSA      Entry       E  Offset  Statement     Load Mod
    
    1        EZBTDUMP    +00000276                EZASLOGD
    2        catchAbend  +000000AA                EZASLOGD
    3                    +00000720                CEEEV003
    4                    +000001C2                CEEEV003
    5                    +00000D60                CEEPLPKA
    6                    +00000208                CEEEV003
    7                    +000000CE                CEEEV003
    8     slg_thread_lock
                         +000002C0                EZASLOGD
    9     slg_serialize_inet
                         +0000008E                EZASLOGD
    10     domark        +00000102                EZASLOGD
    11                   +00000720                CEEEV003
    12                   +000000D6                CEEEV003
    13                   -082E8263                CEEPLPKA
    14                   +003859FA                CEEEV003
    15                   +10CD26D2                CEEEV003
    16       die         +0000051E                EZASLOGD
    17                   +00000720                CEEEV003
    18                   +000000D6                CEEEV003
    19                   -082E8263                CEEPLPKA
    20       logmsg      -1092C6F6                EZASLOGD
    21                   +10B65C56                CEEEV003
    22       main        +00001E16                EZASLOGD
    23                   +10C4C178                CEEEV003
    24                   +000001C4                CEEPLPKA
    
    
    Restart of SYSLOGD works without error
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release(s) 13: SYSLOGD    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When stopping syslogd, syslogd          *
    *                      terminates abnormally in the domark()   *
    *                      function.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The domark() function (a SIGALRM signal handler) was being
    invoked after the die() function was invoked which was
    destroying the locks.  Failure occurred when the domark
    function cause a lock to be obtained which already had been
    obtained for the thread by the die() function.
    +-------------------------------------------------------------+
    + 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 prevent the domark function from being
    invoked when the die() function is entered.
    
    * Cross Reference between External and Internal Names
    EZASLOGD (SYSLOGD )
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76512

  • 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-05

  • Closed date

    2012-11-13

  • Last modified date

    2013-01-02

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

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

    UK83479

Modules/Macros

  • EZASLOGD
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R1D0 PSY UK83479

       UP12/12/18 P F212

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.



Rate this page:

(0 users)Average rating

Document information


More support for:

z/OS family

Software version:

1D0

Operating system(s):

z/OS

Reference #:

PM76512

Modified date:

2013-01-02

Translate my page

Machine Translation

Content navigation