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

Clear

Ideas

    Showing 115 of 3839

    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 7 years ago in z/OS / USS 1 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 9 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 3 years ago in z/OS / USS 0 Future consideration

    Uncontrolled environment after accessing OMVS

    After accessing OMVS under TSO we are getting an uncontrolled environment and is necessary to logoff/logon in order tho have again a controlled environment. We received the following message if we try to access any TSO application that requires a ...
    about 2 years ago in z/OS / USS 1 Not under 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 3 years ago in z/OS / USS 0 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 6 years ago in z/OS / USS 1 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.
    over 6 years ago in z/OS / USS 1 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...
    almost 10 years ago in z/OS / USS 2 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 4 years ago in z/OS / USS 0 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 2 years ago in z/OS / USS 1 Not under 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.