HP3000-L Archives

January 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"VANCE,JEFF (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
VANCE,JEFF (HP-Cupertino,ex1)
Date:
Mon, 24 Jan 2000 15:08:27 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
> !JOB TEST,MGR.DBUG
> !EDITOR
> T TEST
> EXIT
> ABORTTHISJOB
> !ECHO SHOULD NOT GET HERE
> !EOJ
>
> I think this job should exit out of Editor and abort on the
> ABORTTHISJOB command.  On our current system (mpe 5.5.7) the ABORTTHISJOB
> command disappears and the job processes the ECHO and EOJ.

I agree, even though the ABORTTHISJOB statement is missing the leading
exclamation mark ("!"), that this appears confusing.  BTW, the missing
! is quite important because it tells the CI that the next command is
expected to be a CI command, and not a left over EDITOR command.
After all processes (run by the CI) terminate, the CI flushes $STDIN until
it encounters the first command with a leading "!", or more accurately,
until
the input spooler "pseudo colon" is found in column one.  The CI does this
to prevent a job from aborting in cases where the program that was just run
did
not read all of its $stdin input.  If you put a leading "!" in front of the
bogus command name all should work fine.

regards,
Jeff Vance, CSY

ATOM RSS1 RSS2