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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Marking it as "future consideration" as we wait for response from HOGAN
We have reached out to Hogan team to see whether we can build a scanner for Hogan. We discussed all other ideas, but they all have too much complexity in them that, the final result will be lot more messy than what customers would like to use.
Reviewing it with IDz team
In response to the comment: The issue we have at the moment is the HSQLA, where DBB doesnt recognize it as a dependency for Cobol, so when it tries to get built in a Hogan environment the hogan program is looking to link the HSQLA to the cobol, but since DBB isnt correctly recognizing it, the HSQLA elements aren't where they're supposed to be, causing the build to fail.
The HSQLA file essentially just has a single activity in it, so DBB doesn't recognise it as a dependency. The idea was to try and list the HSQLA files statically as dependency's. However if DBB can be updated to recognise this then that would be even better
Currently DBB uses a parser to automagically figure out what part dependencies are. Manually creating lists is a static solution. If that list changes then someone has to update the list. Being able to parse and find dependencies means no thought or effort is required from a user.
I think before going down the path of enabling user created dependency lists we ought to spend some time understanding what shortfalls we have with the current parse and whether this current solution can be fixed so that manually created dependency lists are not required.