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 Usability
Created by Guest
Created on Jun 11, 2014

Resolve Copybooks Within MVS Subproject Natively

Please refer to Service request number 56700,379,000. I understand the dilemma of what to do when the copybook is found in multiple subproject datasets (based on my use case) and my expectation is if that were to occur the user would get the similar "!Warning message unable to resolve copybook reference". Otherwise, I see the following scenarios: 1) it is found in the MVS subproject and in one of the HLQ datasets defined in the property group, then the MVS dataset overrides the property group COBOL tab, 2) if it is only found in the MVS subproject and NOT in a HLQ dataset defined in the property group COBOL tab, the copybook is resolved through the existence of the MVS dataset member, or 3) if it is NOT found in the MVS subproject but exists in a HLQ dataset defined in the property group COBOL tab, the copybook is resolved through the existence of the property group.

Idea priority Medium
  • Guest
    Reply
    |
    Sep 14, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Programming Languages
    Product - Developer for System z

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Developer for System z

  • Guest
    Reply
    |
    Jun 17, 2014

    Thank you for taking the time to suggest an enhancement to our product. We believe that the existing function provides a reasonable process for accomplishing your objective since you only need to update SYSLIB in your property group if your new copybook is in a dataset not already listed in SYSLIB. Adding all your new copybooks to a "development sandbox" dataset referenced by SYSLIB would allow the RDz tooling to locate them automatically. As a result, your request for enhancement is not within our product strategy and vision and we have no plans to address your request in the near future. Again, thank you for your suggestion and continued support

  • Guest
    Reply
    |
    Jun 11, 2014

    Attachment (Use case)