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.

Add a new idea Subscribe
Status Not under consideration
Workspace z/OS
Categories Communications Server
Created by Guest
Created on Jun 6, 2012

RELATED IDEAS

SYSLOGD logging messages to LOG_DAEMON & LOG_ERR

Currently the SYSLOGD component routine loginfo() is unconditionally calling logmsg() to log the messages for LOG_DAEMON and LOG_ERR to both the daemon and errors files.

Have all error messages go to the errors file and all the normal messages for syslog daemon go to the daemon file.

Idea priority Low
  • Guest
    Reply
    |     Nov 19, 2015

    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 Communications Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Networking
    Product - z/OS Communications Server

  • Guest
    Reply
    |     Jul 13, 2012

    Hi ,The syslogd component provides a "facility" (such as daemon, local0, etc) and a "priority" such as err(or) critical, warning, info, etc.  You can use the rules (based upon facility and priority), syslogd provides to log messages to the defined log file.  For example:

                  *.err   /dir/all_errors.log
                  
                    or

                 daemon.err   /dir/daemon_err.log             /* log only errors */
                 daemon. *     /dir/daemon_all.log              /* log all errors   */

    The above would allow you to separate the messages with error priority in a separate file (daemon_error.log).  All messages (including error) would go to daemon_all.log.  The assumption is that you would want to have all messages in a chronological order.  If you don't then I don't think there's a way to exclude only error messages.  Do you still feel you require additional support?

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.