IBM Support

PK90957: LOOPING CPSM BATCH API HANGS AFTER BEING CANCELED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You have a batch CPSM API that goes into a loop.  When you
    cancel the job, it hangs.  This seems to be a timing issue
    during termination.  The wait is coming out of EYUTXEPC in the
    TERM_CHK_APIT routine.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V4R1M0 Users                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:    You have a batch CPSM API that goes  *
    *                      into a loop.  You cancel the job, but   *
    *                      it hangs, and the MVS "FORCE jobname"   *
    *                      command must be used to end the job.    *
    ****************************************************************
    * RECOMMENDATION: After applying this PTF, all CMASes, MASes   *
    *                 and WUI servers must be restarted with the   *
    *                 updated code.                                *
    *                                                              *
    *                 To restart with the updated code, the CPSM   *
    *                 Environment Service System Services (ESSS)   *
    *                 subsystem address space (EYUX410) must be    *
    *                 terminated and the CPSM EYUX subsystem End   *
    *                 of Task (EOT) exit (EYU9XEET) must be re-    *
    *                 loaded on the MVS image if a CMAS has been   *
    *                 started without the updated code, since the  *
    *                 last IPL.                                    *
    *                                                              *
    *                 This can be accomplished in either of two    *
    *                 ways:                                        *
    *                                                              *
    *                   1 - IPL the MVS Image.  This terminates    *
    *                       the ESSS and the EYUX subsystem.  When *
    *                       the first CMAS starts after the IPL,   *
    *                       the ESSS address space and the EYUX    *
    *                       subsystem will be started at the pro-  *
    *                       per level.                             *
    *                                                              *
    *                 Or:                                          *
    *                                                              *
    *                   2 - Stop all CMASes and MASes on an MVS    *
    *                       image.                                 *
    *                                                              *
    *                     - Use EYU9XENF to check that no address  *
    *                       spaces are connected to the ESSS sub-  *
    *                       system.                                *
    *                                                              *
    *                     - Use the EYU9XEUT TERMINATE function to *
    *                       stop the ESSS.                         *
    *                                                              *
    *                     - Use the EYU9XEUT RELOAD function with  *
    *                       the EOT option to reload EYU9XEET,     *
    *                       ensuring that UTILLIB specifies the    *
    *                       SEYUAUTH library updated by the PTF.   *
    *                                                              *
    *                     - Refresh LLA to ensure the updated      *
    *                       version of EYU9X410 is picked up.      *
    *                                                              *
    *                     - Restart any CMASes, MASes, and WUI     *
    *                       servers which execute on the MVS       *
    *                       image, ensuring that the updated       *
    *                       libraries are being picked up.  When   *
    *                       the first CMAS is started the ESSS     *
    *                       address space will be started at the   *
    *                       proper level.                          *
    *                                                              *
    *                 For details on EYU9XENF and the EYU9XEUT     *
    *                 TERMINATE and RELOAD functions, please       *
    *                 refer to "CICS Transaction Server for z/OS   *
    *                 Version 4 Release 1 CICSPlex SM Problem      *
    *                 Determination" (GC34-7037-00).               *
    *                                                              *
    *                 Note that each MVS image can be updated      *
    *                 separately, and systems on an MVS image      *
    *                 that have been updated can communicate       *
    *                 with systems on other MVS images that        *
    *                 have not been updated, without problem.      *
    ****************************************************************
       When an API program connects to CPSM, a control task is
    attached, whose purpose is to handle asynchronous events such
    as the completion of NOWAIT requests, or notification of the
    termination of the CMAS to which the API program is connected.
    When the API program disconnects, a signal is sent to the API
    control task from the TERMINATE PC routine, notifying it that
    the API program is disconnecting. It then waits to be POSTed
    by the control task's End-of-Task exit to disconnect from the
    authorized PC vectors and release the External Services Con-
    nection Block (XECB).
       If the job is cancelled it is possible that the API control
    task could end before the TERMINATE PC routine has sent the
    termination signal.  In this case, the ESSS Subsystem's End-of-
    Task exit, EYU9XEET, will wait indefinitely in the TERMINATE
    PC routine, to be POSTed by a task which is no longer active.
       Because the job has already been cancelled and is waiting in
    a subsystem end-of-task exit, the FORCE command must be used to
    end the job.
    

Problem conclusion

  • When the ESSS Subsystem's End-of-Task exit is entered for
    termination of the API control task, a flag is set in the XECB.
    During TERMINATE processing for the main API program's task,
    if this flag is set, the termination signal is not sent to the
    control task, and the wait for the API control task to end is
    bypassed.
    

Temporary fix

  • *********
                * HIPER *
                *********
    FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK90957

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    60M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-09

  • Closed date

    2009-09-08

  • Last modified date

    2009-10-02

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

    PK90743

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

    UK49883

Modules/Macros

  • EYURXECB EYUTXEPC EYU2XEET EYU9XEET EYU9X410
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R60M PSY UK49883

       UP09/09/12 P F909

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 October 2009