[Info-vax] HP Integrity rx2800 i4 (2.53GHz/32.0MB) :: PAKs won't load

[VAXman- at SendSpamHere.ORG]

In article <584e2fc4-b5fc-4f2b-90c4-2c606e3ae539 at googlegroups.com>, Hans Vlems <hvlems at freenet.de> writes:
>/NO_SHARE has no purpose on non clustered nodes. Brian wrote in his first post that the second node failed AND that it was at that point standalone, not part of a cluster.
>BTW telling VAXman how to use a PAK is like telling Eddy Merckx how to ride bike.

There are a number of issue in play in the particular case I posted about.
The first is V8.4-1H1.  The PAK issue has been sussed out and required NO
/OPTION or /INCLUDE modifications.  There are now some other bugs that have
to be address with patches.  The customer is trying to get me all of their
SAID and RAS (?) numbers so that I can get the patches from HP to address
the problems.

FWIW, mucking about with all of the PAKs was NOT really necessary.  Trying
all sort of LICENSE command permutations didn't address the reason that I'd
gone down the path in the first place.  The problem is address in a patch
for LOGINOUT.  It was all a red herring seeing:

DEC VMSCLUSTER license is not active

...and...

%%%%%%%%%%%  OPCOM  18-FEB-2016 06:39:22.68  %%%%%%%%%%%
Message from user AUDIT$SERVER on NODE1
Security alarm (SECURITY) and security audit (SECURITY) on NODE1, system id: 1025
Auditable event:          Remote interactive login failure
Event time:               18-FEB-2016 06:39:22.68
PID:                      2020044E        
Process name:             _TNA15:         
Username:                 SYSTEM          
Process owner:            [SYSTEM]
Terminal name:            _TNA15:, Host: LOCALHOST Locn: _OPA0:/SYSTEM
Image name:               NODE1$DKA0:[SYS0.SYSCOMMON.][SYSEXE]LOGINOUT.EXE
Remote node id:           16777343
Remote node fullname:     LOCALHOST
Remote username:          TELNET_7F000001
Posix UID:                -2              
Posix GID:                -2 (%XFFFFFFFE) 
Status:                   %LOGIN-F-NOVAXCLUSTER, DEC VMSCLUSTER license is not active

... mucking about for days with the PAKs until everything, including me, was
so confused did nothing because the above is a bug!

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.