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 103 of 3562

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

Declaration of the symbolic link /usr/bin/env in the standard USS installation

Using node.js or npm requires access to the "env" program at the location /usr/bin.By default, when USS is installed, the "env" program is placed in /bin.A symbolic link /usr/bin/env must be created on /bin/env as specified in the installation pro...
over 4 years ago in z/OS / USS 4 Future consideration

syntaxcheck

We would like to request extend syntaxcheck by including 'PARM(...)' checking also when syntaxcheck for bpxprm is executed.
over 6 years ago in z/OS / USS 2 Future consideration

64-bit version of BPXWDYN for C

Please provide a 64-bit version of BPXWDYN
over 4 years ago in z/OS / USS 2 Future consideration

Audit all superuser usage

Provide the ability to audit ALL superuser usage.
over 7 years ago in z/OS / USS 1 Future consideration

Improve USS_PARMLIB Healthcheck to allow for async mounts

Healthcheck USS_PARMLIB flags an exception for filesystems that are mounted asynchronously. The error is 'Path not found. RC=00000070 RSN=05940350'. However, by the time the check runs again, the file system is mounted so the check is successful. ...
over 6 years ago in z/OS / USS 1 Future consideration

Allow the same file name (indirectly volser cataloged) to be mounted to different mountpoints in a shared fileysystem

The ability to mount the same name filesystem (indirectly cataloged) to different version mountpoints would simplify deployment for me.
over 3 years ago in z/OS / USS 0 Future consideration

Avoid manual link creation to /bin/env for Node.js

During the installation of Node.js a manual creation of the symlink "ln -s /bin/env /usr/bin/env" is advised.We try to avoid manual changes to the /usr directory provided by IBM.The link could be provided by IBM in the z/OS root filesystem or the ...
about 4 years ago in z/OS / USS 2 Future consideration

Enhancement to SETOMVS SYNTAXCHECK

The PARMLIB(BPXPRM00) member is shared between two partitions (SQA1 and SQT1) of the same sysplex. It contains the following mount command among others: MOUNT FILESYSTEM('SYSB.PHAP850.UNIX.&SYSNAME..HTTPSRVR') TYPE(HFS) MODE(RDWR) MOUNTPOINT('...
over 8 years ago in z/OS / USS 2 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 5 years ago in z/OS / USS 1 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.