IBM Support

PK07246: ABEND0C4 AKEA HAS OCCURRED AT OFFSET X'0ECC' IN MODULE DFHFCFR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You get a DFHFC0001 An abend (code 0C4/AKEA) has occurred at
    offset X'0ECC' in module DFHFCFR on a Store (ST 5090 800C)
    instruction with register8 (R8) invalid.  You see this when you
    do an EXEC CICS READ request for a DLI database issued under the
    CECI transaction.  Reg8 is loaded from the FCTE +'54' but the
    FCTE for a DLI database and is only x'1C' bytes long.
      Subsequent abends are abend 0C4's in DFHFCFR +X'0F58' and
    DFHFCRM + X'0884'.  Also a DFHRM0101 Severe error CODE X'05' has
    occured in module DFHSPP.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Module DFHFCFR does not check           *
    *                      File Control API requests to see if     *
    *                      they are invalid DLI file requests,     *
    *                      which leads to unpredictable results.   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For File Control API requests no checking is done to make sure
    that the file specified by the application is a valid file type.
    Consequently a DLI database name can be incorrectly supplied by
    the user and no checking is performed to disallow this
    leading to undefined results. This is because FCT entries can
    include DLI files, but the length of the FCTE is smaller.
    Unpredictable results occur when DFHFCFR attempts to reference
    fields beyond the length of the DLI FCT entry.
    
    Additional keywords: FCTDSDLII msgDFHRM0101 RM0101
                         msgDFHFC0001 FC0001 S0C4 abendS0C4
    

Problem conclusion

  • DFHFCFR now checks that the supplied file is not a DLI file
    and if it is it exits with an invalid_file_type exception.
    This leads to DFHFCEI returning an INVREQ with a new RESP2
    of 49 which corresponds to an invalid file type being
    specified on the API request.
    
    In User's Handbook for CICS Transaction Server for VSE 4.1
    (SX33-6101-00), in chapter 7 "EXEC Interface Block (EIB)",
    under the "RESP2 values and their meanings" section,
    under the following commands add a new INVREQ RESP2 value:
    
    Under the "delete" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to delete a file that is an invalid file
    type
    
    --
    
    Under the "endbr" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to browse a file that is an invalid file
    type
    
    --
    
    Under the "read" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to read a file that is an invalid file
    type
    
    --
    
    Under the "readnext" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to browse a file that is an invalid file
    type
    
    --
    
    Under the "readprev" command, add the following new INVREQ RESP2
    and meaning:
    
    49 An attempt was made to browse a file that is an invalid file
    type
    
    --
    
    Under the "resetbr" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to browse a file of invalid file type
    
    --
    
    Under the "rewrite" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to rewrite to a file that is an invalid
    file type
    
    --
    
    Under the "startbr" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to browse a file that is an invalid file
    type
    
    --
    
    Under the "unlock" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to unlock a file that is an invalid file
    type
    
    --
    
    Under the "write" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to write to a file that is an invalid
    file type
    
    --------------
    
    In the Application Programming Reference for CICS Transaction
    Server for VSE 4.1 manual (SC33-1658-02), in chapter 1 "CICS
    API Commands" for each of the following commands, under the
    "Conditions" section and "INVREQ" subsection add the following
    RESP2 value:
    
    For the "delete" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to delete a file that is an invalid file
    type
    
    --
    
    For the "endbr" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to browse a file that is an invalid file
    type
    
    --
    
    For the "read" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to read a file that is an invalid file
    type
    
    --
    
    For the "readnext" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to browse a file that is an invalid file
    type
    
    --
    
    For the "readprev" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to browse a file that is an invalid file
    type
    
    --
    
    For the "resetbr" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to browse a file that is an invalid file
    type
    
    --
    
    For the "rewrite" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to rewrite to a file that is an invalid
    file type
    
    --
    
    For the "startbr" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to browse a file that is an invalid file
    type
    
    --
    
    For the "unlock" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to unlock a file that is an invalid file
    type
    
    --
    
    For the "write" command, add the following new INVREQ RESP2
    value and meaning:
    
    49 An attempt was made to write to a file that is an invalid
    file type
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK07246

  • Reported component name

    CICSTS FOR VSE

  • Reported component ID

    564805400

  • Reported release

    B0P

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-06-13

  • Closed date

    2005-07-28

  • Last modified date

    2005-11-15

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

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

    UK05865

Modules/Macros

  •    DFHFCEDS DFHFCEI  DFHFCEPS DFHFCFR  DFHFCFRA
    DFHFCFRM DFHFCFRR DFHFCFRT
    

Publications Referenced
SC33165802SX33610100   

Fix information

  • Fixed component name

    CICSTS FOR VSE

  • Fixed component ID

    564805400

Applicable component levels

  • RB0P PSY UK05865

       UP05/08/03 P E311

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":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.1.1","Edition":""}]

Document Information

Modified date:
15 November 2005