topic Re: login.com to set symbol up in Operating System - OpenVMS

login.com to set symbol up

jpaulino05 — Mon, 14 Aug 2006 15:40:16 GMT

Hi guys,

Am using ADMIN to log onto the system. When going to my home it show the folowing:

$ sh def
SYS$SYSROOT:[SYSMGR]
= SYS$SYSROOT:[SYSMGR]
= SYS$COMMON:[SYSMGR]

So I have two login.com
One in SYS$SYSROOT:[SYSMGR]
and other in: SYS$COMMON:[SYSMGR]

I set some symbol up in both login files and neither of them is executed when I get into the system.

Q. How can I make the lines I put inside login.com get execute.

Thks a lot.

Re: login.com to set symbol up

Steven Schweda — Mon, 14 Aug 2006 17:37:47 GMT

If you have a root-specific
SYS$SYSDEVICE:[SYSx.SYSMGR]LOGIN.COM,
then no one will ever look at the common
SYS$SYSDEVICE:[SYSx.SYSCOMMON.SYSMGR]LOGIN.COM.

(Where "x" is normally "0".)

Depending on your circumstances, the best
answer may be to put everything into only one
of these files, and to delete the other.

Note that normally
SYS$SYSDEVICE:[SYSx.SYSCOMMON.SYSMGR]LOGIN.COM
is actually
SYS$SYSDEVICE:[VMS$COMMON.SYSMGR]LOGIN.COM.

Is this an individual system of part of a
cluster?

Re: login.com to set symbol up

John Gillings — Mon, 14 Aug 2006 18:35:09 GMT

You should probably only have ONE LOGIN.COM, in SYS$COMMON:[SYSMGR].

Only one procedure will execute. SYS$SYSROOT will be in preference to SYS$COMMON, but if you're in a cluster, SYS$SYSROOT is only for the current node. Usually it makes more sense to have a common login procedure in the SYS$COMMON root.

Test it with

$ SET VERIFY
$ @SYS$LOGIN:LOGIN.COM

It's possible your UAF entry specifies a different procedure. See

$ MCR AUTHORIZE SHOW ADMIN

and check the LGICMD field. If it's not blank, then that's the procedure you will execute on login. Otherwise it should be SYS$LOGIN:LOGIN.COM