Admin Production rocket
Current Publication
Enterprise Test Server V8.0 Troubleshooting Enterprise Server Applications Determining the Failure Type Incorrect Output

Incorrect Output

Enterprise Test Server V8.0
Created:
Last Uploaded:January 7, 2025 12:30 pm
Last Updated:
Initial Upload:January 2, 2025 4:13 pm
tag Enterprise Test Server
tag 8.0
tag Developer
tag Reference
tag No Download
Rocket® Enterprise Test Server (formerly a product of Micro Focus or formerly a product of Open Text) documentation, created before Rocket Software acquired certain products from OpenText, may include outdated references to "Micro Focus" or "OpenText", both of which are trademarks of OpenText or its affiliates. Rocket Software is not affiliated with Micro Focus or OpenText and has since rebranded these products as Rocket® products. You may also encounter outdated links in this documentation. If you do, please contact Rocket Support (support@rocketsoftware.com) for assistance.

Incorrect Output

When application output is not what it should be, the first step in determining the problem is to identify application problems vs. Enterprise Server infrastructure problems.

Application failures other than abends are often application problems. Start by consulting the Look at the active trace dataset coupled with the system trace table in the dump X dataset (casdumpx.rec) to establish the application activity before the failure.

Application abends can be due to application problems or enterprise server infrastructure problems. Look in the active dump dataset for an RTS error dump. If found, evaluate the RTS error and classify the problem from this. What module experienced the failure, application or enterprise server infrastructure?

Parent topic: Determining the Failure Type

    • Related Content