IBM Sustainability Software - Ideas Portal
This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
You don't have to shut down all the JVMs but the one you're going to use. However, doing that means you don't have to twiddle and keep trying when the JVM you're on says Admin Mode is on but some other JVM is running a long job that it doesn't feel like stopping. So, in my professional experience, shutting down all JVMs but one is more predictable and often faster than keeping all JVMs up.
Perhaps this idea should be aimed at having Escalations and more cron tasks and etc check MXServer.getMXServer().isAdminModePending() more often and then graciously and quickly stop when it returns true. For example, PMWOGen and Reorder jobs should definitely be doing this.
You should not have to shut down the JVM's.
https://www.ibm.com/mysupport/s/case/5003p00002YuuKbAAJ/apply-database-configuration-changes-to-a-clustered-environment
"Regarding the use of Admin Mode in a clustered environment we recommend that when you are planning to go into admin mode that you shut down all the JVMs but one."
"This also applies for Control Desk 7.5 and 7.6 (and Maximo 7.6, 7.5, 7.1, TSRM 7.x, TAMIT 7.x, and CCMDB 7.x)."
If I understand correctly, it's only possible to things like "shut down all the JVMs but one" from WebSphere...not from the Maximo UI.
Hi,
Yes this behavior still exists in MAM 7.6.1.2.
More information can be found in TS006286516 (including detailed system information).
Thanks.
Thank you for your submission. This should be available after a fix that was made available several years ago. Can you confirm this is still the behavior you experience in the latest versions? Thank you.