define logicals in sylogin.com (urgent)

[hf.yao]

I defined a logical in sylogin.com like:
$ define/sys/exec HOSTSTR AAA
After system startup, when I
show logical HOSTSTR*, there are two entries:
(LNM$SYSTEM_TABLE)
"HOSTSTR" [super] = "AAA"
"HOSTSTR" [exec] = "AAA"

How this happened?

[Steven Schweda · Accepted solution]

> I defined a logical in sylogin.com like:
> $ define/sys/exec HOSTSTR AAA

SYS$MANAGER:SYLOGIN.COM? Really? _Everyone_
runs SYS$MANAGER:SYLOGIN.COM, and most users
can't do /SYSTEM, so this seems (to me) to be
a poor idea.

> How this happened?

I can't see all the command procedures which
your system runs at system start-up. Logical
names could be defined in very many places.

What, exactly, would you _like_ to happen?

[Hoff]

Guessing about a number of things around what happened here and also around what you want to have happened here, the correct location for this logical name definition should be over in SYLOGICALS.COM, and not in SYLOGIN.COM.

Placing a privileged operation in SYLOGIN will have differing results, particularly depending on the privileges in use when each of the users log in and invoke SYLOGIN.

[Robert Gezelter]

hfyao,

I must concur with Hoff, this definition most likely should be in SYS$MANAGER:SYLOGICALS.COM, which will be executed during the system startup (and which will then be available to all users. (An equivalent system wide logical name may already be available, SYS$NODE, so it may be simpler to use the existing name.)

As to why TWO definitions (one supervisor, and one executive mode)? From the HELP TEXT (fr DEFINE/EXECUTIVE):

"If you define the /EXECUTIVE_MODE qualifier, and you do not have SYSNAM privilege, the DEFINE command ignores the qualifier and creates a supervisor-mode logical name".

Two different users created the two logical names: one with SYSNAM, and one without SYANAM.

As noted earlier, define the name once in SYS$MANAGER:SYLOGICALS.COM.

- Bob Gezelter, http://www.rlgsc.com

[hf.yao]

grate