PK54529: TASKA INITIATES TASKB USING REQUESTSTREAM WHICH CAUSES TASKA TO HANG IN A RZCBNOTI WAIT AND TASKB TO WAIT 07/12/13 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The problem here is that TASKA has attached TASKB using a
  requeststream and sent the data to it. TASKB then runs to
  completion and sends the response back to TASKA. This send
  is done in stages so TASKB suspends on RZRSTRAN waiting for
  TASKA to be ready to receive more data. TASKA now issues a
  listen to wait for TASKB to be send back data. This gets
  notified immediately but TASKA ignores this and suspends
  on RZCBNOTI anyway. Both tasks are suspended waiting for
  each other and will remain that way.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All CICS users with PK40409 applied.         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Pipeline tasks hang with RZCBNOTI and   *
  *                      RZRSTRAN.                               *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A webservice request is received and handled by a pipeline task.
  A context switch occurs by changing the user ID or the
  transaction ID, and a new task is attached using request
  streams. The partner task runs to completion and begins to send
  its response back to the pipeline task. In doing so it suspends
  on RZRSTRAN, waiting for the pipeline task to be able to receive
  the data. When the primary task receives control, it issues a
  suspend (RZCBNOTI) to wait for partner task. So both tasks are
  now suspended waiting for each other.
  

Problem conclusion

• UK24806 UK26333
  APAR PK40409 IS IN ERROR FOR RELS 400
  Pipeline processing has been changed so that the pipeline task
  no longer suspends on RZCBNOTI if the partner task has already
  completed and is waiting to send its response back.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  PK57989 UK32466

Modules/Macros

•    DESPIIS  DESPIPM  DFHPIISC DFHPIPM
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK32466

     UP07/12/21 P F712

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.