Win64 Socket Log Trace Option |
Virtual Machine |
 |
Use this option to trace the socket interface code. This is used for I/O to the GUI screen client. To enable this option, you must create the log file before starting the kernel (you can just use notepad to create an empty file). The log file is called P4BUS.LOG, and it is in the Windows temporary directory. The name of the Windows temporary directory is defined by the TMP or TEMP environment variables.
If this file exists, it is appended to.
Pro4 API trace
There are two sets of trace for the process using the Pro4 API Interface (P4API). This is the API logging option, and one of the General Trace options, TRACETASK.
The P4API call 'setDebugMode(TRUE)' is used to enable the trace log. See for example the P4TASK test program, which issues the call if the "/d" command line parameter is specified.
If Debug Mode is enabled, the log messages are written to the standard error output file for the process.
If the P4BUS.LOG file exists, then all the log messages are also written to the log file. If TRACEIO = 1 or greater is also specified, then they are also written to the General Trace File.
If TRACETASK is specified, then they are written to the General Trace File.
The API logging option uses the same file as the Win64 Socket Log. See the previous section for how to enable this.
For tracing the Pro4 Bus Interface in the kernel, use the General Trace option TRACETASK.
Topic ID: 750069