IBM Rational Performance Tester (RPT) supports various error handling conditions which can help you narrow down the identification of performance bottlenecks of the given applications. You can specify how error conditions are handled when running a test or schedule. Error conditions include verification point failures, connection failures, server timeouts, custom code alerts, and problems with data correlation.
Say, for example, if you encounter an issue in the first transaction and based on this you want to exit from all the transactions and start from the first transaction all over again. It could also be a case where you cannot continue to next iteration as the loop is provided in the schedule. Let's discuss one simple scenario on similar lines.
Below are the Transactions available in the script:
Below are the HTTP pages available in the Transaction’s:
What happens if you select Exit Transaction and outermost in a request available in ‘Login_Logout_maglis_Landing_Page’ Http page? Will it exit from 'Transaction:Login_Logout_MAGLIS_Logout’?
So, if you select Exit Transaction and outermost in a request available in ‘Login_Logout_maglis_Landing_Page’ Http page, It will exit from the Login_Logout_MAGLIS_SignIn transaction and begin running the Login_Logout_MAGLIS_Logout page in the Login_Logout_MAGLIS_Logout transaction. Selection of "Innermost/Outermost" doesn't matter -- it would only apply if you had nested Transactions. However, if you want to start the test over in the event of a failure, you should select Exit Test. If in case you are looping in the schedule, if you exit the test, it should start over with the next iteration.