Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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.

ADD A NEW IDEA

Core OS

Showing 120

spawn() - Don't check "max active" of job queue and controlled end of subsystem for spawn() jobs (BCI)

Spawn jobs (BCI) are handled like normal submitted jobs. This mean that the current job queue needs to have enough "max active jobs" left to start a BCI job. In my eyes the spwan() mechanism should always starts the requested jobs and ignore the "...
almost 5 years ago in IBM i / Core OS 1 Not under consideration

Show active NWSD jobs that have an NWSSTG space in an IASP under the WRKASPJOB command

If an active Network Server Description (NWSD) has a linked Network Server Storage space (NWSSTG) in an available IASP, attempting to vary off the IASP or perform a PowerHA switch will fail with CPAB8E6 'device xxx cannot be varied off at this tim...
about 4 years ago in IBM i / Core OS 2 Is a defect

System tables to use date / time fields instead of character fields in job format

Current IBM supplied output files, such as QADSPOBJ, that are use as templates for associated system commands store dates in 2 character fields and times in single character fields. Given the power of Db2 for i and the availability of date / time...
over 2 years ago in IBM i / Core OS 2 Future consideration

Remove obsolete options from CRTNWSD and CRTNWSSTG

Many of the options on CRTNWSD and CRTNWSSTG are no longer viable. IBM hasn't supported iSCSI since 2016. Starting with the release after 7.5 they should limit it to options currently supported. I would suggest defaults of CRTNWSD TYPE(*GUEST) CRT...
almost 2 years ago in IBM i / Core OS 5 Not under consideration

Create an "Get Current Library Name" API in the spirit of Qp0wGetJobID

The current API named QWCRTVCA works okay, but in those times when you only need the current library (*CURLIB) for something, setting up the parameters and calling QWCRTVCA is far too verbose and complex. Please create a new simplified API to retu...
11 months ago in IBM i / Core OS 1 Not under consideration

QGYOLOBJ does not return Information_Status = 'L' value and it should

The QGYOLOBJ has key 201 as well as a base header that includes the same information as key 201. However, that field, "Information_Status" or Key 201 never includes the 'L' flag (locked). Instead it returns blanks when an object is locked. So eith...
11 months ago in IBM i / Core OS 4 Not under consideration

Change QUSRUSAT to work with LOCKED User Space Objects

When using the QUSRUSAT (Retrieve user space attributes) API, the API hangs/waits when the *USRSPC is *EXCL or *EXCLRD locked by another process. However since this is a read-only API, it should NOT wait. Other APIs, like DSPOBJD, QUSROBJD, etc. d...
11 months ago in IBM i / Core OS 4 Not under consideration

Option to have full usage history log of an object

Currently there are only 2 attributes of usage info for an object: Last used date Days used count 1. Last used date gives only the date used, not the time used.2. "Days used count" does not give us which days it was used.3. We do not know which us...
over 7 years ago in IBM i / Core OS 2 Not under consideration

Advanced Job Scheduler - Report by User

IBM Advanced Job Scheduler DSPJOBJS Field Options. New Feature: Adding the "User field" from the submission information section in an entry. Having an option to determine if a specific user profile is being used in an existing job scheduler entry....
almost 7 years ago in IBM i / Core OS 2 Not under consideration

ENDJOB OPTION(*IMMED) considered harmful

ENDJOB OPTION(*IMMED) has outlived it's usefulness. Modern code contains more subtle locking then in days past & often has exit handlers to perform cleanup. This is true of both client & IBM code (I'm looking at you, SQE). End *IMMED ends ...
about 7 years ago in IBM i / Core OS 5 Not under consideration