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.

ADD A NEW IDEA

USS

Showing 102

Identify top users in BPXI039I message

The BPXI039I message identifies the resource shortage, but there is no easy way to identify the which user(s) are contributing to the shortage. In PMR#84352,L6Q,000 - the resource was MAXMMAPAREA -- our normal high water mark is ~4,000, but all of...
almost 8 years ago in z/OS / USS 1 Future consideration

Provide more granular control over the maximum number of processes limits

Currently, the maximum number of processes is controlled by the MAXPROCSYS value in BPXPRMxx. There are warnings not to set this value too high as each process has the potential to consume its own address space. This means that MAXPROCSYS should n...
about 1 year ago in z/OS / USS 1 Not under consideration

Allow /usr/sbin/chmount to be able to change SETUID/NOSETUID dynamically

At the moment there is no dynamic way of switching between SETUID and NOSETUID using /usr/sbin/chmount. If you need to switch between these two mode it requires an umount/mount of the file system and potentially an outage of the application using ...
almost 7 years ago in z/OS / USS 1 Future consideration

e-poll/io_uring support

e-poll or the more modern io_uring support is essential in USS for modern programming environments like node-js and Go language
almost 5 years ago in z/OS / USS 1 Future consideration

Use SHR-ENQs when copying with OGET / cp from USS-files to Data set Members

When copying USS files to Members of PDS oder PDS/E data sets an exclusive data set enqueue is being used. So when we try to copy a file to a member the copy operation fails if there is any enqueue on the target data set, even if the member that i...
almost 3 years ago in z/OS / USS 0 Future consideration

Healthcheck for CPU consuming remaining USS subprocess

There is no internal instrument of the operating system which detects and terminates processes as described in the use case. We received a user modified health check which solves the described lack. It would be good if it becomes part of the offic...
over 5 years ago in z/OS / USS 2 Future consideration

Improvement to BPX SYNTAXCHECK (z/OS v2r5)

As requested in Case TS011449479, I suggest that BPX SYNTAXCHECK functionality include validation of path. Test on a 2.5 system where the leading '/' was missing from a mount path: EDIT SYS1.PARMLIB(BPXPRMDG) MOUNT FILESYSTEM('ZOS25.ETC.ZFS')TYPE(...
almost 2 years ago in z/OS / USS 0 Future consideration

Add USERID/JOBNAME to USS BPXO058I + BPXF274I msgs

This request is to add userid/jobname to the USS mount failure message (BPXF274I) and the output of D OMVS,MF (BPXO058I). Mount failure message in SYSLOG: BPXF274I FILE SYSTEM OMVS.ZFS.SOMEFS 031 FAILED TO MOUNT. RETURN CODE = 00000079, REASON COD...
about 2 years ago in z/OS / USS 0 Future consideration

Improve information in zFS statistics on z/OS

It is hard to use the zFS statistics because some key information is not available.
over 3 years ago in z/OS / USS 1 Future consideration

Update zlsof -d command

Update the zlsof -d command to identify the blocksize in its output so the size of the locked or delete file can be accurately determined. Today, the zlsof -d displays the following:CommandPID UserFile System MountpointSizeInode/file The user cann...
over 5 years ago in z/OS / USS 1 Future consideration