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
C:D Link failure mesage ids - SVTN001I and SVTO022I documentation
There are few of the transfers ended (failed) with connect: direct completion code 10 along with completion link failure message text SVTN001I and SVTO022I. We checked under below path for the allocation errors message id along with max retry limit of each of the message id but these message ids were not present. C:D -> ADMIN -> INQ -> ALLOC.CODES & ALLOC.RETRIES.in the verified
Hence created problem ticket, L2 support team provided in their research could not find documentation that lists the messages considered for retry. When they discussed this with their Research Engineer, he confirmed this. Since there is no documentation available for these link failure message ids, suggested me to submit a RFE (Request for Enhancement).
We wanted to know the details like, Documentation to be included in the connect direct menu, when are these message ids populated? Are these message texts eligible for retry process? Is there any retry limit for these message ids?
What is your industry?
How will this idea be used?
It would be helpful for the feature link failure issues, so that we can include to retry queue in our logic to avoid issues.
Do not place IBM confidential, company confidential, or personal information into any field.