Skip to Main Content
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

Pinned ideas

PINNED Respect $HOME/.config/go/env
After adding eval $(/path/to/goz-env) in .profile, each time I log in to OMVS, I get 3 or 4 lines about $COMPILER_PATH. Can you add config to turn this off, please? Second, even if I have $HOME/.config/go/env (per XDG spec), go env says that `go` ...

All ideas

Showing 8510

Need a step by step tutorial for Unit testing with local projects

The documentation has some samples but with remote datasets. It will be helpful to have a tutorial with local projects as there is no zUnit property groups and building the testcase is different.

Support 66 levels in Unit testing

66 levels are valid COBOL definitions for working storage and linkage areas, and prevents zUnit from generating test cases for programs containing these.

Support for EXTERNAL data

zUnit should support data items declared as EXTERNAL. If a data item in COBOL is declared as EXTERNAL it can be used to pass data from a calling program to a subprogram, and therefore should be recorded as if it is a parameter. Also when calling a...

Validate playbackfile in DTR runtime

When pushing a zUnit testcase in a pipeline (and maybe other places) the playbackfile isn't validating with possible result a testcase is run forever (or until canceled). The functionality to validate the playback file is present in ZVTP and would...

make userdefined extensions for unit testing thru preferences

zUnit now only is available for a few extensions for cobol sources. As we do have a few more extensions for cobol sources, we would like to be able to add our extensions to a preference so zUnit also can act on these extensions. We are aware that ...

Support for SYSIN and ACCEPT during recording and replay

If a COBOL program performs an ACCEPT on SYSIN then its replay fails with an abend U4038. It works if a SYSIN DD is added during replay. In a pipeline build, it will be better if the Dynamic Test Runner could record and replay SYSIN DD like any o...

Currently Unit testing with IDZ 14.2.2 does not support this case: the list of files are opened in other programs..

We have tested zUnit on simple standalone batch loads however we are now trying to create test cases for individual programs (csects) with a load module. We are getting file open errors in the case where the main program has the open for the file,...

Input file with >7000 lines leads to JAVA heap issue

Large input file in zUNIT with number of lines ( > 7000 lines ) leads to issue. Need solution or best practice to work with large input files. IBM CASE: TS009275317

Support of Assembler Subprogram Calls

Currently when recording in zUnit, any subprogram calls to assembler programs are not recorded. For more complete testing of a program it would be beneficial for zUnit to also intercept and record assembler subprogram calls.

When recording the test cases, the folder should be defaulted to JCL folder and not the PROGRAM folder

Since we have a JCL folder for zUnit, when ever we do start recording, it should point to JCL folder in default, which will help developer avoid manual selection and its time consuimg as well.