IBM Support

PK43600: TOKENERR (RESP 112) IS RETURNED ON A GETNEXT CONTAINER OR STARTBROWSE CONTAINER, EVEN THOUGH THE TOKEN IS VALID.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A STARTBROWSE CONTAINER is issued, and a token is returned.
    Then a GETNEXT CONTAINER is issued with the obtained token
    and TOKENERR is returned, even though the token is valid.
    .
    This can also fail when a STARTBROWSE, GETNEXT or ENDBROWSE
    CONTAINER is issued and then a second STARTBROWSE or GETNEXT
    CONTAINER is issued.
    .
    Additional Keywords: DCIC 15840 Subroutine
    inquire_browse_context in module DFHPGCR looks to be the
    problem.  chcb_prev chcb_next chcb
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: An EXEC CICS GETNEXT CONTAINER command  *
    *                      using the browsetoken obtained by a     *
    *                      successful EXEC CICS STARTBROWSE        *
    *                      CONTAINER CHANNEL command returns a     *
    *                      TOKENERR response.                      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An EXEC CICS GETNEXT CONTAINER command abends AEZL due to a
    TOKENERR condition being returned, even though a valid
    browsetoken was obtained in an earlier EXEC CICS STARTBROWSE
    CONTAINER command. This problem will only occur when a program
    specifies more than one channel.
    Keywords: AbendAEZL
    

Problem conclusion

  • DFHPGCR has been amended such that pointer chcb_next, rather
    than chcb_prev is used to obtain the next chcb in the channel
    chain in routine inquire_browse_context.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK43600

  • Reported component name

    CICSTS 3.1 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-04-18

  • Closed date

    2007-05-03

  • Last modified date

    2007-06-01

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

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

    UK24807

Modules/Macros

  •    DESPGCR  DFHPGCR
    

Fix information

  • Fixed component name

    CICSTS 3.1 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R400 PSY UK24807

       UP07/05/09 P F705

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":"3.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":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 June 2007