OpenAPI User Guide > OpenAPI User Guide > Creating an Application with OpenAPI > How You Can Create an OpenAPI Application > Environment Variables
Was this helpful?
Environment Variables
The following user environment variables are used by OpenAPI:
• II_API_TRACE
• II_API_LOG
• II_API_SET
II_API_TRACE
The II_API_TRACE environment variable specifies the desired trace level of OpenAPI. When it is not defined, it has a value of 0. You can set the II_API_TRACE environment variable to one of the following values:
Value
Action
1
Display fatal error messages
2
Display non-fatal error messages
3
Display warning messages
4
Display checkpoint messages, such as which OpenAPI function is being executed
5
Display detail information, such as values of input and output parameters
II_API_LOG
The II_API_LOG environment variable specifies the desired output file for all OpenAPI tracing. The file name can contain one or both of the following parameter values:
%p
Replaced at startup with the Process Identifier (PID) of the server process.
%d
Replaced at startup with the current date in YYYYMMDD format.
For example:
II_API_LOG = $II_SYSTEM/ingres/files/oapi_%d_%p.log
This file specification prevents servers from writing to the wrong log.
II_API_SET
The II_API_SET environment variable allows GCA_TRACE messages to be written to a file.
Set II_API_SET to PRINTTRACE to write GCA_TRACE messages to default output file iiprttrc.c. To direct output to a different file, add the TRACEFILE option followed by the file name.
For example, on Linux, to enable OpenAPI tracing of GCA_TRACE messages to output file tracing.log:
setenv II_API_SET "printtrace; tracefile tracing.log"
Last modified date: 08/14/2024