Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Workspace QMF for z/OS
Created by Guest
Created on Feb 24, 2022

Setting APPLCOMPAT at BIND of QMF packages

We apply service to QMF for TSO. That includes running DSQ1BPKG to bind packages. All packages are bound with APPLCOMPAT(V11R1) although we have set DSNZPARM APPLCOMPAT=V12R1M504.

The APPLCOMAT parameter for the BIND is set by DSQ1BPKO and there is no way to set the value other than changing the REXX code. We do not want QMF packages to use that low APPLCOMPAT as it will allow users to create Db2 objects that are deprecated and stop them from using new features. As of now we have to rebind the packages directly after binding them to set the desired APPLCOMPAT.

Editing a REXX program is always a risk as you cannot guarantee that something that should not be changed is.

The APPLCOMPAT value for the BIND PACKAGE should be controlled by a new parameter in DSQ1DEFS or by the DSNZPARM setting. An idea would be to always use a parameter in DSQ1DEFS and let a blank value for that prameter mean that the DSNZPARM value should be used.

Needed By Quarter