Debugging

Production Reporting Remote also offers run-time debugging. Using the RemoteSetDebug method, you can set debugging for a session to one of three options:

Table 4. Options for Setting a Debugging Session

Option	Description
0	No debugging
1	Production Reporting Remote debugging messages are written to SQREMOTE.LOG in the current directory.
2	TOC-level debugging is turned on in addition to the Production Reporting Remote debugging.

For best results, turn on debugging immediately before the RemoteConnect call.

When you enable Production Reporting Remote debugging, messages are written to the SQREMOTE.LOG file in the current directory. If the file already exists, messages are appended to its end. The first message contains a time stamp. These messages show the steps that methods such as RemoteRun make. They also show the remote filenames and commands used. Note that some error messages (for example, "file does not exist on the server") are normal.

When you turn on TCP-level, several files with a DBG extension are created. These files contain information regarding the messages that are exchanged with the server. These messages can help you find problems.

Note:

When you turn on debugging, certain items such as passwords are written unencrypted to the log or debug files. Be sure to erase these files when you finish debugging remote operations.