Abend-AID Support for WebSphere MQ
Fault Detection and Diagnosis for WebSphere MQ Applications
More than ever, the IT challenge is to combine speed and quality—reducing time to market and meeting release dates while ensuring every aspect of application reliability and performance. Abend-AID for WebSphere MQ helps developers meet that challenge. With Abend-AID for WebSphere MQ, developers can respond to and resolve WebSphere MQ failures in test and production to produce reliable applications that perform as intended, when they're needed.
Abend-AID for WebSphere MQ supports legacy renewal systems in batch, IMS and CICS environments—extending Abend-AID's benefits to IT projects where mainframe resources have been revamped for e-business.
Abend-AID for WebSphere MQ provides developers with the ability to:
Clearly define reason, return and error codes
WebSphere MQ presents hundreds of unique reason, return and error codes that often fail to reveal the actual source of a coding error, providing developers with limited problem-solving information.
Abend-AID for WebSphere MQ clearly defines reason, return and error codes, which helps find the real cause of the problem. The tool specifies corrective action, saving time in test and production.
Obtain MQ environment information whenever an application fails
Each layer of technology provides additional opportunity for application failure, and a more difficult time in determining where an error occurred. Adding new layers of technology increases the complexity of developing and supporting systems exponentially.
Abend-AID for WebSphere MQ provides MQ environment information whenever an MQ application fails, even when the problem may reside in other areas.
Solve problems quickly
There are hundreds of API options available either by default or choice. Depending on which options are active, different codes will display when a problem occurs. It can be very difficult to determine precisely which options were active when a problem arises.
Abend-AID for WebSphere MQ removes the mystery of untangling the API interface by clearly listing the configuration in place at the time of a failure.
|
