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.

Add a new idea Subscribe
Status Submitted
Workspace IBM Developer for z/OS
Categories Wazi Deploy
Created by Guest
Created on Jan 24, 2025

RELATED IDEAS

Use artifact based deployments instead of hardcoded parameters in the environment file

* non artifact related modules *

(ds_create, ds_delete, job_submit, shell_command, system_command, tso_command, template)

These modules are using the environment file for reading configurations. The developer must edit this file for each deployment and change according to needs for the actual deployment. The environment file is cosidered as "configuration" for the deployment modules so, changing it could be a responsibility of somebody else. There could be some conflicts in case of concurent developments. Also, it is hard to identify the change was applied for a certain deployment.

I suggest to change these modules to be artifact related. Each module could have an "instruction file" which sets the parameters for the module. The module then reads the artifact and executes the action using the contents.

For example:

in case of ds_create, there is yml file:

myseqds1.ds

- name: myseqds1

spec:

type: SEQ

primary_space: 8TRK

secondary_space: 4TRK

record_format: FB

record_length: 25

The deployment type ds is assigned to the ds_create module.

In git, developer creates the file myseqds1.ds, this will be added to the commit and then to the package.


Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.