IBM Support

PM40024: INCORRECT JOBNAME WRITTEN OUT BY SYSLOGD

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • Syslogd sometimes write out an incorrect jobname for a
    particular message.  Here is an example:
    
    Apr 25 15:22:24 CS02TCP/TCPIP    LBAGENT  ftpd■16842812:
    EZY2700I Using port FTP control (21)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release(s) 11, 12,        *
    *                 and 13 IP: Syslogd                           *
    ****************************************************************
    * PROBLEM DESCRIPTION: On system with high syslog activity,    *
    *                      the userid/jobname field of log records *
    *                      contains incorrect information.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The syslogd multi-thread writers of log messages are serializing
    the copying of the userid/jobname field when writing log
    records.  The wrong user/jobname values are copied to the 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

Temporary fix

Comments

  • This APAR is being closed FIN (Fixed If Next) with concurrence
    from the submitting customer. This means that a fix to this
    APAR is expected to be delivered from IBM in a release (if any)
    to be available within the next 36 months.
    
    This problem will be tracked as Feature F153628
    by Communications Server for z/OS Development.
    
    The solution for this APAR is included in
    CS for zOS Version 2 Release 1.
    

APAR Information

  • APAR number

    PM40024

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    1B0

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-25

  • Closed date

    2011-06-03

  • Last modified date

    2013-09-16

  • 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

  • R1B0 PSN

       UP

  • R1C0 PSN

       UP

  • R1D0 PSN

       UP

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

Document Information

Modified date:
16 September 2013