IBM Support

PM88514: ABEND0C4 RC11 WHEN EXECUTING MODIFY COMMAND DURING SMTP INITIALIZATION

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A MODIFY command was issued for SMTP before SMTP had fully
    initialized causing an ABEND0C4 RC11.
    
    This APAR could have multiple symptoms.
    
    Verification Step:
    
    Verification Steps for ABEND during SMS processing:
    
    1) The following message is issued:
    IGD300I AN ABEND OCCURRED DURING SMS PROCESSING
    
    2) Dump Title is:
    DUMP TITLE=COMPON=SMS,COMPID=DF101,ISSUER=IGDERDM2,CSECT=UNKNOW
               N ,OFFSET=UNKNOWN ,ASMDATE=UNKNOWN,FMID=UNKNOWN
    
    3) Last call in RB chain is DYNALLOC.
    
    
    Additional Symptom(s) Search Keyword(s): SMSG
    

Local fix

  • Wait until SMTP has fully initialized and attempt command again.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of the IBM Communications Server                   *
    * for z/OS Version 2 Release 1 IP: SMTP                        *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * An ABEND0C4 occurred in SMS module                           *
    * IGDERDM2 when a Modify SMTP,SMSG                             *
    * command was issued before SMTP                               *
    * had fully initialized.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fix.                                                   *
    ****************************************************************
    The problem can be summarized as follows:
    1. SMTP was started.
    2. Before SMTP had finished initialization, an operator issued
    a MODIFY SMTP,SMSG command.
    3. The address of the external interrupt handler had not been
    filled in yet, so MVPIOINT took a wild branch that eventually
    lead to an ABEND0C4 in SMS module IGDERDM2.
    +-------------------------------------------------------------+
    + 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

  • MVPOCM has been changed to verify that the external interrupt
    handler address has been set before scheduling an IRB for
    MVSIOINT to process the MODIFY SMTP,SMSG command.  If it has not
    been set, MVPOCM will issue new message EZY1979I to inform the
    operator that they should try the SMSG command again later.
    
    The following documentation updates for the new message
    were included in the V2R1 IP Messages Volume 3 (EZY):
    
    EZY1979I SMTP cannot accept the MODIFY command - try again later
    
    Results: The MVS platform received a command to modify SMTP,
      but the command was not accepted because SMTP initialization
      had not completed.
    
    Example:
    
    F SMTP,SMSG,ST
    EZY1979I SMTP cannot accept the MODIFY command - try again later
    
    System Action:  SMTP continues.
    
    Operator Response:  Issue the command after SMTP initialization
      completes.
    
    User Response:  Not Applicable.
    
    System Programmer Response:  No Action Needed.
    
    Problem Determination:  Not Applicable.
    
    Source:  z/OS Communications Server TCP/IP: SMTP
    
    Module:  MVPOCM
    
    Routing Codes:  10
    
    Descriptor Codes:  12
    
    Automation:  This message is sent to the console where the
      command was entered.  Automation could be used to issue the
      MODIFY command at a later time.
    
    * Cross Reference between External and Internal Names
    EZAAA00A (MSMVP   )  EZACA01Y (MVPOCM  )
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM88514

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-06

  • Closed date

    2013-05-14

  • Last modified date

    2013-07-03

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

    PM77026

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

    UK94299

Modules/Macros

  • EZAAA00A EZACA01Y
    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R210 PSY UK94299

       UP13/06/26 P F306

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":"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:
03 July 2013