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.
1. Where is the job card currently defined or expected to be defined?
-Is it stored in the property group, or are users editing it manually within the JCL or another location?
2. Can you describe what you mean by ?dynamic??
-Are you expecting support for placeholders (e.g., `@TEAMID@`, `@USERID@`) to be automatically substituted at submission time?
-If so, are these values meant to be user-specific, team-specific, or system-derived (e.g., from z/OS system symbols or user profiles)?
3. Where would the values for these dynamic fields come from?
-Would they live in the property group itself, in a centralized config file, or do you expect them to be retrieved from the host (e.g., system symbols, REXX scripts, etc.)?
4. Is this meant to support team-level standardization?
-Are you envisioning a reusable job card template across multiple developers or projects?
5. How do you currently manage job cards for different environments or teams?
-Is this request driven by a need to reduce manual editing per team, per developer, or per build environment?
6. Would a client-side substitution (prior to JCL submission) meet your needs?
-For example, having the Eclipse client expand variables based on property group-defined values before the JCL is submitted.