PN92232: SMTPNOTE HAS A DEFAULT TIMEZONE VALUE OF "LCL". LCL IS NOT A VALID TIMEZONE VALUE PER RFC 822. THIS CAUSES INCORRECT OUTPUT.

APAR status

• Closed as documentation error.

Error description

• From MVS HOST, customer uses SMTPNOTE to send out a note.
  EVERYTIME SMTPNOTE sends it's header, the timezone equals
  "LCL".  If in the SMTP CONFIG file, the TIMEZONE = EST is
  specified, the "external wrapper" or "outside header" (RFC
  821) shows EST as the timezone as expected, but (the internal
  header still has "LCL" for it's timezone).  Since, "LCL" is
  not known via RFC 822, his MAIL STATION (Microsoft Exchange)
  defaults to GMT for the internal header; thus, subtracts 5
  hours from the actual EST.
  As documented in the Customization and Administration
  manual, chap 12 in (SC31-7134-02) or pg 393 in
  SC31-7134-03 (STEP 3: Update the SYSTEM CLIST and
  PARMLIB Data Sets), customers "MUST COPY and
  customize the SMTPNOTE CLIST on EVERY SYSTEM where users
  will be able to send mail with the smtpnote command".
  It then lists the SMTP variables that need to be
  customized.  Unfortunately, it did NOT list TIMEZONE as
  one of them.
    We need to update the manuals to reflect this requirement.
  We also need to modify SMTPNOTE's default TIMEZONE value to one
  that is supported according to RFC 822.  Example: GMT, instead
  of LCL.
    In addition, we may want to document the USER's GUIDE with
  some of this info too.
  

Local fix

• In the SMTPNOTES CLIST, change the TIMEZONE value to
  appropriate value.  A clipping of that CLIST follows:
  TIMEZONE   The time zone which appears in the "Date:"
             stamp of the RFC 822 header.
             SET TIMEZONE = LCL
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All SMTP users.                              *
  ****************************************************************
  * PROBLEM DESCRIPTION: When a note is sent with SMTPNOTE, the  *
  *                      time zone in the internal header may    *
  *                      be LCL.  LCL is not a supported value   *
  *                      according to RFC 822.                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The timezone variable in the SMTPNOTE CLIST should be
  customized, but this is not documented.
  

Problem conclusion

• The TCP/IP for MVS Version 3 Release 1 Customization and
  Administration Guide
  (SC31-7134-02) should be changed as follows:
  
  In Chapter 13 'Configuring the SMTP Server' in 'Step 3: Update
  the System CLIST and PARMLIB Data Sets', add the following
  information after the paragraph explaining TEMPDSN:
  
      TIMEZONE   The time zone which appears in the "Date:"
                 stamp of the RFC 822 header. The default is
                 LCL for local time.  See RFC 822 for time zone
                 values.
  
  The equivalent softcopy file will also be updated.
  
  
  The TCP/IP for MVS Version 3 Release 2 Customization and
  Administration Guide
  (SC31-7134-03) should be changed as follows:
  
  In Chapter 12 'Configuring the SMTP Server' in 'Step 3: Update
  the System CLIST and PARMLIB Data Sets', add the following
  information after the paragraph explaining TEMPDSN:
  
      TIMEZONE   The time zone which appears in the "Date:"
                 stamp of the RFC 822 header.  The default is
                 LCL for local time.  See RFC 822 for time zone
                 values.
  
  The equivalent softcopy file will also be updated.
  
  
  * Cross Reference between External and Internal Names
  SPA_NAME (IDSS_NAM)
  

Temporary fix

Comments

APAR Information

• 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