Installation guide

Application Debug Strategies
FlashCONNECT Administrator’s Guide 151
3. Use the tandem command to connect to and debug the FlashCONNECT
application.
4. Tandem to the port before running the application, so when the connection is
made, the application is already being observed.
Debugging w3Monitor
When w3Monitor detects a FlashCONNECT port in either the system or Pick BASIC
debugger, it removes the connection automatically unless this feature is overridden
by enabling debugging.
For more information, refer to the options listed in the topic w3Apps
in the
FlashCONNECT Programmer’s Guide; or in w3DebugOK API found in the
FlashCONNECT Programmer’s Online Reference
to modify this feature.
Recording Outgoing HTML Code and Incoming
Variables
FlashCONNECT supports the ability to record the HTML information sent to the
browser and all of the variables returned from a Web page. This ability facilitates
resolving intermittent and complicated problems. The w3Debugging tool controls
FlashCONNECT’s capability to record in the w3Logs,Dump file, outgoing HTML pages
and incoming environment and Web form variables.
Port x in debugger, connection removed
CAUTION—If you are debugging a program in FlashCONNECT and heartbeats are
being used, the heartbeat may not be processed. If w3Monitor is running
and the heartbeat is not processed, the w3Monitor may log off the
program being debugged. To avoid this, turn on FlashCONNECT debugging
as described in Using the FlashCONNECT Server Debug Program
.
NOTE—If D3 performance slows while w3Monitor is checking server pool
connections, verify that the dm,jobs, and run-time errors files are properly
sized. If it is not properly sized, correct the size or delete the completed
jobs (use the clear-jobs command).