Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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
Categories General TM
Created by Guest
Created on May 11, 2015

Option to turn off checkpointing for GSAM files

Currently, IMS sets the DS1CPOIT flag in the Format-1 DSCB for all GSAM files used by an IMS program, such as a BMP. This flag is left on regardless of whether the program terminates normally or not, leading to many thousands of checkpoint files left in the system, even though in the vast majority of cases these files have no checkpoint value since the program can't be restarted anyway.
In order to avoid DASD management issues, DFSMShsm and DFSMSdss have included options to ignore the checkpoint flag (DS1CPOIT) while doing housekeeping such as space management or similar. This has led to an absurd situation where IMS indicates datasets are checkpointed, and DASD management outright ignores the indicator. Now, this would not be a problem if it weren't for the (theoretical) case where a program ends abnormally (thus leaving a pending restart situation), and HSM needs to migrate the dataset before a restart happens. This would mean that the checkpointed dataset is no longer valid, and a potential data corruption might ensue.

We suggest that IMS introduce an option to not leave the DS1CPOIT flag if the program terminates normally. (We leave it up to IMS development to define what constitutes 'normally', though we feel it should be along the same lines as DBRC or similar use to define a run as not-restartable.) This would give us the option to instruct HSM/DSS to not ignore the bit, and we would thus ensure data integrity.
The option could be 3-tiered:
- An IMS system option defining a default behaviour,
- An option on the PSB to override system default, and/or,
- An invocation option on DFSRRC00 to override the option for a specific run only.
We would prefer it if we could get the option in all 3 places, if possible.

Idea priority High
  • Guest
    Reply
    |
    Oct 13, 2015

    Dear Bertil Andersson:

    Thank you for submitting this IMS enhancement request.

    After a comprehensive review, we regret to inform you that we have determined that at this time this request will not be a candidate for inclusion in an upcoming release because this appears to be a defect. Hence, we have rejected this request.

    I would recommend you open PMR and describe this scenario again and reference your earlier PMR 08327,180,846, this RFE 70961 and include my name Jeff Fontaine. In the new PMR request a FIN APAR be opened to address the issue raised in this RFE because the RFE has been rejected. A FIN APAR means that IMS accepts this as a defect but due to mitigating factors the defect will not be fixed in the reported release but instead will be fixed in a future release of IMS.

    We appreciate your input to the IMS development team.

    Sincerely,
    Jeff Fontaine
    IMS Database Development lead