Debugging and Tracing Your Application

The Sentinel RMS licensing library has been written to intercept and log four different levels of events. The values for the different events in increasing order are:

>VLS_TRACE_KEYS

>VLS_TRACE_FUNCTIONS

>VLS_TRACE_ERRORS

>VLS_TRACE_ALL

Tracing can be enabled using either traditional or unified API functions. To enable tracing using Unified APIs, click here.

NOTE   A fifth value, VLS_NO_TRACE, is the default and turns off all logging activity.

You can activate one of these levels by inserting a call to VLSsetTraceLevel somewhere in the client code. The trace level will not be set until the function is called, making it possible to limit logging to certain portions of the client code only. You may choose to place more than one such call in the client code and use different trace levels with each call to generate different logging profiles based upon what code is being executed.

NOTE   You can also guide your customers to enable License Manager tracing. See Configuring the License Manager Tracing Operations.

The Sentinel RMS client library has built-in default responses to all error conditions that may arise. Custom error handlers can also be registered with the Sentinel RMS licensing library. Each error condition handler must be explicitly registered. The default error handlers will be used for those errors for which no explicit handlers are registered.