Show TOC

&ST30_POST_WAIT_ASYNCLocate this document in the navigation structure

You can use the parameter &ST30_POST_WAIT_ASYNC to help you ensure that performance tests executed using transaction ST30 (Global Performance Analysis) and eCATT test configurations are executed correctly when the tested scenarios contain asynchronous parts. The parameter provides a link between the eCATT script run and the activation/deactivation of ST30 measurements.

The parameter is set in the script text, like a command. For this reason, the parameter is displayed in the list of commands.

You use &ST30_POST_WAIT_ASYNC = <xx>. to enter a wait time within and at the end of an eCATT script command. xx is the number of seconds to wait.

Example

&ST30_POST_WAIT_ASYNC = 60.

SAPGUI ( … )

In the case the SAPGUI command waits 60 seconds internally after its last step, before processing continues with the next command of the test script. This differs from the WAIT command, which waits outside the eCATT command.

To test asynchronous calls, the following 3 conditions must be met:

  • Set the parameter &ST30_POST_WAIT_ASYNC = <xx>. before the command that contains the asynchronous parts to be measured.

  • You should allow a long enough wait time to ensure that the asynchronous parts have run before the end of ST30 performance measurement for the relevant eCATT command is flagged.

  • Make sure that everything that is executed in the background runs under the same user context (the user used in the RFC destination from the central ST30/eCATT system to the tested system). This ensures that ST30 can find the relevant performance data (transaction STAD).