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 87

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)
almost 5 years ago in z/OS / USS 1 Future consideration

Citi requests WJSIPUSE be a formally supported product

Citi has had experience with WJSIPUSE. They asked me if it, or an equivalent, can be formally supported by IBM. I am submitting the request on their behalf.
over 3 years ago in z/OS / USS 2 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

USS_PARMLIB_MOUNTS Health Check Refresh After IPL

During a recent IPL a typo in the BPXPRMxx member had the incorrect name for a zFS file system. As a result, the mount failed with error message BPXF002I: BPXF002I FILE SYSTEM OMVS.ASYS.ORESB1.COBOL42 WAS 674 NOT MOUNTED. RETURN CODE = 00000081, R...
about 4 years ago in z/OS / USS 1 Future consideration

Simplified MNTE_SYSLIST syntax as part of z/OS UNIX REXX mount command

Currently, if a user would like to include MNTE_SYSLIST as a parm in his USS REXX mount command implementation, the user must code the MNTE_SYSLIST as though they are writing assembler code using the mapping described in BPXYMNTE: MNTENTSYSLISTNUM...
11 months ago in z/OS / USS 0 Future consideration

Issue WTO about the ROOT (sysplex root) mount after processing BPXPRMxx

As we had a failure to mount the sysplex root correctly (see PMR), it would be very useful to have an indication after processing the BPXPRMxx (IPL) how the root filesystem was mounted (RO or RDWR). If the mount was not made as wanted (see PMR) ma...
about 8 years ago in z/OS / USS 2 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

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

OMVS Shell Logging to SYSLOGD

IBM should provide the ability to log messages to the active OMVS/USS syslogd. Currently logger, which is standard in UNIX for writing messages to syslogd, does not have this ability in z/OS but writes messages to the z/OS SYSLOG without an option...
almost 8 years ago in z/OS / USS 4 Future consideration

CHECK(IBMUSS,USS_PARMLIB_MOUNTS) make MTAB updatable.

IBM Healthchecks are very good to follow, to avoid an outage. We use them a lot! But if a mount statement of a ZFS data set is wrongly defined in BPXPRMxx. The Healthcheck (IBMUSS,USS_PARMLIB_MOUNTS) complains with an exception. "ZFS NOT MOUNTED. ...
over 9 years ago in z/OS / USS 3 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.