This is an IBM Automation portal for Cloud Management and AIOps 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
email@example.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
ZenHub Issue: https://github.ibm.com/hdm/tracking/issues/9169
Thanks for linking the 2 requests Lawrence.
There is another Idea and RFE that is the same request (2019):
To clarify this customer's request/idea, only item 1 below is requested, and only for the Windows native client. The Admin GUI is required to use Netcool; there is no web counterpart at this time.
1) Admin GUI - Java program
2) Native Windows Desktop - C++, MFC
3) Native UNIX Event List - C, X-Windows
From the RFE, below is my comment from 23 Feb 2021:
The following information is from IBM L3 in recent Support Case TS004943871, which was the impetus for client to open this RFE: "The nco_jdbc.timeout is similar to the IPC.Timeout value for the native processes. It's the maximum amount of time that the jdbc client will wait for a response from the server before giving up and saying there was no response. It has nothing to do with the client disconnecting itself after a certain amount of time and requiring the password to be entered again.
The functionality that the customer is looking for does not currently exist. We could write a trigger in the ObjectServer to disconnect specific clients that have not issued any SQL for a specific amount of time, but that won't solve the problem as the client (nco_config in this example) will not request the password again, it will just use the password the user already entered (which it caches in memory in case it ever needs to reconnect). The desired functionality would need to be implemented in the client and is therefore an RFE."