IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Sterling Transformation Extender
Categories Compliance
Created by Guest
Created on Jan 23, 2026

RELATED IDEAS

Single Version for ITX installation

With relation to : ITX-I-396 , to get the version of ITX , we use dtxver command.

This command doesn't provide a version of the installation. It provides a version of each file in the directory it's run from.

This is again a massive SDLC, compliance and operational risk multiplier.

Rather than the product exposing a single authoritative version that we can use to track changes, it behaves like a loose collection of binaries so it's a no longer controlled software release. That breaks every modern expectation of software governance.


We want the product to have:

  1. one version number

  2. one build id

  3. one release artefact


Again , it becomes impossible to reproduce a known state

Environment drift is bound to occur


Our change control function expects :
1. a versioned artifact.

  1. evidence of testing of that version

  2. evidence that the same version went to production

This accordingly breaks SOX traceability , PCI-DSS change management , ISO 27001 configuration control and internal audit expectations.

We need to have a single version for the installation to work in alignment with the other idea above.


What is your industry? Banking
How will this idea be used?

To control patch releases for the product

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.