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 Future consideration
Workspace z/OS
Created by Guest
Created on Oct 5, 2022

Add PROC parameter/variable to ACBJBAOB in SYS1.SACBCNTL for ISPF data set name HLQ

When using Naviquest to generate a job, it will generate a JCL job stream that contains a JCLLIB statement that points to SYS1.SACBCNTL and an EXEC statement for a PROC located in that data set (ACBJBAOB). There are a few parameters/variables that the user needs to fill in to make the job function, but the names of the ISPF data sets are hard-coded to the IBM default HLQ of "ISP". Originally, all of the IBM-supplied z/OS data sets, including the ISPF data sets were named with a HLQ of "SYS1". At some point, IBM changed that to "ISP", but provided an installation option to change the HLQ for any z/OS data set to something else, like "SYS1" and that's what we did. So all of our ISPF data sets have a data set HLQ of "SYS1". Unfortunately, this causes the Naviquest-generated JCL to fail when submitted, even after the user has updated all of the available PROC parameters since the HLQ for all of the ISP data sets are hard-coded to "ISP". In order to make this work, the user must not only copy the PROC from SYS1.SACBCNTL into another data set and update the ISPF data set names, the user must also update the JCLLIB statement to point to the non-IBM-supplied data set containing the updated PROC. This also adds complexity in that the user must re-copy and update the PROC whenever IBM updates the PROC in SYS1.SACBCNTL. It would be helpful and provide additional usability if IBM would add a PROC parameter/variable for the ISPF data set name HLQ so that the user would only have to update the PROC parameters supplied by IBM at the time the job is generated/submitted and not have to maintain a local copy of the PROC with the ISPF data set name updates. The default HLQ as supplied by IBM could remain "ISP", but allowing the ISPF data set name HLQ override would make this so much easier to manage/maintain.
Idea priority Low