Article View: vmsnet.internals
Article #331Re: SET WATCH
From: Ian Kitching System Manager
Date: Fri, 02 Oct 1992 11:00
Date: Fri, 02 Oct 1992 11:00
12 lines
825 bytes
825 bytes
Problem solved! I used the Debugger to step through and found my problem is due to a command parsing quirk. The "SET WATCH" part invokes SETWATCH.EXE via a syntax clause, as one would expect. SETWATCH then does CLI$GET_VALUE for the WATCH_OPTION and tests if it is "FILE", no abbreviation allowed. It doesn't do anything if the test fails. Since I (almost) always abbreviate interactive commands, I've been typing SET WAT FI(L)/CL=... Ian Kitching systimk@va.anglia.ac.uk
Technical Details
Message-ID:
<8454167@MVB.SAIC.COM>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!news.service.uci.edu!unogate!mvb.saic.com!macro32Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!usc!news.service.uci.edu!unogate!mvb.saic.com!macro32 From: "Ian Kitching, System Manager" Newsgroups: vmsnet.internals Subject: Re: SET WATCH Message-ID: <8454167@MVB.SAIC.COM> Date: Fri, 2 Oct 92 12:00 BST Organization: Macro32<==>Vmsnet.Internals Gateway X-Gateway-Source-Info: Mailing List Lines: 12