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

Clear

Ideas

    Showing 72 of 9153

    Need support for migrated dataset during DEPLOY_MODULES/UPDATE/MEMBER_COPY phase

    When Wazi Deploy tries to copy to a dataset that has been migrated, it fails with an error in ZOAU dtouch which doesn't support migrated datasets: stderr_response: IKJ56893I DATA SET BUILD.PDSE.LOAD NOT ALLOCATED+ IGD17101I DATA SET BUILD.PDSE.LOA...
    2 months ago in IBM Developer for z/OS / Wazi Deploy 1 Future consideration

    Perform Batch Reanalysis on FA Originating LPAR in SYSPLEX

    This idea would benefit all users who run Fault Analyzer in a sysplex environment, use Fault History Views that cover history files from different LPARs in said sysplex, and have LPAR specific dependencies where running the batch reanalysis on an ...
    24 days ago in Fault Analyzer for z/OS 0

    Add a link between the artifact and the step result in the evidence file

    The step_result field in the evidence file for the MEMBER_COPY, SEQUENTIAL_COPY, MEMBER_ARCHIVE and SEQUENTIAL_ARCHIVE steps currently don’t include a field that represent the element being deployed. It only appears as part of the copy command. We...
    about 1 month ago in IBM Developer for z/OS / Wazi Deploy 0 Future consideration

    Generate the default report as part of wazideploy-deploy and the Ansible module

    Wazi Deploy comes with predefined reports for a single deployment: https://www.ibm.com/docs/en/developer-for-zos/17.0.x?topic=analysis-predefined-queries-in-product Instead of dedicating an extra step in the pipeline script/configuration for the r...
    3 months ago in IBM Developer for z/OS / Wazi Deploy 0 Future consideration

    Default Application Manifest extension for DBB builds in Wazi Deploy Packager

    Wazi Deploy packager (https://www.ibm.com/docs/en/developer-for-zos/17.0.x?topic=commands-wazi-deploy-packager-command) comes with an extension option to amend information into the application manifest file. I would like to see a default extension...
    4 months ago in IBM Developer for z/OS / Wazi Deploy 0 Planned for future release

    Introduce Wazi Deploy Config and Work directories

    Wazi Deploy currently requires users to define their own strategy to maintain deployment configurations and work directories. I would like to see a simplified approach leveraging standard config and work directories: Maintain a configuration direc...
    4 months ago in IBM Developer for z/OS / Wazi Deploy 0 Future consideration

    Consistent variables names for building blocks for Ansible and Python translator

    The configuration of the existing building blocks make use of different variable names (depending on the building block). This should be consolidated by deprecating the old names and move to consistent variable names across both translators.
    4 months ago in IBM Developer for z/OS / Wazi Deploy 0 Future consideration

    Improve documentation of data available in jinja2 templates

    We use jinja2 templates to generate JCL submited by job_submit templates. We often need to loop trough the artifacts and generate jcl. For us it is not clear what data wazi provides that can we can exploit in the templates. there is a note on this...
    5 months ago in IBM Developer for z/OS / Wazi Deploy 0 Future consideration

    Load evidences into a Database

    In our environment we deploy to multiple sysplexes. We would like to store the evidence files in a central databse (e.g. DB2)We would like to get an option to load the evidence files into a database so that we can centrally query all deployments. ...
    5 months ago in IBM Developer for z/OS / Wazi Deploy 0 Future consideration

    Consistency about of Jinja2 template between Ansible and Python translator

    On the python translator approach, it requires to reference the variable from a conditional deployment via the "environment" dict. In Ansible, this is different - variables can be accessed directly by referencing it's name. The documentation outli...
    5 months ago in IBM Developer for z/OS / Wazi Deploy 0 Planned for future release

    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.