Log into the ALPHA02 (remote) system and look for the NET*SERVER.LOG file that typically gets created in the context of the target environment. This file will typically be created in the default directory of the target username; in the default directory for SYSTEM, here.
Look in this log file and see if there are any interesting errors listed there.
On no evidence, I'd assume there are DCL commands in SYLOGIN or in LOGIN.COM file used for SYSTEM username that are preventing the login sequence. (This is a fairly common mistake when unfamiliar with the sometimes cryptic and arcane world of DCL; this is a common corner case that most everybody has implemented and then had to debugg.)
To test this theory (and looking within NET$SERVER.LOG is part of this research), temporarily place the line "$ EXIT" at the top of each of the two files.
The LOGIN file is usually:
SYS$LOGIN:LOGIN.COM
when you're logged in as SYSTEM.
As for the system-wide login, issue the SHOW LOGICAL SYS$SYLOGIN command; that typically shows the file. The system may or may not have a system-wide SYLOGIN.
Here's something I posted on a related (and slightly more general) topic a week or so ago:
http://64.223.189.234/node/955I've preferred either "OpenVMS" or "VMS" as the name of the operating system; that's been what DEC, Compaq and HP have tended to use in the official materials. There are about a dozen (and variously different) V7.* releases around for VAX and Alpha systems.
[[[Decent Points are assured for helpfull answers.]]]
That phrasing doesn't necessarily mean what you had intended.
Stephen Hoffman
HoffmanLabs LLC
