🚀 go-pugleaf

Well, Harry Flowers suggested the following;

>>I'm stumped.  I'm trying to get the DECWindows Debugger to come up from another
>>account (other than my primary one).  I have security set as follows:
>>
>>DECNET HULK SYSTEM
>>DECNET HULK MUNROE
>>DECNET HULK DMC$INFO
>>DECNET HULK NEWSMGR
>
>Can you connect from HULK from another account?  When I've had this problem,
>it was because I hadn't defined the node in NCP on the workstation.  If
>HULK::MUNROE works and HULK::NEWSMGR doesn't (and you don't have *::MUNROE
>in there somewhere), then you've got me stumped.
>
>$ MCR NCP SHOW NODE HULK ! Should show you node HULK
>
>If it was defined, but not SET, you can do a NCP> SET NODE HULK ALL
>

The ncp database defines HULK as:

Node Volatile Summary as of 29-SEP-1992 11:51:43

Executor node = 1.1 (HULK)

State                    = on
Identification           = DECnet-VAX V5.4-1,  VMS V5.4-2

The SCS node name is HULK and the SCS system is 1025 (which from my tribal
recollection is correct (area*1024+decimal = DECNET NODE NUMBER)

I tried adjusting the protections on the various SYS$SYSTEM:NET*.DAT
files with no effect (as expected).  I also tried replacing the HULK
designation by 1025 (the decnet node number) with no joy.

I CAN get it to work by using *::NEWSMGR in the security settings (or *::*)
which works for me (in my shop, security isn't an issue), but I'm still
immensely puzzled by why the checking for the node is messing up.  I have to
assume that it has SOMETHING to do with the way DECnet/DECWindows is
configured, but what in the world it could be is a really question.

Still stumped, but making progress.
-- 
Dick Munroe				Internet: munroe@dmc.com
Doyle Munroe Consultants, Inc.		UUCP: ...uunet!thehulk!munroe
267 Cox St.				Office: (508) 568-1618
Hudson, Ma.				FAX: (508) 562-1133

GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection.