IBM Support

PM39961: ESDS AUTOJOURNAL WRITE-ADD-COMPLETE RECORDS OUT OF RBA SEQUENCE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Files have been defined with JNLADD as AFTER. This means that
    FCTJWAC is set, but not FCTJWA, which would indicate
    autojournalling before the VSAM call rather than after it. Code
    in DFHFCVS will acquire the ESDS write lock if either FCTBACKO
    or FCTJWA are set on. Since neither are set currently, we do not
    get the write lock around the calls to VSAM and the LG domain,
    and hence they are not treated as a serialised operation. This
    allows for races between tasks and the potential for occasional
    autojournal after images to be written in opposing order within
    a log block.
    Additional Keyword(s) : RBA , RBARPT
    KIXREVEPH
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION: Autojournal write add complete records  *
    *                      may be out of sequence with writes to   *
    *                      an ESDS.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    On a busy system, it is possible for CICS tasks to interleave
    between calls to write to a non-recoverable ESDS file, and the
    subsequent calls to journal the write add complete autojournal
    log record for the write operation. This can lead to the
    ESDS RBAs being autojournalled out of the order in which
    records were written to the file. It requires write-add-complete
    autojournalling to be defined without write-add journalling
    and/or recoverable logging as well.
    KEYWORDS: FCTJWAC
    

Problem conclusion

  • DFHFCVS has been changed to acquire the ESDS write lock enq for
    the duration of the request to write to VSAM and then journal
    the write-add-complete autojournal record. This matches the
    existing behaviour for write-add journalling and recovery
    (backout) logging.
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PM39961

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-05-25

  • Closed date

    2011-06-29

  • Last modified date

    2011-08-01

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

    PM39862

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

    UK69193

Modules/Macros

  •    DFHFCVS
    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R500 PSY UK69193

       UP11/07/07 P F107

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

Document Information

Modified date:
01 August 2011