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.

Add a new idea Subscribe
Status Not under consideration
Workspace IBM Developer for z/OS
Categories z/OS Application Development
Created by Guest
Created on Nov 11, 2010

RELATED IDEAS

Use standard methods for setting JCL parameters for compilation procedures

The RDz job generation process creates overrides for many compilation procedures. For example, the DBRMDSN and DBRMMEM variables for COBOL compilation with the DB2 preprocessor and coprocessor. In one case, the values are assigned explicitly for the EXEC ELAXFCOP.

//P0000 EXEC PROC=ELAXFCOP,
// DBRMDSN=T02161A.DBRMLIB,
// DBRMMEM=COBDB2

In the case of the DB2 coprocessor, the appropriate //DBRMLIB DD statement is added to the generated JCL.

Because standard JCL // SET statements are not used, these variables cannot be used by subsequent steps for example, our customized BIND.

Idea priority High
  • Guest
    Reply
    |     Oct 26, 2018

    Thank you for taking the time to suggest an enhancement to our product. Many of our product enhancements result from feedback from our customers, so your input is always very important to us. This request for enhancement is not currently aligned with our product strategy and vision and for this reason, we will not be implementing it. Again, thank you for your suggestion and continued support.

  • 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
    |     Jan 10, 2011

    This RFE is consistent with our roadmap and is being considered for delivery within the next 2 year timeframe. Thanks.

  • Guest
    Reply
    |     Nov 12, 2010

    I would like to clarify my requirement.

    1. Rather than generating JCL override statements for DBRMLIB (DB2 coprocessor), or DBRMDSN,DBRMMEM (DB2 coprocessor), RDz should generate set statements for DBRMDSN and DBRMMEM before the first step.

    2. This would avoid the need to specifiy DBRMDSN uand DBRMMEM parameters for EXEC ELAXCFCOP

    3. The generated override for the DB2 coprocessor could then use symbol variables.

    Overall, I would imagine this is a very minor change. Indeed it would simplify and standarize the job generation process.

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.