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 98

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
over 4 years ago in z/OS / USS 1 Future consideration

Use USS_PARMLIB Health Checker on Libraries other than SYS1.PARMLIB

We use USS_PARMLIB Health checks on our BPXPRMxx members in SYS1.PARMLIB. However, most errors occur during IPL time with an updated version of these members. It would be convenient if we can use the USS_PARMLIB Health check on other (distribution...
over 4 years ago in z/OS / USS 3 Future consideration

Mount point and directory hierarchy verification

Just like the SYNTAXCHECK checks the syntax of BPXPRMxx, I'd like to have the ability to compare whatever there is in the BPXPRMxx in terms of mount and mount points against the root file system. A feature that checks if the mount points exist in ...
over 4 years ago in z/OS / USS 1 Future consideration

SMF92 record remount in correct mode

The product only writes out the remount SMF record during the unmount portion and does not write another record after it is mounted again. This means that the mode in the record does not necessarily reflect the correct mode in effect after the rem...
over 4 years ago in z/OS / USS 1 Future consideration

Update OCOPY to correct abend S213-15 (IEC143I) if DSNTYPE=LARGE and SMS BLOCKTOKENSIZE is REQUIREd

We depend OCOPY to move files from z/OS Unix space (zFS) and more importantly, Network File System space into z/OS data sets. These files can be very large and require DSNTYPE=LARGE. However, in our z/OS ISV development environment with SMS settin...
over 4 years ago in z/OS / USS 4 Future consideration

Allow System Symbols in keyword name automount policy

I want to have a single entry in automount policy that covers all LPARs in a sysplex. Instead, I have to have an entry for each because I cannot use &SYSNAME in the name component.(Case TS002611927 is not allowed in PMR field)
over 4 years ago in z/OS / USS 1 Future consideration

z/OS USS using "stat" and "st.st_size" does not give expected, correct value

z/OS - Unix System Services For such big file sizes, using "stat" and "st.st_size" does not give you a precise size value unfortunately as you see in comparison with the "ls -l" output that includes the exact value.
almost 5 years ago in z/OS / USS 3 Future consideration

USS Health Check for MOUNTS limit

a USS Health Check would give a warning for when a threshold was crossed, alerting users to a fixed limit for the number of files that can be mounted.
almost 5 years ago in z/OS / USS 1 Future consideration

Z/OS Unix OCOPY

Update OCOPY to correct abend S213-15 (IEC143I) if DSNTYPE=LARGE and SMS BLOCKTOKENSIZE is REQUIREd.
almost 5 years ago in z/OS / USS 4 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...
almost 5 years ago in z/OS / USS 2 Future consideration

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.