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

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Created by Guest
Created on Oct 3, 2022

To change PROCESS library FB80 requirement

Scenario: CD transmissions between z/OS and Windows or Linux.

Large Windows and Unix FileNames have to be constructed via concatenation of multiple tokens (strings and symbols).

The reason is the PROCESS library is required to be RECFM=FB LRECL=80 (and cols 73-80 are ignored).

We’ve opened a PMR and Support has confirmed that “nothing has changed in the latest version and hence the concatenation of the symbols is still required."

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

The PROCESS library format should be more flexible in order to avoid a crazy deconstruction and reconstruction in large path+filenames. If large path+filenames have blanks inside of them, the complexity increases a lot.

If the invocation engine of the transmissions is running in middelware, it should be able to send the entire invocation process up to 255 characters. Nowadays, the requirement of max 72 characters is outdated.