Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal
Hide about this 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

RACF

Showing 58

To externally document return/reason codes in relocate section 443

Currently the authentication info in byte 1 of the relocate section 443 does not differentiate between when IDs with MFA fallback are logging in when MFA started task is down and when they are logging in from a bypassed application. Having a prope...
about 1 year ago in z/OS / RACF 0 Future consideration

Enhance RACF so that type 80s cut for CONNECT commands are consistent

RACF should be consistent about when it cuts type 80 records for CONNECT commands. That is not the case today. We always get them when the AUTH() parameter is specified even if the connection already exists. We do not get them if we issue this typ...
over 8 years ago in z/OS / RACF 1 Future consideration

Apply RACF Conditional ACL only when in MFA fallback mode

When Using MFA, RACF conditional access lists should have the option to be applied only when the user is being authenticated in password fallback (PWFALLBACK) mode – in this case, to limit access to a terminal name prefix. (Ross Cooper suggested I...
over 5 years ago in z/OS / RACF 1 Future consideration

z/OS UNIX File System Audit Default Bits

Please enhance z/OS UNIX so I can set default auditing bits for both the file owner and system Auditor.
almost 6 years ago in z/OS / RACF 3 Future consideration

Allowing first qualifyer masking in DATASET names

Many legacy naming conventions make it difficult to establish a simplified set of commands to define DATASETS. This is specially hard in the case of sysplexes with many systems so there are DATASETS that somehow identify the system in the first qu...
almost 3 years ago in z/OS / RACF 0 Future consideration

SURROGAT with JESINPUT and NODES

We have a requirement to submit a job from zVM, comes across using the NODES class, and then use SURROGAT with WHEN(JESINPUT). This doesn't work
over 1 year ago in z/OS / RACF 0 Future consideration

RACF RVARY password should have additional control point

Please enhance RACF so that the RVARY STATUS & SWITCH passwords are not the sole control point on this command.Alternatively think up an entirely new more 21st century approach to replace the RVARY password with completely.
over 8 years ago in z/OS / RACF 1 Future consideration

Create an attribute that would prevent the REVOKE of a UserID due to incorrect password attempts

Requesting the creation of an attribute that would exist on the User ID that would prevent/override the User ID from being revoked due to invalid password attempts. Any successful authentications should be allowed. Unsuccessful authentications sho...
almost 2 years ago in z/OS / RACF 0 Future consideration

RACF Password Settings need to include Complexity, Examples: 1. To prevent the use of 3 repeating or sequential characters. 2. Avoid specific words such as User Name / Name of Service. 3. Prevent the use of passwords obtained from previous breaches.

Audit requires ability for specific Complexity settings as listed in my Idea above and beyond RACF specific Password settings. Examples: 1. To prevent the use of 3 repeating or sequential characters. 2. Avoid specific words such as User Name / Nam...
about 2 years ago in z/OS / RACF 1 Future consideration

RACF database recovery utility

In the case of primary database in error with no backup database, after restoring a copy from dump, maybe we have lost some updates. In System Programmer's Guide we can find the following text: Your database is probably back-level. To bring...
about 2 years ago in z/OS / RACF 1 Future consideration