| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 599.1 | STOP/ID=0 works. | CADSYS::PRENTICE | Ed 225-4061 HLO2-2/G13 (E13) | Mon Nov 16 1987 13:26 | 1 |
| Sure. Just type "STOP/ID=0" instead of "LOGOUT".
|
| 599.2 | | BPOV09::GRAHAM | Dr. John | Mon Nov 16 1987 15:58 | 3 |
| Thanks. It does just what I want.
JG
|
| 599.3 | Not the same??? | BEES::SCHLIESMANN | I'd rather be driving a Titleist | Tue Nov 17 1987 13:18 | 4 |
| Several years back, I wanted to do the same thing, and remember STOP/ID=0
as not being the greatest alternative. STOP/ID=0 is not as "graceful" as
actually logging out. I believe that STOP/ID=0 does not perform some of
the cleanup that LOGOUT performs, and simply calls DELPRC.
|
| 599.4 | $ STOP /ID=0 does most things needed. | PASTIS::MONAHAN | I am not a free number, I am a telephone box | Wed Nov 18 1987 05:35 | 11 |
| If you have arrived at the DCL prompt by interrupting a running
programme with ^Y, then you might want to allow user mode exit handlers
to be run. Also it would be tidier to close files that DCL has open
for write access.
$ EXIT !run user mode exit handlers (if any)
$ CLOSE FILE1 !that was explicitly opened by DCL
$ STOP /ID=0
If this is part of a command procedure you will not want the EXIT
command, of course.
|
| 599.5 | how do I make my .COM do EXIT without EXIT ? | VIDEO::OSMAN | type video::user$7:[osman]eric.six | Wed Nov 18 1987 14:44 | 21 |
| > $ EXIT !run user mode exit handlers (if any)
> $ CLOSE FILE1 !that was explicitly opened by DCL
> $ STOP /ID=0
>
> If this is part of a command procedure you will not want the EXIT
> command, of course.
Interesting issue here ! If "EXIT" when typed at top level means to run
user mode exit handlers, and "EXIT" when typed at lower "@" levels means
to run user mode exit handlers and also return to previous level, what
command in a lower "@" level means ONLY run user mode exit handlers but
DON'T also return to previous level ?
I can think of implicit methods. For instance, if the "@" level merely
runs another program, the previous program's exit handlers will be
run, but what if the "@" wants to do it without having to run another
program. Other hacks might work too, like "@nl:", but it still seems
like a hack.
/Eric
|
| 599.6 | Exit without exiting? | CADSYS::PRENTICE | Ed 225-4061 HLO2-2/G13 (E13) | Wed Nov 18 1987 16:31 | 7 |
| > Interesting issue here ! If "EXIT" when typed at top level means to run
> user mode exit handlers, and "EXIT" when typed at lower "@" levels means
> to run user mode exit handlers and also return to previous level, what
> command in a lower "@" level means ONLY run user mode exit handlers but
> DON'T also return to previous level ?
Doesn't "STOP" do what you're asking? /egp
|
| 599.7 | | WINERY::THOMAS | The Code Warrior | Wed Nov 18 1987 20:08 | 3 |
| $ COPY _NL: _NL:
Just force the executation of another image.
|
| 599.8 | STOP is pretty severe! | CADSYS::SLATER | Ken Slater, SEG-CADsystems | Wed Nov 18 1987 22:26 | 3 |
| Re: .6
No, Ed, STOP does not do what he wants. STOP does not run exit
handlers. Check out your DCL dictionary...Ken
|
| 599.9 | having to run another image to exit this one is a cr | VIDEO::OSMAN | type video::user$7:[osman]eric.six | Thu Nov 19 1987 15:42 | 8 |
| re: copy nl: nl:
I already mentioned that yes, I could run another image, but that's a crock.
I want to exit this image but NOT run another. (For instance, my .COM
is about to do some non-image execution, such as OPEN/READ/WRITE/CLOSE
or a bunch of F$ stuff)
/Eric
|
| 599.10 | | VIDEO::LEICHTERJ | Jerry Leichter | Mon Nov 23 1987 22:32 | 7 |
| You don't have to do ANYTHING to force an image exit - when commands are coming
from a command file, the next DCL command executed, WHATEVER it is, will cause
user-mode run-down.
Why do you think you can't do a CONTINUE from a CTRL/Y handler?
-- Jerry
|
| 599.11 | Suppressing LOGOUT message | FOO::BHAVNANI | It's not a bug - it's a feature! | Wed Dec 02 1987 12:47 | 3 |
| Getting back to the original question, I've been happily doing
$ EOJ for years.
/ravi
|