IBM Support

PI58100: SOME OTELNETD MESSAGES WRITTEN TO SYSLOGD DESTINATION APPEAR ON MULTIPLE LINES IN ARCHIVED SYSLOG DATASETS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • The following messages are written to SYSLOGD destination:
    
    . EZYTU02E UTILITY:Read from ttloop. Peer died.  . EDC5000I No
    error occurred. rsn=00000000
    
    However, when the syslogd file is archived the same message
    appears on mltiple lines, with one additional blank line after
    the second record:
    
    EZYTU02E UTILITY:Read from ttloop. Peer died.
    EDC5000I No error occurred. rsn=00000000
    .
    
    
    
    
    Additional Symptom(s) Search Keyword(s): syslogd archive otelnet
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server for z/OS Version  *
    * 2 Release 1 and Release 2 IP: syslogd archive                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * The syslogd archive function splits records that contain a   *
    * carriage-return into multiple records in the archive file.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * FIN                                                          *
    ****************************************************************
    The syslogd log file may contain records which have a
    carriage-return within the record. When this log file is
    archived the single record is split into multiple reocrds in the
    archive file.
    

Problem conclusion

Temporary fix

Comments

  • The solution for this APAR is included in CS for zOS Version 2
    Release 3.
    
    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.
    

APAR Information

  • APAR number

    PI58100

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    210

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-02-25

  • Closed date

    2016-03-31

  • Last modified date

    2017-09-20

  • 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

  • R210 PSN

       UP

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

Document Information

Modified date:
20 September 2017