IBM Support

PK24824: WHEN PROGRAM IS ASSEMBLER AND THE SDWAINTF IS 1, THEN THE SYSTEM REGISTERS AND PSW SHOULD BE PROPAGATED TO THE TACB.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Do to the lack of "Fencing" around the Assembler environment
    the SDWAXFLG flag is from either the Linkage Stack or RB. If
    the program is Assembler and the SDWAINTF is 1, then the system
    registers and PSW should be propagated to the TACB. The most
    valuable information from the actual moment of the program
    check should be placed in easily accessible TACB block as
    opposed to the KERRD that is quite complicated to access.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All.                                         *
    ****************************************************************
    * PROBLEM DESCRIPTION: Following a program check in an         *
    *                      assembler subprogram which had issued a *
    *                      BAKR, the wrong PSW and registers are   *
    *                      recorded by the CICS exit, DFHKESTX.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An assembler subprogram which uses a BAKR instruction is called
    with a BASSM instruction.  Following a program check in the
    subprogram, the wrong PSW and registers are recorded by the CICS
    ESTAE exit, DFHKESTX.  The PSW and registers are those from the
    linkage stack entry generated by the BAKR instruction, instead
    of the PSW and registers at the time of the program check.  When
    the CICS Kernel control blocks in the dump produced at the time
    of the program check are formatted, the Kernel Error Data and
    associated PSW and registers are incorrect, as is the TACB.
    
    Additional keywords: SDWAXFLG SDWARC1 SDWARC2 SDWASRSV SDWAARSV
                         KERNEL_ERROR_DATA TASK_ENTRY RECORD_ERROR
                         DFHKERRD
    

Problem conclusion

  • DFHKESTX has been changed to use the SDWA indicators to
    establish if the program check occurred under a linkage
    stack entry created under the CICS RB.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK24824

  • 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

    2006-05-11

  • Closed date

    2006-08-29

  • Last modified date

    2006-09-05

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

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

    UK17644

Modules/Macros

  •    DFHKESTX
    

Fix information

  • Fixed component name

    CICSTS 3.1 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R400 PSY UK17644

       UP06/09/01 P F608

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:
05 September 2006