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 Delivered
Created by Guest
Created on Oct 24, 2018

Simplify DBB user build wizard, by hiding fields containing values that don't need to be filled each time

DBB user build asks questions that are relevant to set up the user build, but these questions don't need to be in the developer's face at each user build session (on the same file or on different file). Some fields could be handled as configuration options that should be set elsewhere: not in the wizard.

(1) build script to use : on our system it will be a remote file and it will always be the same one. DBB samples lean toward having a single script as an entry point.

(2) encoding to use : on our system there's a single encoding for all files.

(3) build sandbox : there's a single sandbox for each developer.

(4) location to store logs: same as sandbox

(5) build destination HLQ : same as sandbox

(6) team HLQ : this relates to the jenkins build, and we expect users to perform user build related to the development jenkins build: it will be the same most of the time.

In the end all of these options make the user build frightening for a developer. Most of these options should be captured once, for example in Eclipse preferences. Some options could be displayed by the wizard, but as information about how the build is going to be configured (aka : user build will build in this location, using this encoding and this script. Click here if you want to change the settings).

Idea priority Medium
  • Guest
    Reply
    |
    Nov 11, 2019

    This enhancement was delivered in IBM Developer for z/OS 14.2.

  • Guest
    Reply
    |
    Dec 19, 2018

    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
    Component - z/OS Application Development
    Operating system - Linux
    Source - Client

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Development Tooling
    Product - IBM Z Development and Test Environment
    Component - Base
    Operating system - RHEL
    Source - Client