Skip to Main Content
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.

Status Future consideration
Workspace z/OS
Categories RACF
Created by Guest
Created on Mar 2, 2023

Add a set of return codes in RACF r_secmgtoper documentation for empty non-boolean character fields

r_secmgtoper does not validate a field that has no field data in it, and creates an ALTUSER racf command with an empty field. The field is not suffixed with parenthesis to indicate the absence of field data. If the call is made without an EXECUTE option parameter, the return code is 0 indicating no errors.

To reproduce the above case, create an input XML with a "user" security definition with operation="set". Add a Base segment under it and a Password field with no character data in it ('<racf:password></racf:password>') under the Base segment, all under racf or saf namespace. Do not pass the EXECUTE option parameter to IRRSMO00. The returned XML contains an 'ADDUSER <userid>' and an 'ALTUSER <userid> PASSWORD' with all 0 return and reason codes.

We are adding support for r_secmgtoper under ACF2, and are looking for ways to handle inputs like these with a set of standard SAF and RACF return and reason codes. We have not found a set of return and reason codes matching this case.

In the short term, a set of Return Codes can be added to the documentation, indicating the absence of a character field, or an invalid character field, which can be returned to the caller in case r_secmgtoper finds the error before generating commands on the ESM.

Idea priority Medium