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.

Status Not under consideration
Created by Guest
Created on May 15, 2025

Permissive mode for JZOS Fields

JZOS fields throw exceptions on their input values holding invalid data (e.g. Packed Decimal fields with > 0x9 digit nibbles or invalid sign codes); COBOL programs, on the other hand, don't always store valid values in their fields.


Could we add a "permissive mode" to applicable JZOS fields that always returns a value rather than throwing an exception when provided with invalid input? The returned value may be undefined (i.e. behaviour is deliberately implementation defined and undocumented, such that clients may not rely on a fixed value). The alternative is doing some tricky bit-fiddling code before the JZOS Field call, or (possibly extensive) client-side COBOL modifications.

Idea priority Medium
  • Guest
    Aug 7, 2025
    .Closing, as per requester.