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).
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.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
It is our mission, within IMS, to deliver high quality code to our clients. Our goal is that this enhancement continues to help drive success for your company!
I am excited to share with you that we have successfully delivered an enhancement with the requested RFE ID 130780.
This enhancement has been delivered via IMS service process:
IMS 15 APAR[PTF]: PH28554[UI71476] - https://www.ibm.com/support/pages/apar/PH28554
This enhancement enables you to send IMS Connect message by using the IMSInteraction.pingIMS method.
To use the pingIMS method, you first have to cast your Interaction to an IMSInteraction and call imsInteraction.pingIMS(imsInteractionSpec).
To use the pingIMS method to check each connection status in the connection pool. You can repeatedly call the pingIMS with each conn Connection object from the ConnectionFactory. If the pingIMS method return false, it means that the connection is stale and no longer valid. Do this as many times as needed up to the connection pool size.
Please share your feedback with us as you implement this enhancement. Let us know if you have any questions.
Have a great day!
Haley Fung - hfung@us.ibm.com
Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.
After reviewing this request for enhancement and assessing its potential value, our decision is to add this RFE ID 130780 to our backlog . Items in our backlog are expected to be delivered within the next 18 months. We reserve the right to re-prioritize our backlog items as new requests come in. This helps ensure that we are constantly focused on providing the best value to all of our clients. Thank you for your continuous support and interest in the IMS product.
Thank you!
Haley Fung - hfung@us.ibm.com
We do not use sysplex distribution for the IMS connector, because we want to make a fine-grained switch depending on the ICO error message or timeout. The problematic situations, which we want to master with a skilful panning, do not arise predominantly isolated e.g. by the unavailability of the IMS-Connect or the IMS, but from the interaction of all backend and network components up to databases.
Therefore we use two independent instances of IMS-Connect in a sysplex, which primarily address the IMS on the same system and secondarily the IMS on the complementary system. From the server there are simplified two connection factories to PRIMARY and SECONDARY IMS-Connect.
If, for example, timeouts occur during processing within the primary IMS instance, this is noticed by the server application and the SECONDARY IMS Connect is addressed. Meanwhile, as long as the primary IMS instance is still active, the PRIMARY IMS Connect would want to send all requests to the primary IMS instance with timeouts.
I hope this clarifies our approach and remain with best regards,
Stefan Block
Thank you for your interest in keeping IMS a vital and successful product. Software development has continuously evolved during IMS's lifetime, and so has IMS itself. We have kept pace with, adopted, and implemented many industry standard best practices within our organization, including Continuous Delivery, Design Thinking, and Agile.
At this time, after further review this request for enhancement, we need more information to understand the use case of this requirement. Based on the description of your use case, most of the customers utilize the Sysplex Distributor to send the workload to the IMS Connect instances that is up and running automatically. The advantage of using Sysplex Distributor is you do not need to code that routing logic in your application.
If you can provide further information on why Sysplex Distributor does not work for you, it will be helpful for us to assess this RFE.
Thank you!
Haley Fung - hfung@us.ibm.com