IBM Support

PM08382: SMTP ADDS X'00' TO HLQ.TEMP.NOTE FILE WHEN A RECORD IN THE JES SPOOL IS 1024 OR GREATER

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In this case a RECFM=VB lrecl=1029 file is put onto the jes
    spool where one of the lines in the email body is 1024 in
    length.  When SMTP reads the data off the jes spool and writes
    it to hlq.TEMP.NOTE, when is writes the line of size 1024 a
    null (x'00') is written at the end of the line.  This null can
    cause problems when other mailers try to process the mail.
    .
    This problem does not occur if the recommendations in the IP
    User's Guide, section SMTP responses is followed:
    Data lines must not exceed 998 characters in length for mail
    RFCs (this value does not include the carriage return/linefeed
    character (CRLF), which must be added to each data line).
    Internally, SMTP uses a slightly larger MaxDataLine value to
    hold record attributes.
    .
    KEYWORDS: nul null 00 x'00' blank email empty mail TEMP NOTE
    .
    VERIFICATION STEPS:
    Looking at the JES spool file, a x'00' is not found.  You can
    issue 'set hex on' to see the hex values.
    .
    Looking at the hlq.TEMP.NOTE, the file contains a x'00' at the
    end of a long line of data.
    

Local fix

  • Do not put emails on the spool that have a line length of 1024
    or greater.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the IBM Communications Server   *
    *                 for z/OS Version 1 Release(s) 9, 10, and     *
    *                 11 IP: SMTP                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: SMTP puts X'00' in HLQ.TEMP.NOTE file   *
    *                      when processing a record from the JES   *
    *                      spool that contains 1024 bytes of       *
    *                      data.                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    SMTP mistakenly puts X'00' in HLQ.TEMP.NOTE file when processing
    a record from the JES spool that contains 1024 bytes of data.
    SMTP is limited to 1024 bytes of data. Long data lines can be
    a problem for mail server since the mail RFC states that
    maximum data line is 998 bytes (excluding the carriage return
    and line feed characters).
    +-------------------------------------------------------------+
    + 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

  • SMTP code has been modified so the '00'x is not put into
    a long data line. However, SMTP is still limited to processing
    up to 1024 bytes and will now generate informational message
    EZA5132I when processing spool jobs that contain these long
    data lines.
    
    The following documentation changes have been made:
    ================================================================
    z/OS Communications Server IP Messages:
    Volume 1 (EZA)
    Document Number SC31-8783
    ----------------------------------------------------------------
    
    EZA5132I <mm/dd/yy> <hh:mm:ss>  Large record detected in spool
    job <spoolid>
    
    Explanation: This message is generated to show that a large
    record containing 1024 bytes was detected in the spool job.
    SMTP's implementation is limited to processing 1024 bytes
    of data. However, the mail RFC 821 limits the amount of bytes
    on a data line to 998 (excluding the carriage return and line
    feed characters). These long lines may get truncated by the
    remote SMTP server depending on its implementation. It is
    recommended that applications stay within the RFC specification.
    
    <mm/dd/yy> is the current date (month/day/year).
    <hh:mm:ss> is the current time (hours:minutes:seconds).
    <spoolid>  is the spool job identifier.
    
    System Action: SMTP continues.
    
    Operator Response: None.
    
    User Response: Not applicable.
    
    System Programmer Response: None.
    
    Problem Determination: Not applicable.
    
    Source: z/OS Communications Server TCP/IP: SMTP
    
    Module: SMTP
    
    Routing Codes: Not applicable.
    
    Descriptor Codes: Not applicable.
    
    Automation: Not applicable.
    
    * Cross Reference between External and Internal Names
    EZAAA00H (MSSMTP  )  EZABB01Z (SMTPBTCH)  EZAAA00H (MSSMTP  )
    EZABB01Z (SMTPBTCH)  EZAAA00H (MSSMTP  )  EZABB01Z (SMTPBTCH)
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM08382

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    190

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-02-23

  • Closed date

    2010-03-12

  • Last modified date

    2010-05-04

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

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

    UK55172 UK55173 UK55174

Modules/Macros

  • EZAAA00H EZABB01Z
    

Publications Referenced
SC31878310SC31878309SC31878308  

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R1A0 PSY UK55172

       UP10/04/07 P F004

  • R1B0 PSY UK55173

       UP10/04/07 P F004

  • R190 PSY UK55174

       UP10/04/07 P F004

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

Document Information

Modified date:
04 May 2010