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 ISPF
Created by Guest
Created on Nov 10, 2021

More informative messages on RACF error

Issuing the TSO command "racmap" is producing the following message in the TSO session:

Abend 684000 hex occurred processing command 'RACMAP '.
ISPD210 CMD abended - 'RACMAP' terminated abnormally.

This abend is actually 2 codes 684 system abend and 000 user abend. 684 indicates that the command has not been added as an authorised command on the system.

To me, this ranks very low on usability - how is a user supposed to know there are actually two abend codes here?

At an absolute minimum, this should be reported as "system abend code xxx, user abend code yyy" or better still not report the 000 code at all.

Given the abend is such an explicit condition, why is the user not told the problem for example "This command needs to be authorised on the system using AUTHCMD" preferably without the abend at all.

Idea priority Medium
  • Guest
    Reply
    |
    Jan 18, 2022

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - ISPF
    Operating system - IBM z/OS
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - z Systems Software
    Product - z/OS
    Component - RACF
    Operating system - IBM z/OS
    Source - None