|
|
|||||||
When you have some bad code that stops the KiX interpreter, it will put the error message on the console. The problem is that the console closes before you get to read the message. The best way to troubleshoot and to get the message to stay on the console is to first open a DOS box. Then, from the DOS box, type the command to launch your test script. One can also pass an ERRORLEVEL to the LOGON.BAT from within KiX. The KiX EXIT command supports a parameter which in fact should always be included. If KiX bombs before reaching the EXIT 0 then ERRORLEVEL will be set to 1 by the error. The following bad code is used here as an example: code:It yeilds the following output:break on code:THe following BAT file is used to demonstrate:Microsoft Windows 2000 [Version 5.00.2195] code:@ECHO OFF [ 19. January 2003, 03:51: Message edited by: LLigetfa ] |