IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Planned for future release
Workspace z/OS
Categories LE
Created by Guest
Created on Feb 16, 2026

RELATED IDEAS

Split 31/64 Bit environments create 2 enclaves both think they own //SYSOUT and over-write each other when writing //SYSOUT to Disk DataSet. //SYSOUT needs to be owned by the initiating Enclave only.

With the need to go to the 64-bit Java JNI for storage reasons, three of our customers all write //SYSOUT from some jobs to Disk. From Discussions with IBM both with Tickets:
TS019872641 (COBOL) – closed - Low Severity, Question on JCL/JES //SYSOUT dd dsn=dataset limitations, and

TS019567472 (LE) – open - (COBOL V6.4) COBOL program not writing SYSOUT --> This was opened by our customer, but we have the ticket  number
also our reading of IPCS dumps showed both the 31-bit and 64-bit enclaves had their own //SYSOUT dd in their chains, corroborating IBM's findings,   and would over-write each other as the application processed in the 31-bit addressing then switched to the 64-bit COBOL 6.4 JNI to call 64-bit Java, which began another enclave and it's own //SYSOUT.

If just our company had 3 customers hitting this, there are likely others. We would like to see //SYSOUT behave as if we were either all-31 bit or all-64 bit, where one enclave owns //SYSOUT so disk-dataset based output is written.

Idea priority Low

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.