PK49248: EXECKEY(USER) PROGRAM UNDER AN ISOLATE(YES) TRANSACTION DOES NOT RUN IN A SUBSPACE FOLLOWING AN SQL CALL.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• An EXECKEY USER program running under an ISOLATE YES transaction
  ought to run in a Subspace when transaction isolation is active.
  But such a program can invalid run in basespace following an
  SQL call if during processing of that SQL call CICS invoked
  the Dynamic Plan exit.
  .
  Running in basespace like that can cause a problem when using
  Debug Tool to debug a USERKEY OPENAPI program.  The task
  being debugged hangs and then eventually times out and gets an
  abend4039 and then loops and does it all again.
  .
  Underlying the Debug Tool hang is an Attach that fails with
  RC20.  Debug Tool is trying to attach a TCB.  If that TCB had
  been successfully attached, it would have posted the task so
  that it wouldn't hang.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: A program defined as OPENAPI and        *
  *                      EXECKEY USER, in a CICS region which    *
  *                      specifies TRANISO=YES, stops running    *
  *                      in its own subspace following an SQL    *
  *                      call.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A program is defined as OPENAPI and EXECKEY USER, in a CICS
  region which specifies TRANISO=YES. This indicates that the user
  wishes the program to run in its own isolated subspace.
  After beginning execution in its own subspace, following an SQL
  call, which necessarily invokes a switch to basespace due to
  calling a DB2 dynamic plan URM exit, the program is never
  re-instated back to subspace when the SQL call returns.
  

Problem conclusion

• DFHPGLU has been amended such that the subspace environment is
  tested and stored prior to the URM call. Then, upon return from
  the URM call, using this stored environment value, the original
  subspace environment is re-instated.
  

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:

  UK33555 UK33556

Modules/Macros

•    DESPGLU  DFHPGLU
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R400 PSY UK33555

     UP08/02/12 P F802

• R500 PSY UK33556

     UP08/02/12 P F802

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.