The following methods can be used to debug dynamic applications.
Within the application, use the w3Log subroutine to log important information to the w3Logs file.
Within the application, display diagnostic information to the screen.
Use tandem or WWW-TANDEM to connect to the phantom process running the application and observe what is happening.
Leave the diagnostic messages in production code to assist debugging at client sites.
When the w3Debugging tool is enabled, the incoming values of the request are displayed but the CGI variables are not. When a reply is sent, the outgoing data is displayed. See Enabling and Disabling the w3Debugging Tool.
The run-time impact is limited to the time it takes to display the diagnostic messages to the non-existent terminal.
Within the application, use the Pick BASIC debug command to place the application into the debugger.
Use tandem or WWW-TANDEM to connect to the phantom.
Use standard debugging techniques to debug the application.
Start WWW-IRUN from TCL and debug the application as you would any other application. Since the options for WWW-IRUN change with each release, the options can be determined using the list-jobs command to view the phantom processes started by WWW-START.
See Also
Debugging and Diagnosing FlashConnect Configuration
Diagnosing FlashConnect Configuration Problems (D3 Only)
Running the Loop-Back Test (D3 Only)
Static Application Debug Strategy
Determining if the Application is in the Debugger
Using the FlashConnect Server Debug Program
Recording Outgoing HTML Code and Incoming Variables
Testing FCService on a Specified Machine and Port
Logging Diagnostic Messages for FCService and FCSocketServer
Examining CGI and Form Variables