How do I make the OSS API functions write out data and error messages when using the time-optimized runtime?

When using the time-optimized runtime, you should C-compile the generated .c file with the macro -DOSSDEBUG #defined. The -DOSSDEBUG macro has three settings: low (0), medium(1), and high (greater than or equal to 2). For example, to set tracing ability to medium, you would #define the following on your C compiler command-line.:

 -DOSSDEBUG=1

When -DOSSDEBUG=0 is specified, no error message is constructed and only an error code is returned. When -DOSSDEBUG=1 is specified, a simple error message that states what went wrong is generated along with the error code. However in this case, no context info is generated. When -DOSSDEBUG=2 (or greater) is specified, an error message is generated that explains the specific error and where (which component type was being processed) the error was detected. Additionally, an error code is returned.

Note that the error code generated is the same regardless of what the OSSDEBUG level is. Also note that ideally the OSSDEBUG value should not be set to a value greater than two, for the effect of such values is reserved for possible future use by OSS.

For more information about OSSDEBUG, see the C Compiler Macros for Controlling Performance/Memory Footprint when Using TOED section.

The samples included with some of the Knowledge Center answers are meant for your general understanding of the OSS products. Different versions of the products might produce slightly different outputs. Consult the products documentation and samples for the most up-to-date products information and code examples.