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 SMS
Created by Guest
Created on Dec 29, 2016

Allow SMS to process DD DUMMY

We would like to eliminate all esoterics from HCD and thus allow SMS to be the sole source for esoterics. There is at least one circumstance where this is not a transparent change and that is when using the DUMMY parameter. For example if you have an esoteric called TAPE1 defined in SMS that is not defined in HCD the following DD will work:
//DD1 DD DSN=SYS2.TAPEDSN,LABEL=(1,SL),UNIT=TAPE1

However the following DD will fail with IEF210I jobname stepname DD1 - UNIT FIELD SPECIFIES INCORRECT DEVICE NAME
//DD1 DD DUMMY,DSN=SYS2.TAPEDSN,LABEL=(1,SL),UNIT=TAPE1

This is simple enough to correct in JCL but it still represents a barrier to a seamless transition to SMS. We have already been caught by this when we eliminated one of our HCD esoterics and several jobs took JCL errors because they had DUMMY DDs setup.

Idea priority Medium
  • Guest
    Reply
    |
    Jan 1, 2017

    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 - None

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