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.

Add a new idea Subscribe
Status Functionality already exists
Workspace z/OS Connect
Created by Guest
Created on Oct 15, 2025

RELATED IDEAS

stopEntity() logging visibility

For creating HA solution for ZCEE we have implemented Automation solutions by issuing REFRESH commands whenever an API or Services are being installed,updated,deleted etc.
We pushed the message codes to the MVS Syslog, and that is how Automation picks up. It works as expected.
The problem is when the customer stops an API or a Service (with ZOSConnectProject:stopEntity() - this does not generate a message in Mainframe ZCEE server message log, which can be pushed to MVS Syslog).

When a STOP is being done, and the refresh does not happen, an UPDATE on the service/API can not happen, because it needs to be stopped first.

The idea is to have a BAQ* message code for this in message.log which can be pushed to MVS Syslog in order to have it captured, as for now it cannot be captured as it is not generating any messages on any verbose level.

Thank you in advance for your implementation, which will help our work and our customer reliability with ZCEE HA! 

Idea priority Medium
  • Admin
    Beth Williams
    Dec 17, 2025

    This IDEA has been assessed by the team. For zosconnect-3.0 there isn't a requirement to stop an API before updating it. Files are copied to the correct directory and then a REFRESH command is issued to make them live. For more information, please refer to the topic "Deploying APIs with zosConnect-3.0" in our documentation here. As such this IDEA is being closed. If you have any further requirements in addition to the capability that exists today, we would welcome another IDEA.

    Reply

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.