You can continue to use C APIs to customize your application, but C APIs are not enhanced to support new capabilities provided by Java APIs and REST APIs.
Activates and deactivates client-side logging of server activity.
If you perform a set operation on an overlay and you provide values for an inherited grain, the values are ignored. Only values for extended or overwritten grains of the overlay are set.
Users with permission to perform client-side logging. (See Client-side ARAPILOGGING.)
#include "ar.h" #include "arerrno.h" #include "arextern.h" int ARSetLogging( ARControlStruct *control, ARULong32 logTypeMask, ARULong32 whereToWriteMask, FILE *filePtr, ARStatusList *status)
The control record for the operation. It contains information about the user requesting the operation, where that operation is to be performed, and which session is used to perform it. The user and server fields are required.
A bitmask that indicates the type of logging to set. This is for SQL, filter, API, and plug-in server logging. The possible values are:
Database or SQL logging (
Filter logging (
API logging (
Plug-in logging (
A value that indicates where to return log information. The possible values are
Logs to a file (
Logs as part of an ARStatusList (
A file handle to the log file. It is assumed the file has already been opened. A
NULL value indicates that no writing be done to the file.
A list of zero or more notes, warnings, or errors generated from a call to this function. For a description of all possible values, see Error checking.
whereToWriteMask input parameter is set to
AR_WRITE_TO_STATUS_LIST, the message number is of type
messageNum (number of the status structure), and everything that is logged is of type