IBM Support

PK90945: USERKEY PROGRAM RUNS IN BASESPACE RATHER THAN SUBSPACE FOLLOWINGA CALL TO AN OPENAPI TRUE (OTHER THAN DB2 AND MQ.)

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You are using Tranaction Isolation.  You have an application
    program defined as EXECKEY(USER) and Concurrency ( Threadsafe ).
    Following a call to the CICS/TCPIP Sockets TRUE, EZACIC01 (which
    is enabled as OPENAPI,) the program runs in basespace rather
    than in subspace .
    .
    Furthermore, when you use Debug Tool and RDz to debug this
    program , the debug session hangs.  It was found that when
    Debut Tool program IBMPDSFU attempted to attach a subtask, that
    Attach failed with RC20 .  It failed because at that time,
    control of the task was on an L8 TCB and the task was running
    in basespace .    This causes the task to hang in a WAIT
    EXTERNAL out of IBMPDSFU because the attached subtask was
    going to post the task out of the wait.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Userkey program ran in basespace when   *
    *                      it should have run in subspace.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A program was running in SUBSPACE mode and made a call to an
    OPENAPI true. In this case, it caused DFHERM to issue an
    environment switch to BASESPACE which the TRUE ran in. The TRUE
    ran and returned to the application. However, no switch to the
    original environment of SUBSPACE occurred so the application
    continued in BASESPACE rather than SUBSPACE.
    Symptoms of this incorrect environment switching may present
    differently but in the reported problem, the application hung
    because it was unable to attach a subtask.
    

Problem conclusion

  • DFHERM has been modified to avoid the switch to BASESPACE in
    this case.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK90945

  • Reported component name

    CICS TS Z/OS V4

  • Reported component ID

    5655S9700

  • Reported release

    600

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-09

  • Closed date

    2009-07-28

  • Last modified date

    2009-08-03

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

    PK85198

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

    UK48726

Modules/Macros

  • DFHERM
    

Fix information

  • Fixed component name

    CICS TS Z/OS V4

  • Fixed component ID

    5655S9700

Applicable component levels

  • R600 PSY UK48726

       UP09/07/29 P F907

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:
03 August 2009