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 Delivered
Workspace z/OS
Created by Guest
Created on Feb 28, 2018

CSSMTP should allow SYSOUT class specification for error reports

When CSSMTP detects an invalid SPPOL file, it can optionally generate a report that describes the error(s). This is accomplished by using the Report statement in the CSSMTP configuration file. Unfortunately, when setting the Report statement to SYSOUT, there is no way to specify the SYSOUT class and CSSMTP uses the SYSOUT class characteristics of the SPOOL file that was used in the attempt to send an email. In most cases, this is generally a “punch” class with an external writer name of CSSMTP or SMTP. CSSMTP should not be using that as a model to generate these error reports—these are SYSOUTs, not something to be “punched” to the internal reader or an external writer. Each shop should have the ability to specify the SYSOUT class so they they can properly control and manage the output that is generated.

Idea priority Medium
  • Guest
    Reply
    |
    Jan 16, 2020

    This was addressed via the "SMTPD compatibility enhancements for CSSMTP" for z/OS V2R3 and V2R4 via APAR PH18237.