Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace z/OS
Categories DFSMS VSAM
Created by Guest
Created on Apr 18, 2023

VSAM Verify to repair control blocks

If VSAM open feedback indicates improperly closed VSAM, we would like to have VSAM open to implicitly drive VSAM Verify one time and re-drive the open request. This is to be done in a fashion that application requesting OPEN is successful in the case VSAM Verify is able to repair the control blocks.

This can be provided as an option setting at system level.

Idea priority High
  • Guest
    Reply
    |
    Jul 19, 2023
    If VSAM Open determines that the last user who had the data set open for output did not close the data set normally, it will open as normal but before returning to the caller, it will issue a VERIFY. If the VERIFY is successful and the HURBA and other important fields have been corrected, it will issue the IEC161I pp62 message and set the ACBERFLG to x'76'. If the VERIFY is not successful (or was not run), it will issue the IEC161I pp56 and set the ACBERFLG to x'74'. Regardless of the results of the VERIFY, the data set is opened and control returns to the caller. The calling program can then take any specific action based on the information in the ACBERFLG. It would be very inflexible if VSAM were to assume that the caller wanted only one specific action (to close the data set and reopen) so that is why it is left to the caller to make that choice. However, that may not be what you are asking. It could be your request is more specific and you want CICVR to take that action, not VSAM. Can you please clarify your request because the CICSVR group routed the request to VSAM.
  • Guest
    Reply
    |
    May 19, 2023

    VSAM open currently will initiate a VERIFY after building the control blocks and before returning to the caller. Is there a specific scenario you are referring where you are not seeing an implicit VERIFY?

  • Guest
    Reply
    |
    May 3, 2023

    This Idea was incorrectly raised against CICSVR rather than z/OS DFSMS VSAM. I tried to transfer it and incorrectly assigned it to IDZ. Please transfer to z/OS DFSMS VSAM