Logical name "LINK" and user named "LINK"

Logical name "LINK" and user named "LINK"

Post by John E. Malmber » Tue, 15 Feb 2000 04:00:00




> Greetings.  We have a graduate student with the last name of "Link".  He
> has an account on one of our VMS systems (an Alpha 3000/400) that we have
> recently upgraded to VMS 7.2 from 5.5-2 (a complete reinstall actually,
not
> an upgrade).  It's now evidently no longer possible to send mail to Mr.
Link:

> MAIL> send/noself
> To:     link
> %MAIL-E-USERSPEC, invalid user specification ':LINKER64.EXE'

Until you resolve your problem, he can be addressed as _LINK as long as he
is not forwarding his mail somewhere else.

-John

 
 
 

Logical name "LINK" and user named "LINK"

Post by Michael Hanno » Tue, 15 Feb 2000 04:00:00


Greetings.  We have a graduate student with the last name of "Link".  He
has an account on one of our VMS systems (an Alpha 3000/400) that we have
recently upgraded to VMS 7.2 from 5.5-2 (a complete reinstall actually, not
an upgrade).  It's now evidently no longer possible to send mail to Mr. Link:

MAIL> send/noself
To:     link
%MAIL-E-USERSPEC, invalid user specification ':LINKER64.EXE'

It isn't hard to discern the cause of the problem:

$ show logical link
    "LINK" = "SYS$SYSTEM:LINKER64.EXE" (LNM$SYSTEM_TABLE)

I found one reference to LINKER64 on the net:

        http://www.veryComputer.com/

where it is suggested that this is somehow related to the ADX072 De* kit.

I couldn't find any more information about either LINKER64 or about ADX072.

I've done enough programming in my life to view de*s as useful tools,
so I presume we want whatever is the latest in debugging technology, but we
also would like to send email to Mr. Link.  Can we do both?

Thanks.

                                        - Mike
----------

Dept. of Physics
University of California        ucdhep::mike (42385::mike)  (HEPnet)
Davis, CA 95616-8677            530.752.4966 (Voice)        530.752.4717 (FAX)

 
 
 

Logical name "LINK" and user named "LINK"

Post by Frank Sapienz » Wed, 16 Feb 2000 04:00:00


Of course, you could also change his user name.  I doubt he would be upset
if you included his first initial either at the beginning or end, such as
LinkM.  After all, if you ended up with two users, both with last name of
Link, what would you do?  Most people would include one or more initials to
find uniqueness.


> Greetings.  We have a graduate student with the last name of "Link".  He
> has an account on one of our VMS systems (an Alpha 3000/400) that we have
> recently upgraded to VMS 7.2 from 5.5-2 (a complete reinstall actually,
not
> an upgrade).  It's now evidently no longer possible to send mail to Mr.
Link:

> MAIL> send/noself
> To:     link
> %MAIL-E-USERSPEC, invalid user specification ':LINKER64.EXE'

> It isn't hard to discern the cause of the problem:

> $ show logical link
>     "LINK" = "SYS$SYSTEM:LINKER64.EXE" (LNM$SYSTEM_TABLE)

> I found one reference to LINKER64 on the net:

> http://www.veryComputer.com/

> where it is suggested that this is somehow related to the ADX072 De*
kit.

> I couldn't find any more information about either LINKER64 or about
ADX072.

> I've done enough programming in my life to view de*s as useful tools,
> so I presume we want whatever is the latest in debugging technology, but
we
> also would like to send email to Mr. Link.  Can we do both?

> Thanks.

> - Mike
> ----------

> Dept. of Physics
> University of California        ucdhep::mike (42385::mike)  (HEPnet)
> Davis, CA 95616-8677            530.752.4966 (Voice)        530.752.4717
(FAX)

 
 
 

Logical name "LINK" and user named "LINK"

Post by Phillip Helb » Thu, 17 Feb 2000 04:00:00




> Until you resolve your problem, he can be addressed as _LINK as long as he
> is not forwarding his mail somewhere else.

More precisely, mail to _LINK will not be forwarded.  Handy for sending
someone an email saying that his forwarding address does not work!
 
 
 

1. Logical name "LINK" and user named "LINK"

The solution is fairly simple in this case. Remove the logical name and
define a symbol instead. If you do need a logical name restrict its scope
with, for example, DEFINE/USER. Logical names are useful but I'm sure
everyone has hit this problem at some time where a username happens to be
the same as some facility for which a logical name has been defined. It's
usually a bad idea to define commands with logical names: use a symbol.

John


Post: Nuclear and Astrophysics Laboratory, Keble Road, Oxford OX1 3RH,UK
Phone: +44-1865-273388 (direct)  273333 (reception)  273418 (Fax)

2. 2000 reject packets within 5 minutes. How to stop?

3. LINKING F90 programs leads to "multiply defined" and "undefined" CMA$TIS

4. Promise 2300+ EIDE in Warp

5. F$GETQUI("DISPLAY_JOB","LOG_SPECIFICATION",,"THIS_JOB")

6. leaving your PC on for extended periods

7. """The Art of Debugging"" Was: Compiler Optimisation problems"

8. BIND 8 Service wont start

9. """Problems!"""

10. How to type node"user pass"::"task=file.com" ?

11. How to "tell" all users (was: Re: Another 6.2 BACKUP "feature")

12. Decevent "add user" and "add external"

13. "-" as a valid logical name?