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 Planned for future release
Created by Guest
Created on Jul 18, 2023

Documentation doesn't mention soft link for /usr/bin/env which seems to be needed for scripts to work properly

Having this mentioned in documentation may save a big number of hours of debugging everyone's first build process with DBB and groove. The user responsible for running dbb builds has Bash set as their default shell (configured via OMVS PROGRAM setting) since it's needed for the gitlab runner. The build process involves executing DBB_HOME/bin/groovez, which begins with "#!/bin/sh" as the interpreter in its first line. That script, in turn, calls DBB_HOME/groovy/bin/groovy, which uses "#/usr/bin/env sh" as its shebang. This is where the problem arises. Process breaks. Until we either: 

Create a soft link: /bin/env -> /usr/bin/env. 
Change the shebang in groovy/bin/groovy to: #!/bin/env sh
Change the shebang in the main groovyz script to: #!/bin/bash

It has been discussed in the GitHub IBM/DBB group that the soft link is the best solution, as it is already equired for other products like Python anyway. Please make a note on this in the documentation if this is in fact a preferred way  for dealing with this issue. 

https://github.com/IBM/dbb/issues/171

Idea priority Low