IBM Support

PQ00019: SMTP LOOPS WITH MESSAGE EZA5335E FOR VARIOUS TEMP DATASETS: IE: UNABLE TO ALLOCATE NEW FILE SYS2.SMTP.SYSB.CONN257.NOTE RC=4

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When processing SMTP mail requests, SMTP allocates temporary
    datasets.  If it fails to allocate these datasets due to
    insufficient space on volser, vtoc, etc., it issues message
    EZA5335E with rc = 4, repeatedly, until SMTP is restarted:
    EZA5335E Unable to allocate new file SYS2.SMTP.SYSB.CONN257.NOTE
    EZA5335E Unable to allocate new file SYS2.SMTP.SYSB.CONN256.NOTE
    ...
      The information about this message, in our IP Messages manual,
    SC31-8517-00 lacks diagnostic information to help determine the
    cause of the problem or where to look for possible allocation
    problem.  RC = 4 provides little information.  Ideally, if we
    could propagate the reason code from the allocation failure,
    then it would help a great deal.  Currently, multiple routines
    call Xallocate and MVS utilities; thus, a change in that area
    would not be feasible; however, at the application layer, we can
    use the S99Error procedure to use MVS's IEFDB476 service routine
    to be able to deliver dynamic allocation or enq failures to the
    log.  In this case, we could modify EZA5335E to point to this
    IKJ... message or so.  In this case, one would be able to see
    messages similar to these below:
      EZA5335E... IKJ56241I dataset xyz not allocated
                  IKJ56241I specified unit is undefined
                  DYNALLOC Reason Code Error = 021C, info = nnnn
      EZAxxxxx... Failed to open dataset xyz
    .
    VERIFICATION STEPS: Check MVS LOG for SMTP messages appearing as
    EZA5335E Unable to allocate new file SYS2.SMTP.SYSB.CONN256.NOTE
    EZA5335E Unable to allocate new file SYS2.SMTP.SYSB.CONN257.NOTE
    ...
    ADDITIONAL SYMPTOMS: May also find trace back messages such as:
          TRACE BACK OF CALLED ROUTINES
     ROUTINE                          STMT AT ADDRESS IN MODULE
     SVC202                            149    0006CDEC   SMMVSUB
     DODATA                             32    000A3F80   SMTPCMDS
     DOCOMMAND                          49    000A7E50   SMTPCMDS
     MAINLOOP                          158    00022C06   SMTP
     <MAIN-PROGRAM>                     12    00023D5A   SMTP
     VSPASCAL                                 000FC806
    .
    KEYWORDS: Dynamic allocation SVC99 SVC202 EZA5335E LOOP RC = 4
    

Local fix

  • While the VTOC INDEX is full, SMTP will not run properly.  Thus,
    fix the VTOC INDEX and restart SMTP.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of the eNetwork Communications     *
    *                 Server for OS/390 Release 7 IP: SMTP         *
    ****************************************************************
    * PROBLEM DESCRIPTION: The message SMTP EZA5335E did not       *
    *                      contain enough information for the      *
    *                      customer to understand why dynamic      *
    *                      allocation was failing so that          *
    *                      the problem could be corrected.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When dynamic allocation of a data set (DYNALLOC - SVC 99) fails,
    SMTP generates an error message. However, that error message
    does not contain enough information regarding the failure for
    the customer to correct the situation. Many of these errors
    occur due to DASD management problems such as volume table of
    contents (VTOC) full.
    +-------------------------------------------------------------+
    + 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

  • Added the following new informational message EZA5560I to
    contain more data regarding the SVC 99 failure. These additional
    messages will appear in the SMTP job log after the failing SMTP
    error message.
    
    OS/390 Communications Server
    IP Messages Volume 1
    Document Number SC31-8517
    
    The following documentation should be changed to explain the new
    message.
    
      --------------------------------------------------------------
      EZA5560I error_message
    
      Explanation:
      This diagnostic message is preceded by an SMTP error message.
      This message displays the text of the Dynamic Allocation
      (SVC 99-DYNALLOC) message. This message provides additional
      information about why the Dynamic Allocation failed. The
      message might be issued multiple times to include the complete
      text from Dynamic Allocation.
    
      error_message is the text of the message produced by DYNALLOC.
    
      System Action: SMTP might halt or continue depending on the
      preceding SMTP error message.
    
      User or Operator Response: Notify the system programmer of the
      error.
    
      System Programmer Response: Use the text of this message and
      the documentation describing Dynamic Allocation (DYNALLOC) in
      MVS/ESA SP V5 Authorized Assembler Services Guide to
      determine the cause of the error and respond as indicated.
      Most of these problems are DASD management related so you
      stop the SMTP started task, correct the problem, then restart.
    
      Source Data Set: SMMVSUB
    
      Procedure Name: SMTP_s99error
    
    
    * Cross Reference between External and Internal Names
    EZAAA00H (MSSMTP  )  EZAAI00V (SMTPGLOB)  EZABB01X (SMTP    )
    EZABB024 (SMTPQUEU)  EZABB04L (SMMVSUB )
    

Temporary fix

Comments

APAR Information

  • APAR number

    PQ00019

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    370

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2001-09-13

  • Closed date

    2001-09-20

  • Last modified date

    2001-11-01

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

    PQ41198

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

    UQ57958

Modules/Macros

  • EZAAA00H EZAAI00V EZABB01X EZABB024 EZABB04L
    

Publications Referenced
SC31851702    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R370 PSY UQ57958

       UP01/10/19 P F110

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

Document Information

Modified date:
01 November 2001