IBM Support

PM86872: ALLOW U240 TIMEOUT FOR LONG RUNNING EXTERNAL SUBSYSTEM CALLS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • This service provides the ability to allow an ABENDU0240 Timeout
    condition to be issued to terminate IMS applications that are in
    long running External Subsystem calls.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: ALL IMS V13 Customers using IMS Timing       *
    *                 Services and connecting to External          *
    *                 Subsystems.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: Long running calls to External          *
    *                      Subsystems from application programs    *
    *                      running in IMS dependent regions do not *
    *                      receive ABENDU240 when using IMS Timing *
    *                      Services.                               *
    ****************************************************************
    * RECOMMENDATION: INSTALL CORRECTIVE SERVICE FOR APAR/PTF      *
    ****************************************************************
    Application programs running in IMS dependent regions that are
    using the IMS Timing Services (STIMER= parameter on the
    dependent region start up) may not be terminated with ABENDU240
    while in a long running call to an External Subsystem.
    

Problem conclusion

Temporary fix

Comments

  • ABENDU240 will now be enforced in IMS dependent regions that
    are running in an External Subsystem (ESS) when time expires
    using IMS Timing Services.
    
    IMS timing is established in BMP Regions using CPUTIME= and
    the STIMER= parameters on the BMP startup.
    
    MPP regions establish timing using the STIMER= parameter on
    the MPP startup and the PROCLIM= parameter of the TRANSACT
    macro for the transaction being processed by the MPP.
    
    Prior to this change, ABENDU240 was delayed until after the
    External Subsystem returned to IMS. Now when the Timeout
    routines detect processing in an ESS, they will schedule
    ABENDU240.
    
    It should be noted:
    IMS establishes a time limit using the STIMER macro and the
    TASK parameter to indicate that the time interval is only
    decreased when the associated task is running. Any ESS that
    WAITs or SUSPENDs the IMS dependent region will therefore not
    decrease the time interval during these events and will not
    drive STIMER exit routines to issue abends.
    
    U240 U0240 ABENDU0240 ABENDU240
    

APAR Information

  • APAR number

    PM86872

  • Reported component name

    IMS V13

  • Reported component ID

    5635A0400

  • Reported release

    300

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2013-04-11

  • Closed date

    2013-05-10

  • Last modified date

    2013-10-04

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

    PM81063

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

    UK94219

Modules/Macros

  •    DBFHGU10 DFSECP10 DFSESPR0 DFSPCC20 DFSPCJB0
    DFSPCJM0 PARMBLK
    

Fix information

  • Fixed component name

    IMS V13

  • Fixed component ID

    5635A0400

Applicable component levels

  • R300 PSY UK94219

       UP13/05/14 P F305

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"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"300","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
14 December 2020