From: pittam@mrluv2.dsto.oz.au
Newsgroups: comp.os.vms
Subject: Re: Invalid Login Information questoin (SAK 92_13)
Date: 7 Sep 92 01:58:49 GMT
Organization: Defence Science and Technology Organisation

Apologies if I am repeating responses already given - I tend to get a couple of
days behind when reading NEWS for some 75 newsgroups . . .

In article <01GOBM02SVAQ000OKQ@ACAD.DRAKE.EDU>, SK0001@ACAD.DRAKE.EDU writes:
> Hello All.
> 
>    In March of 91, we upgraded VMS from 5.2 to 5.4-2, and our VAX hardware to
>    the setup shown below. here is our current setup: 
> 

 *** unimportant stuff deleted (problem not related to hardware)

> 
>       Since the upgrade, we have experience some strange phenomena. I am 
>       listing them below. Can anyone help me diagnose and rememdy the 
>       situation ? Thank you all in advance.
> 
>    1- MAIL from KIRK to SPOCK and SPOCK to KIRK no longer displays receipt 
>       notification at the terminal.

You need to define/system/exec the mail$system_flags as summarised below -
        1 indicates homogeneous (single SYSUAF) cluster
      * 2 enables cluster breakthrough messaging for notification
        4 include the time of delivery in notification
        7 all of the above
We have ours set for 2,4 as we didn't always have a singe SYSUAF, but 7 would
be my general recommendation.  This will also stop users from getting "you have
new mail" but not being able to find it (read/new gets rid of this annoying
problem).  All of this is in the MAIL manual (p16 in mine).

> 
>    2- MAIL to SPOCK::USER from KIRK, or KIRK::USER from SPOCK no longer works.
>       It returns the errors:
>       "%MAIL-E-LOGLINK, error creating network link to node KIRK",
>       "-SYSTEM-F-INVLOGIN, login information invalid at remode node".
> 
>    3- PHONE from SPOCK to KIRK and KIRK to SPOCK no longer works. Phoning 
>       KIRK::USER from spock results in the "Establishing DECnet link..."  
>       Message, the PHONE utility returns the error "login information invalid 
>       at remode node"

The problems in 2 and 3 are related - and are caused by a mismatch of NCP and
SYSUAF passwords - the password shown with a ncp show/list object mail char
(need privs to see it) must match that found in the SYSUAF.  This problem was
given to me in my first week as SysAdmin (because nobody else could solve it -
not even Digital Support) as we had an Ultrix gateway (store and forward mail)
trying to send messages after one of our ops ran netconfig on a minor node in
the cluster.  It took some 6000 logfails before resolution.  This was fun
considering I had NO systems or VAX experience prior to this position !! 
Incidentally, SYSMAN is a great way of synchronising the NCP passwords, and I
suggest you check ALL objects.

> 
>    4- The DCL command REPLY/USER does not ALWAYS display a message on the
>       user's terminal on KIRK on occasion. I was unable to detect a pattern of
>       success or failure for this oepration.

? - set terminal/nobroadcast ?? some applications may do this automatically ??

> 
>    5- SHOW PROCESS/CONTINUOUS and SHOW PROCESS/ACCOUNTING no longer work if the
>       requestor process is on a different CPU than the target process.
> 

show proc/con would not, should not, could not work - cannot speak for show
proc/acc though, expect it would be the same.  Can it be done while in SYSMAN?

Hope this has been of some help . . .

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                       Adrian Pitt - Systems Administrator
DSTO Materials Research Laboratory - PO Box 50, Ascot Vale, VIC 3032 Australia
Telephone (03) 246 8779  Facsimile (03) 246 8999  eMail pittam@mrl.dsto.gov.au