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

[VAXman- at SendSpamHere.ORG]

In article <na26c3$tjs$1 at dont-email.me>, David Froble <davef at tsoft-inc.com> writes:
>clairgrant71 at gmail.com wrote:
>> We must be on at least our fifth or sixth attempt at finalizing a very long release note but here is the basic idea.
>> 
>> "When booting into a cluster containing members running VSI OpenVMS V8.4-1H1
>> and members running any HPE version, a node may fail to load a valid license.
>> The failure occurs for products that are not licensed under the cluster's
>> Operating Environment License Agreement (BOE or HAOE).  For example, consider
>> VMSCLUSTER licenses purchased along with the VSI BOE and HPE FOE licenses."
>> 
>> For 8.4-1H1 you need a new LMF.EXE and you must execute a few LICENSE MODIFY
>> commands. For 8.4-2 you only need to execute the commands.
>> 
>> So, how did such a blatant, in-your-face problem escape our thousands of
>> hours of testing as well as everyday operation where we have 8.4 systems and
>> 8.4-1H1 systems clustered all the time? That is almost as interesting as the
>> problem itself. The embarrassing answer is that we didn't have the right
>> combination of operating environment licenses and individual product license
>> units in play to expose the problem.
>
>One word describes this.  "Murphy"
>
>> This will likely not be the last time something unforeseen arises regarding
>> multiple producers (VSI and HP) of products with the same name. It is just a
>> tough problem but we are gaining on it. BTW: Replacing the current licensing
>> scheme altogether is an on-going topic of discussion.
>> 
>> 
>
>That's good to know.  Sometimes things grow to the point of uselessness.

Well, I stumbled upon another bug/issue/feature which I've been informed will
require the installation of a patch for V8.4-1H1 to address it.  It's always
fun to be one of the early adopters/implementers.  Hopwfully, all of this can
be address quickly with this particular customer so that I can get back to
doing what they hired/asked me to do.
  
-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.