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.
Adding an additional field to the build map artifact would require a database schema change and require all customers to upgrade their databases when moving to a new DBB version. However, you should be able to implement your solution using the existing build map design.
As with most artifacts in the DBB metadata store, the Build Map is created and populated using low-level Java APIs. This makes the build map very flexible and meets customers' requirements. To handle the scenario where the resolved PDS and the ISPF stats need to be added to the build map, customers could use the BuildMap.addInput method to add an additional input for the resolved PDS and ISPF stats information:
// Add a resolved PDS as an input
// public void addInput(String lName, String category, String path, String sourceRef, String version)
buildMap.addInput("$member", "PDS", "//'${HLQ}.COPY'", null, "$ISPFStats")
All arguments/fields in an Input are strings.
The PDS category can differentiate the resolved PDS location from the Git repository location.
The path field could be in standard dataset notation or as shown here, in Unix CP command notation.
The ISPF stats could be in any format you would like.
This should result in a build map entry with the following format:
INPUT:
lName: EPSMTCOM
category: PDS
path: //'USERID.COPY'
version: 5 2002/07/25 2002/07/25 16:28:48 USERID
This would be a separate input from the Git source file:
INPUT:
lName: EPSMTCOM
category: COPY
path: MortgageApplication/copybook/epsmtcom.cpy
source: MortgageApplication-main
version: 19c37e8fa01351f6fea5e0dc6e03284e971a1aa67