Try OpenEdge Now
skip to main content
Servers, DataServers, Messengers, and Adapters
Monitoring Plans and Rules for Servers, DataServers, Messengers, and Adapters : Understanding and using resource monitor rules : Average Procedure Duration High rule : Supplying data for ABL procedures and AppServers
 
Supplying data for ABL procedures and AppServers
AppServer ABL procedures execute with the RUN statement based on an AppServer connection handle. The procedures can reference PROPATH relative directories, unqualified procedure names, internal procedures, and user-defined functions. To measure the duration of specific AppServer procedures, enter the procedure name in the Average Duration High Rule page exactly as it is referenced in the RUN statement.
The following table describes three examples.
Table 45. Examples of AppServer-related ABL procedure entries
This ABL procedure entry . . .
Runs a procedure that . . .
RUN myOrders.p ON SERVER hAppSrv
Is PROPATH-relative. This entry refers to a procedure that is located in a directory or procedure library specified on PROPATH.
RUN myApp/myAccounts.p ON Server hAppSrv
Is PROPATH-relative. This entry refers to a procedure that is located in the subdirectory called myApp that is relative to PROPATH.
RUN processOrder IN hProc
Shows the execution of an internal procedure.
To measure any of the example procedures noted in the above table using the Average Procedure Duration High rule, you must enter the procedure name exactly as it appears on the RUN statement.