IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Add a new idea Subscribe
Status Delivered
Workspace Db2 for z/OS
Created by Guest
Created on Apr 22, 2017

RELATED IDEAS

Managing status of DB2 REST services

One of the really good things about the REST implementation is that it is based on static SQL. This makes it possible for us to get to know what services will be affected before we do some maintenance to one or more referenced tables. But, without the possibility to stop the impacted services, applications will get "strange" error codes dependent on where in the maintenance process we are.

We would rather be able to stop the impacted services based on the dependency information in the DB2 catalog - then it would be scriptable. That would make our applications get consistent error codes and furthermore, a GET on an impacted service will show that it is disabled in the JSON description of the service (in "serviceStatus").

To make it easy from an operational standpoint (eg to script the stops and starts), the start and stop of services should be implemented as -START SERVICE and -STOP SERVICE commands modeled on the -START PROCEDURE and -STOP PROCEDURE commands. Furthermore there is also a need to have a -DISPLAY SERVICE command. The status information should also be reflected in the output when you do a GET on a specific service or when you list all available services - the information can be tagged as "serviceStatus" and displayed as "started" or "stopped".

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.