Recently we've had a few customers that have upgraded to V7R2 and experiencing some odd results with jobs "hanging" and not ending like they should

For example, when using MAILTOOL to send an email (even using MAILTOOL Plus) the first call to MAILTOOL on a new job seems to hang at the end for a minute or more.  The logs show that things are going great, but it's almost like before the program ends it just sits there for a long amount of time.

All subsequent calls for the job work just fine.

In working with a customer we were able to get picture of the call stack when the job was "hanging" which looked like the following:

5770SS1 V7R2M0 140418                      Display Job                                          8/03/15  8:50:49         Page   1
 Job . . . :   OCPAPZD1     User . . . :   OCPAPZ        Number . . . . :   006117
                                               Job Call Stack
 Thread  . :   00000003
                                                                                                    Module or              Ctl
 Type Program                 Statement Identifiers    Instruction      Activation Group            Expanded Type          Bdy
      QCMD       QSYS                                              0519 *DFTACTGRP 0000000000000001                         Y
      QUICMENU   QSYS                                              00C1 *DFTACTGRP 0000000000000001                         N
    1 QUIMNDRV   QSYS                                              0D7E *DFTACTGRP 0000000000000001                         N
    2 QCMD       QSYS                                              01C8 *DFTACTGRP 0000000000000001                         N
      QCATRS     QSYS                                              015E *DFTACTGRP 0000000000000001                         N
      QLEIT      QSYS         92                                        *DFTACTGRP 0000000000000001 QLEIT      QBUILDSS1    Y
         Procedure: Q LE sinit_processor
      QLEIT      QSYS         21                                        *DFTACTGRP 0000000000000001 QLEIT      QBUILDSS1    N
         Procedure: itl_callInit__FPV12ITL_COM_AREA
      QTMSUTL72  QTCP                                                   *DFTACTGRP 0000000000000001 QTMSUSR    QBUILDTC1    N
         Procedure: __sinit80000000__tmp_CC__VakMa_qtmsusr_C_380077184__Fv
      QTMSUTL72  QTCP         76                                        *DFTACTGRP 0000000000000001 QTMSUSR    QBUILDTC1    N
         Procedure: __ct__12QTMSUserFileFv
      QTMSUTL72  QTCP         11                                        *DFTACTGRP 0000000000000001 QTMSUSR    QBUILDTC1    N
         Procedure: read__12QTMSUserFileFv
      QTMSUTL72  QTCP         13                                        *DFTACTGRP 0000000000000001 QTMSUSR    QBUILDTC1    N
         Procedure: makeLock__FPc
      QTMSUTL72  QTCP         3                                         *DFTACTGRP 0000000000000001 QTMSUSR    QBUILDTC1    N
         Procedure: select_sleep__FiT1
      QP0LLIB1   QSYS         9                                         *DFTACTGRP 0000000000000001 QP0LLIB1   QBUILDSS1    N
         Procedure: select
                          * * * * *  E N D  O F  L I S T I N G  * * * * *

Using this information we were able to track down the following that solves the issue using IBM's PTF Search Page:

http://www-01.ibm.com/support/docview.wss?uid=nas27bb08ca208bf7c9f86257e000041ebef

This page leads us to the following PTF (SI57421):

http://www-01.ibm.com/support/docview.wss?uid=nas36cd29f4bc016604886257e930079376f

We've received verification from the one customer that this does in deed solve the issue.  The customer in this case was using MAILTOOL Plus which should totally bypass all of IBM's SMTP and MSF processing.  The PTF description claims this is for applications that use the IBM SMTP email APIs, which MAILTOOL Plus certainly does not.  So, the fix fix something else as well.

Any questions, feel free to contact us!