#Failed To Execute
4 messages in this thread
Anyone know why "Execute dh0:s/finish-sequence" would fail with a
"Execute failed; no K directive" ? this happens when it's part of my s-s
(it's _been_ working, just recently started failing)… once it fails, I can
type it into the CLI just as it appears in my s-s and it works fine.
<baffled> Keith
sounds like it's getting parameters as an input… and there is no Key word.
got any "<" or ">" characters in your script? If so, they may be taken as a
replacement delimiter, and without a .K or .Key directive, cannot be
processed correctly. If you _must_ use the "<" or ">" characters, then use
the .Bra and .Ket keys to redefine the delimiters to something you're NOT
using. –Ben–
Hmm… the only thing I see in there is the _last_ line of "dh0:s/finish-seq"
and it's "endcli >nil:" but that's always been there… and like I said, if I
type "execute dh0:s/finish-seq" in the CLI directly, it works fine. hmmmm.
Thanks, I'll play with it some more. – Keith
Keith,
That will happen (I think) if the drive the script is on isn't ready yet.
Try a short delay, or even better, if you have the 1.3 MOUNT command, put the
line 'Mount = 1' in your mountlist for that drive.
-larry