- Initialization output from oninit -v (or starts %INFORMIXSERVER% -v on Windows).
- Ouput from an unhandled exception in a process launched within a Virtual Processor such as a JVM crash in a Java Virtual Process (JVP).
On UNIX oninit output to standard out will appear in the console window where oninit was launched. On Windows, since IDS runs as a Windows service, the output is lost. One way to see this output is to run oninit in foreground on Windows (see an earlier post), but suppose the problem you're trying to investigate only occurs when IDS runs as a service?
The solution is to set the environment variable ONINIT_STDOUT to point to a file where the stdout and stderr output are to be printed. This needs to be set as either a system-wide environment variable or a user environment variable for the informix user.
For example if I set ONINIT_STDOUT to c:\temp\oninit_out.txt in Control Panel and start IDS in verbose mode with:
- starts %INFORMIXSERVER% -v
The c:\temp\oninit_out.txt file will contain the full verbose output from the IDS initialization.
I was fairly sure this feature was documented - it's been in the product since 9.30.TC7, but a quick search draws a blank - will try to get this added to the documentation.