7 Oct
2013
7 Oct
'13
6:37 p.m.
On Mon, Oct 7, 2013 at 11:31 PM, Cory Smelosky <b4 at gewt.net> wrote:
On Mon, 7 Oct 2013, Cory Smelosky wrote:
Let's assume you have no need for your prior accounting information...
$ SET ACCOUNTING/NEW_FILE/ENABLE=IMAGE
Execute the UUCP command(s) which fail.
$ ACCOUNTING/SINCE=TODAY
Post that output and let's see if there's anything revealing in there.
Also, you can $ SET ACCOUNTING/DISABLE=IMAGE because /ENABLE=IMAGE can
become a resource hog.
Doing so now.
I disabled TERM/INQ on login in SYLOGIN and the abort went away (ACCOUNTING didn't
have anything useful to say). I know I can disable it per-line/per-use but this was the
quickest test.
I've seen this screw lots of stuff. I have stuff in my personal LOGIN.COM that
configures the terminal they way I like it. I just wrap it in the following:
$ interactive = (f$mode() .eqs. "INTERACTIVE")
$ network = (f$mode() .eqs. "NETWORK")
$ batch = (f$mode() .eqs. "BATCH")
...
$ if (interactive)
$ then
$ set terminal ...
$ endif
Regards, Tim.