PJ41015: VSAM INDEX FLUSH ON DISMOUNT DOES NOT WORK.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • See Problem Summary.
    

Local fix

  • na
    

Problem summary

  • APAR NUMBER:  PJ41015
    PRODUCT:  z/TPF
    FUNCTIONAL AREA:  DATA SET SUPPORT, GENERAL FILE
    SHIPPED IN PUT:  10
    
    ABSTRACT:
    VSAM indices are not properly flushed on dismount.
    
    PACKAGE CONTENTS:
    Source Segments:
    (C) base/cp/cvf3.cpy
    
    Object Only Binaries:
    None.
    
    Configuration Independent Binaries:
    None.
    
    Support Files:
    None.
    
    OTHER BINARIES TO BUILD: YES
    (C) <sys>/obj/ccvfac.o
    (C) <sys>/load/CPS0.so
    
    COMMENTS:
    When a virtual storage access method (VSAM) dataset is
    dismounted all BCAs belonging to this dataset are to be removed
    from VFA. Routine CVF3FLVSAM loops through all BCAs and
    invalidates any with an index matching the input VSAM dataset.
    CVF3FLVSAM is invoked properly, but is not finding any matching
    VSAM indicies in the BCAs.
    
    When a BCA is allocated it is populated with the 8-byte FARF
    address from the IOB (MIOXSON) and, if possible, the same value
    occupies the 4-byte FARF address area in the BCA. When a BCA is
    allocated for GDS purposes there is no FARF address (MIOXSON is
    zero); the GDS index is in field MIOMCHR of the IOB. This means
    a VSAM record can be put into VFA, but the index saved to BCAFA
    is zero. When a VSAM dataset is dismounted the loop finds no
    matching index and so all VSAM records still reside in VFA
    after the dismount completes. VSAM BCAs must be populated with
    the VSAM dataset index rather than a FARF address of zeroes.
    

Problem conclusion

  • SOLUTION:
    Copy member cvf3.cpy of CSECT CCVFAC was updated, before label
    CVF3AL22A, to populate a VSAM BCA with information from field
    MIOMCHR of the IOB rather than MIOXSON. This change will allow
    a GDS BCA to have valid information in it so that when a VSAM
    dismount occurs the related BCAs will be invalidated.
    
    COREQS: NO
    None.
    
    MIGRATION CONSIDERATIONS: NO
    None.
    
    BUILD COMMANDS AND INSTRUCTIONS: YES
    #maketpf commands for linux
    maketpf -f CPS0 ccvfac.o
    maketpf CPS0 link
    
    UPDATED INFORMATION UNITS: NO
    None.
    
    See your IBM representative if you need additional information.
    
    DOWNLOAD INSTRUCTIONS:
    http://www.ibm.com/software/htp/tpf/maint/maintztpf.html
    
    APAR URL:
    http://www.ibm.com/software/htp/tpf/ztpfmaint/put10/PJ41015.htm
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ41015

  • Reported component name

    Z/TPF

  • Reported component ID

    5748T1501

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-22

  • Closed date

    2013-03-04

  • Last modified date

    2013-03-04

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

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

Fix information

  • Fixed component name

    Z/TPF

  • Fixed component ID

    5748T1501

Applicable component levels

  • R110 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

TPF
z/TPF

Software version:

110

Reference #:

PJ41015

Modified date:

2013-03-04

Translate my page

Machine Translation

Content navigation