locked myself out of the system

[Christian Burschka]

Volker,

thanks,
what puzzles me , is that I only see a single startup.log;1 which does not explicitly show an error.

There is the normal line that interactive limit is set to 64 and a created process.
(Just as I normally see it on the blue screen, before the X window manager starts)

Is the problem the window manager ?

I just found in the docs:

Content starts here
HP DECwindows Motif
for OpenVMS Alpha
Release Notes
Previous Contents Index
2.5.8.3 Detached Processes Created by Default May Prevent Other Applications from Opening

V1.1

Applications created by FileView and Session Manager are detached processes.

The implication is that during application startup,
SYS$MANAGER:SYLOGIN.COM and SYS$LOGIN:LOGIN.COM command procedures are executed. Any command executed by these command procedures which reads from SYS$INPUT reads data intended to be used by FileView or Session Manager for the application startup.

>>>This prevents the application from
starting. <<<

Examples of such commands are INQUIRE, READ/PROMPT, and SET TERMINAL/INQUIRE.

etc etc.

As I run vms 6.2-1h3 may be I should begin to install a new system on a clean disk and update to 7.1 ?

Regards

Chris

[Volker Halle]

Chris,

did you check SYS$MANAGER:DECW$STARTUP_0.LOG and DECW$SERVER_0_ERROR.LOG for errors ?

Volker.

[Christian Burschka]

Volker,

thanks for this hint:

sorry I cant find a
SYS$MANAGER:DECW$STARTUP_0.LOG

but the recent
DECW$SERVER_0_ERROR.LOG
might be interesting:

it has a
... failed to attach transport DECNET
... no such device available.

and it is for several times
... closing screen down
...calling the dispatcher

sorry, I do not know how to send You the fairly long details...

The system formerly had two ethernet devices,
as I was not sure, if the second one is working, I took the card out, and configured ucx with only one interface.


Regards,

Chris.

[Volker Halle]

Chris,

looks like you don't have DECnet started at all. Does the previous DECW$SERVER_0_ERROR.LOG file show the same error ? And did DECwindows work at that time ? If so, no need to worry.

Otherwise, run @NETCONFIG and configure DECnet.

Volker.

[Christian Burschka]

Volker,

no, I didn't ever use decnet knowingly.

sorry to say that I only have two versions of
decw$server_0_error.log and they do not differ
except the time.

Regards

Chris

[Volker Halle]

Chris,

did you check DECW$SM.LOG in SYS$MANAGER ?

If you can't open a DECterm, try putting an $ EXIT into the first line of SYLOGIN.COM and LOGIN.COM

Did you try to run @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK ?

Volker.

[John Travell]

OK, a week late, and maybe a dead issue.
I suffered what seems to be a similar symptom when I incorrectly defined some logicals to match the device name I had put into UAF for the users login directory.
The net result was that login could not find my DECW parameter files, and the alleged place to write new ones did not exist, so DECW failed to start correctly, leaving me with only one window and essentially nothing else.
So, in your failed state, can you do a
$ dir sys$login: --- without error...
Do a '$ show default', and verify you are looking at a real disk and a directory you have the priv's to access.
If NOT, you probably will not find any logfile.
If this does match your problem, look in the UAF at your account to see where you should be logging into, then see if that disk is mounted prior to your login... Has a disk gone offline ? Have you changed something in systartup_vms.com ?