| I don't have any guesses about why you are seeing this problem,
but you will have a better chance of isolating it if you enable
image mode accounting on your VMS system. See the VMS documentation
for "set accounting /enable" for details.
When you quit a session, the session manager sends a message to the
job controller requesting that a new loginout job be run. Image
accounting should let you determine how far along this is getting.
If everything worked properly, you should see a new process created
running loginout, and then a successful loginout image exit status.
If the loginout image fails for any reason, image account should
record the exit status.
|
| This has been happening intermittently to me, too...
I enabled image accounting and found out the following:
When the login screen reappears, I see the window manager and my CHILD-created
DECterms terminate, and then the session manager. When it doesn't reappear,
the window manager and session manager terminate first, followed by the
DECterms.
When it works, I see the following image records logged for the session
manager process: DECW$SESSION.EXE exit with status = 1, LOGINOUT exit
with status = 1, follwed by the process termination with status = 1.
When it doesn't work, I see DECW$SESSION.EXE exit with status = 1, and then
the process terminates with status = 1. There is no LOGINOUT record. The
DECW$SM.LOG does not have the "CLEVELAND logged out at ... " message.
I am running SSB 5.2, I'm swimming in pool space, and have plenty of free
and contiguous global pages and pagefile space. I've autogen'd with FEEDBACK
recently.
I do create three DECterms (via CHILD) from DECW$LOGIN.COM. Is everyone that
is seeing this problem using CHILD?
Tim
Ps: There have been two QARs entered on this in the V5 database, so I didn't
add another.
|