IBM Support

PM65357: SR HUNG AFTER STOP ISSUED, CANCEL OF CR NEEDS FORCE TO TERMINATE SR

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • After issuing a STOP to the server the SR does not terminate an
    d is hung in Crossmemory PC to the CR after the CR is cancelled
    the SR cannot be cancelled and FORCE must be used to terminate
    the SR.
     The CR ASID can be seen in the Linkage Stack as the ASID for
    the PC call. It is in the TARG field as the first 2 bytes or in
    the PC table from the summ format output.
    
    For the last thread in the TCB Summary table of the hung asid in
    this
    case the SR.
    
    LINKAGE STACK ENTRY  01  LSED: 7EB05138
      LSE: 7EB05018
         GENERAL PURPOSE REGISTER VALUES
         ~~~omitted~~~
         ACCESS REGISTER VALUES
         ~~~omitted~~~
         PSW...... 07041000  80000000 PSWE..... 00000000  0116221E
         TARG..... 01F20B37  0001AD11 MSTA..... 00000000  00000000
                   ^^^^ = CR asid in crossmemory.
         TYPE..... 0D
    
    LINKAGE STACK ENTRY  02  LSED: 7EB05260
      LSE: 7EB05140
         GENERAL PURPOSE REGISTER VALUES
         ~~~omitted~~~
         ACCESS REGISTER VALUES
         ~~~omitted~~~
         PSW...... 07241000  80000000 PSWE..... 00000000  27F76006
         TARG..... 00000000  0000030D MSTA..... 00000000  00000000
         TYPE..... 0D
    ...
       PSWE address 27F76006 is found to be BBOTRPCX, issued a wait.
       Problem is in this case the CR is not running anymore.
    

Local fix

  • FORCE can be used to terminate the SR that is hung.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: After stopping and canceling the        *
    *                      server, the servant does not            *
    *                      terminate.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Context services invoked a Websphere PC that space switched to
    the controller. The PC queues a piece of work and waits on an
    ECB for the work to complete. When the controller is canceled
    while the PC is waiting on the ECB, the ECB is never posted and
    the servant does not go down. First linkage stack
    entry shows CTXCEMGR+0FCE PCed to Websphere.
    

Problem conclusion

  • Changed the code to use pause elements instead of an ECB so the
    controller will be the owner of the pause element and the
    paused servant thread will be released when the controller
    terminates.
    
    APAR PM65357 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.27 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM65357

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-23

  • Closed date

    2012-08-27

  • Last modified date

    2013-01-02

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

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

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server for z/OS
General

Software version: 7.0

Reference #: PM65357

Modified date: 02 January 2013