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.

Add a new idea Subscribe
Status Not under consideration
Workspace z/OS
Categories DFSMS SMS
Created by Guest
Created on Jun 25, 2019

RELATED IDEAS

Fail request to encrypt when no enctyption is done (TAPE)

When we request a dataset to be encrypted (allocation in extended format and keylabel) on DASD SMS issues messages indicating the dataset was encrypted, however, If we request a new dataset with the same characteristics that goes to VTS (tape), even though it has keylabel and extended format coded , the dataset is created but not encrypted, we know extended format (or dsntype=) is not valid for TAPE but we expected the operation to fail. The system misled us to think we were able to encrypt the dataset. A LISTC command reveals the encryption bit is OFF. Would you please create a mechanism (either fail the job or return something else than RC=0) to get the user's attention ?
Thanks

Idea priority High
  • Guest
    Reply
    |     Feb 10, 2022

    Since DSNTYPE=EXTPREF | EXTREQ is not applicable to TAPE, it appears that the ACS routines have redirected your data set allocation to TAPE. We think you have a solution today through your ACS routine logic to decide if you want to fail the allocation in this case. That is, &DSNTYPE and &DSKEYLABEL are available in the ACS routine. You may add logic to fail the data set allocation when your ACS routine logic determines whether the data set allocation goes to DASD or TAPE. If you don't want to fail the allocation, make sure your ACS routine directs your allocation to DASD.

    This solution is available. So, please let us know if that satisfies your need.

    The concern is that we don't want SMS to fail the request if the intention of the ACS routine logic is to redirect the allocation to TAPE. Such a change could impact other clients.

  • Guest
    Reply
    |     Jun 28, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - DFSMS SMS
    Operating system - IBM z/OS
    Source - Client

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - ICSF
    Operating system - IBM z/OS
    Source - Client

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.