The generic utility and caching APIs support execution on an application server. They provide functions to define the application server connection to be used when a local database is not present. The functions that read data from or write data to a database forward their requests to the application server whenever they detect that the database is not local. For application server execution, you can only call the procedures in the caching or generic utility APIs directly, as they are the only APIs that are application server aware.

If you want to call any of the other standalone procedures directly, your code needs to handle the forwarding of requests to the application server. For example, in the following combination of pseudo-code and ABL, the caller handles the application server connection:

DEFINE VARIABLE hAppSrv AS HANDLE    NO-UNDO.
DEFINE VARIABLE hDSet   AS HANDLE    NO-UNDO.
DEFINE VARIABLE cError  AS CHARACTER NO-UNDO.

CREATE SERVER hAppSrv.
hAppSrv:CONNECT("-AppService asbroker1 -H localhost- S 5162").

RUN auditing/_get-policies ON hAppSrv 
  ("sports2000", OUTPUT DATASET-HANDLE hDSet, OUTPUT cError).