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

Status Submitted
Workspace z/OS
Categories z/OSMF
Created by Guest
Created on Sep 23, 2025

Support Intrdr File Encoding header for all Submit Jobs requests

The z/OSMF API for submitting jobs supports a “X-IBM-Intrdr-File-Encoding” header, which has the following limitation:
> This header is effective only when the JCL for the job to be submitted is included in the HTTP request body. This header is ignored when the job to be submitted resides in a data set or UNIX file.
Source: https://www.ibm.com/docs/en/zos/3.1.0?topic=interface-submit-job

In order to submit JCaL with a custom encoding directly from a PDS member, currently the only way is to make 2 API calls - first to download JCL from the member with the desired encoding, and then to submit the body of text as a job on a PUT request with the encoding header.

Ideally this header would be supported for all Submit Jobs requests, regardless of the source of the JCL, so that only a single API call is needed.

Idea priority Low