|
Well, since no one else has taken a stab at this, I'll try.
I (and other memebers of the group) have an opinion that Cobol would
most likely not be a good language in which to write code that runs in
Exec mode. You might want to poke around the CLT::COBOL notesfile and
see if anyone there has a differing opinion.
As far as ACMS goes, there's lots of Exec mode code in the server. The
message switch software all runs in Exec/Kernel mode. RDB also runs in
Exec mode. The problem you might run into might be in the passing off
from EXC to TWP (the main part of a procedure server). EXC calls TWP
and waits for it to return. TWP then calls the routine specified in
the processing statement and waits for your code to return to it. The
place where I see a problem is in the task cancel. If a task is
cancelled for some reason (operator, user, etc.), EXC will attempt to
cancel the call to TWP, using a user-mode AST. Since you are executing
in EXEC mode, that AST will not be delivered until you drop back to
USER mode. If your code is well-behaved then things will probably
work properly. But, as you have already seen, if you get stuck in
EXEC mode, you cannot delete the process. It is also possible to
bugcheck VMS while in EXEC mode.
Can you explain what it is you're planning on doing in this elevated
mode code? I'm sure others would be interested.
Bill
|