ABAPSET_RUN_TIME_CLOCK_RESOLUTION - SET RUN TIME CLOCK RESOLUTION

BAL_S_LOG - Application Log: Log header data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

SET RUN TIME CLOCK RESOLUTION

Short Reference

SET RUN TIME CLOCK RESOLUTION ${HIGH$|LOW$}.

Effect

This statement specifies the measurement precision for the statement GET RUN TIME. It can be changed in a program only before the statement GET RUN TIME is executed for the first time, otherwise an uncatchable exception is raised.

Specifying HIGH defines a measurement precision of one microsecond. If the level of precision is high, this can produce false time values for multiprocessors, since the clocks of the individual processors are not always regularly synchronized on all platforms. The high level of precision on the following platforms always returns correct values:

• AIX

• SINIX

• SUN-OS

• Linux

• IBM i5/OS (previously OS/400)

• Windows

To avoid incorrect time values on the other platforms, LOW can be used to specify a low precision measurement whose resolution depends on each platform.

Without the preceding statement SET RUN TIME CLOCK RESOLUTION, GET RUN TIME uses the high precision measurement implicitly.

Notes

• To execute multiple measurements with different levels of precision within an internal session, the class CL_ABAP_RUNTIME can be used (see Class for Runtime Measurements).

• No exception is raised if SET RUN TIME CLOCK RESOLUTION is used after the statement GET RUN TIME, but the level of precision is not changed.
  
  

Example

Use of SET RUN TIME CLOCK RESOLUTION in front of GET RUN TIME.

Exceptions

Non-Catchable Exceptions

• Cause: An attempt was made to change the level of precision after GET RUN TIME using SET RUN TIME CLOCK RESOLUTION.
  Runtime Error: SET_RUN_TIME_CLOCK_ERROR

ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Length: 3008 Date: 20230322 Time: 100422     sap01-206 ( 54 ms )