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 Not under consideration
Workspace z/OS
Categories SDSF
Created by Guest
Created on Jul 14, 2023

Suppress SDSF ULOG panel after z/OS V2.5

SDSF ULOG display was changed by z/OS V2.5 following.

<V2.4>The users who do not authorized READ access to resource ISFCMD.ODSP.ULOG.jesx could not display ULOG panel.

<V2.5> The users became to display ULOG panel whether authorized or not READ access to resource ISFCMD.ODSP.ULOG.jes.


We require the function to inhibit to display ULOG panel for certain users like V2.4 or earlier.

The reasons are as follows.

  • The users who do not authorized to activate EMCS console can display ULOG panel. If they issue commands on ULOG panel, ICH408I message is displayed on ULOG and SYSLOG and Extra messages may interfere with system monitoring.

  • The users who do not authorized to display SYSLOG can refer a part of ICH408I message on ULOG panel. As a result, it is possible that they infer about RACF setting from ICH408I message displayed on ULOG.

  • All SDSF Panel exclude ULOG panel can be inhibited to display, so we think that ULOG panel should be protected as well as other panels.

Idea priority High
  • Guest
    Reply
    |
    Jul 31, 2023
    We have emailed back and forth with the submittor, we don't see why this is an issue. All users should be able to access ULOG. We don't believe it introduces any security concerns.

    Over the past several releases, SDSF has generalized the ULOG to contain messages related to the user session as well as system commands and responses. Over time, additional messages and diagnostics will be written to ULOG. It is acting more like an overall log for the user.

    As a result, in v2r5 access to ULOG was changed to be unauthorized, i.e., all users automatically have access to ULOG. There are other functions that are like this, obviously HELP, SEARCH, COLSHELP (COLH), CMDH, ACTH, MENU and SRCH.

    When SAF access is denied and RACF returns an ICH408I message, the message is written to ULOG. Note that when the user has PROF WTP in effect, the ICH408I message will also be written to the terminal regardless of whether the user accesses ULOG. Similarly if you run SDSF in batch you will get the SAF messages.

    In addition, all resources checked are documented, so the ICH408I message in ULOG is not exposing anything that cannot otherwise be derived.

    An extended console will be activated on first access to ULOG. If you want to control activation of the console based on access to ULOG, a custom property is provided for compatibility. Property Console.EMCS.UlogAuthReq can be set in ISFPRMxx.

    When set to TRUE, SDSF will only activate an extended console when the user has read authority to ISFCMD.ODSP.ULOG.jesx. This means that the user will be able to access ULOG but activation of the extended console can still be controlled through use of the ISFCMD.ODSP.ULOG.jesx profile.