This portal is to open public enhancement requests for IBM Sterling products and services. 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 updateson 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
I was developing the map and it broke the whole system. Upon requesting for for information regarding the process, I was told that because the issue is not with the map editor but with the map, every thing is fine and ticket should be closed.
I have 2 points here to discuss regarding this issue. First, I would request to add debugger into the map editor so that developer can see how the program (in or case, map translation) is progressing and how the developer can fix his/her logic to achieve the final objective.
Second, I understand that map editor is a tool to the whole application SI. If I run map test in my application, it should create an instance of the program and that instance can either time out or error out. The application, in any case, should not let the instance keep on running and consume all the memory.
In addition to point two, and as per my case, I ran the map test and instance was created. The instance kept on running and later I terminated the instance forcefully. Then also, the instance kept on running (without any entry in any queue) and brought the adapter to halt. This instance brought the communication bridge down instead of failing itself. I understand this issue severe and at the application side. I request you to have a look at both the points and take appropriate action.
Do not place IBM confidential, company confidential, or personal information into any field.