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 z/OSMF
Created by Guest
Created on Aug 6, 2019

z/OSMF: Make IZUG.log messages eligible to be sent to the operlog by parmlib member

z/OSMF messages (of all types; informational, warning, error, severe) are currently all writen to the IZUG0.log in its own unix directory /global/var/zosmf/data/logs/.
z/OSMF currently does not issue any messages to the syslog/operlog. (with a few exceptions)

This makes automating/monitoring z/OSMF a difficult task for automation products, who usually only monitor the syslog/operlog.

This RFE is raised to provide a setting (preferably adding to IZUPRMxx) to, either allow message to also be cast to the Syslog/Operlog or to specifiy specific messages to be always sent to the operlog too.

Example:

LOGGING INFO(%%%%,%%%%) WARNING(%%%%) ERROR(%%%%) SEVERE(%%%%)

Where %%%% can be the indentifier of said message. Multiple digits can be specified (seperated by "," )

E.g. ERROR(0001) WARNING(861) Would apply on:

IZUWF0001E The request to create a workflow failed because the maximum number of workflows is reached.

IZUG861W: The number of cross-site request forgery (CSRF) attempts detected since the last reported occurrence is "%"

and thus always also sent to the syslog/operlog.

Idea priority High