www.grootersnet.nl |
WASD CGI loggingSuppose you get an error in some CGI procedure like this: %DCL-E-OPENIN, error opening DKA100:[APPLS]APP_ASSIGNS.COM; as input -RMS-F-DEV, error in device name or inappropriate device type for operation WASD has one more other great feature is that you can trace your DCL-code, used as CGI-script, as seen by the server, without even changing anything the code. Just specify a system logical and you will get the full code as has been executed on your screen. Be aware though that you won't see formatted output, just the HTML code: $ DEFINE /SYSTEM HTTPD$VERIFY 1 or, on a live server: $ DEFINE /SYSTEM HTTPD$VERIFY <dotted IP-address> and you'll see why. First, all server-generated symbols will be shown, and after that, each line as the server has executed. ... Eh? WEBTRACE wasn't defined - but still you get this trace. (It's because APACHE and OSU don't have thgis feature. They have to rely on defining this logical) $ assign/nolog base:keydef.xxx keydef This reference (DKA100:[APPL]) depends on data specified in the URL, and this way, it's easy to track it down. This is a simple one, but complex problems - mainly concerning the differences between SWS, OSU and WASD - were very easily found. It's priceless! |
(c) 2003- 2006 W. Grooters Last updated 16-11-2006 |