Debugging Programs and Logging Diagnostics
The SDK has diagnostic facilities that may help in tracking down unusual behavior. Enable SDK diagnostics in one of two ways: either when the SDK is initialized with mtaInit() or afterwards with mtaDebug(). The following table lists the diagnostics types that may be enabled through either routine:
|
Diagnostic Type |
Description |
|---|---|
|
MTA_DEBUG_SDK |
Provide diagnostics whenever the SDK returns an error status |
|
MTA_DEBUG_DEQUEUE |
Provide diagnostics from the MTA low-level dequeue library |
|
MTA_DEBUG_ENQUEUE |
Provide diagnostics from the MTA low-level enqueue library |
|
MTA_DEBUG_OS |
Provide diagnostics from the MTA low-level, operating-system dependent library |
All diagnostic output is written to stdout. In the case of a channel program, this is typically the channel’s debug file. Message enqueue and dequeue activities performed through the MTA SDK (and Callable Send facility) will be logged when the channels involved are marked with the logging channel keyword.
- © 2010, Oracle Corporation and/or its affiliates