IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Is there any way to capture the SNODE name for which the SSL Handshake failure occurring with the error message CAPA202E, since the affected SNODE name is not present in the same line? We are able to find SVTM055I message in the next line but it's not feasible to scrap the SNODE information from that line in CA-OPS/MVS script.
|Link to original RFE||http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=123795|
|What is your industry?||Non-Industry Specific|
How will this idea be used?
Automation script is not able to scrap the right node involved in CSPA202E as it's displayed in previous line or next line of the error message. So, the automation alert is misleading to find/analyse the right node where the actual issue occurred.
Do not place IBM confidential, company confidential, or personal information into any field.