Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Planned for future release
Workspace z/OS Connect
Created by Guest
Created on Jul 1, 2025

A "kind" of STATEOD parameter similar to what exists in CICS

SMF 123 records are written at the stop of the zOSconnect server or every 20 requests or at each request if it is set in the server.xml (bad idea for production environment)

We would like to have a parameter similar to SATEOD in CICS to write the SMF123 at the end of the day, so that a request that was executed, is not written in the SMF file of the next day


Idea priority High
  • Admin
    Demelza Farrer
    Feb 25, 2026

    We have further investigated this IDEA and would love to know from our users if the following proposal would meet the requirement as layed out in the IDEA?

    A possible solution to this idea would be to enhance the audit interceptor to write buffered request data to SMF at a specific time (specified by HHmmss) for API Provider and API Requester

    The following configuration attributes are proposed to be added to the auditInterceptor:

    apiProviderEndOfDay = [true/false] Indicates whether or not API provider SMF records should be written at the end of each day. Default is false.
    apiProviderEndOfDayTime = The time of day (HHmmss format) when API provider SMF records should be written. Default is 23:59:59.

    apiRequesterEndOfDay = [true/false] Indicates whether or not API requester SMF records should be written at the end of each day. Default is false.
    apiRequesterEndOfDayTime = The time of day (HHmmss format) when API requester SMF records should be written. Default is 23:59:59.

    The following messages are proposed to be added:

    BAQR08nnI = The audit interceptor {name} is set to write any buffered API provider request data to SMF at {time} each day.
    BAQR08nnI = The audit interceptor {name} is set to write any buffered API requester request data to SMF at {time} each day.
    BAQR08nnE = Invalid end-of-day time format: {time}. Expected HHmmss format.

    Please let us know whether an implementation using these configuration attributes and messages meet the requirement detailed in this idea?