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
Created by Guest
Created on Mar 30, 2018

Please change behavior of IDCAMS utilitty ALTER commands

If IDCAMS ALTER detect that backpointer to catalog points is not user intended one.
then ALTER issue some WARNING or INFORMATION message.

<User case>

<<Background>>
User used IDCAMS DELETE to delete VSAM but got below message:
IDC3009I ** VSAM CATALOG RETURN CODE IS 50 - REASON CODE IS IGG0CLFL-88
IDC0551I ** <<vsam name>> NOT DELETED

then he did IDCAMS PRINT to the VVDS which the VSAM is placed on, and confirmed that backpointer did NOT point to user intended one but wrong one.
(User intended catalog "A" but VVDS has entry of catalog "B")

This situation is described in IBM manual "DFSMS Access Method Services Commands"-"DELETE"-"SCRATCH operands"
-----------------------------------------------------
Note:
If the VVDS indicates that the data set is owned by a catalog other than that catalog identified through the usual catalog search order for DELETE, a DELETE NOSCRATCH is done against the catalog that resulted from the catalog search, and a zero return code is returned to the user
-----------------------------------------------------
So IDCAMS DELETE checks this situation.

But user did IDCAMS ALTER RENAME for this VSAM one week before DELETE,
Then IDCAMS ALTER completed without any error or warning.
It means IDCAMS ALTER don't check this situation.

I think IDCAMS ALTER should check this situation then give user to some information.

Idea priority Medium
  • Guest
    Reply
    |
    Feb 5, 2024
    This item is a valid requirement but unlikely to be given high enough priority to be placed into the product plan. If this requirement is high value, please re-open it, or open a new requirement.
  • Guest
    Reply
    |
    May 5, 2023

    It would be nice if IDCAMS ALTER did check the alias of the new target name and recatalog the dataset to the relevant target name catalog, such as with an ISPF rename. So many people get caught out by this, wondering where their datasets have disappeared to, leaving support to sort it out. Often they'll just create another dataset and leave an orphaned one which create other issues.
    But even if the newname alias points to the same catalog you can still have an issue where the new named dataset is now in the wrong Storgrp for datasets of that name. We encourage Users to COPY rather than rename datasets in place for this reason.

  • Guest
    Reply
    |
    Feb 13, 2023
    .The catalog back pointer is used only to confirm that the correct entry is being deleted. Alter does not do this check because the user has the ability to change the entry, in this case, rename it.