[Info-vax] %SHOW-I-NOLICENSE, no licenses exist

[Dave Froble]

On 4/11/2024 3:57 PM, Mark Daniel wrote:
> On 11/4/2024 06:22, Mark Daniel wrote:
>> On 11/4/2024 03:09, Craig A. Berry wrote:
>>> On 4/10/24 12:25 PM, Simon Clubley wrote:
>>>> On 2024-04-10, Mark Daniel <mark.daniel at wasd.vsm.com.au> wrote:
>>>>>    Welcome to OpenVMS (TM) x86_64 Operating System, Version V9.2-2
>>>>>
>>>>> Username: system
>>>>> Password:
>>>>> %LICENSE-I-NOLICENSE, no license is active for this software product
>>>>> %LOGIN-S-LOGOPRCON, login allowed from OPA0:
>>>>> VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, V9.2-2
>>>>>       Last interactive login on Thursday, 11-APR-2024 01:02:15.51
>>>>>       Last non-interactive login on Tuesday,  9-APR-2024 11:41:55.28
>>>>>
>>>>> X86VMS$ show license
>>>>>
>>>>> Active licenses on node X86VMS:
>>>>> %SHOW-I-NOLICENSE, no licenses exist
>>>>>
>>>>
>>>> It's not clear what you are trying to say Mark.
>>>>
>>>> Is this the VSI VM image that has suddenly stopped working ?
>>>>
>>>> If so, I would start by checking the time on the host machine is
>>>> set correctly. Assuming you have already done that, are there any
>>>> recent changes you have made ?
>>>>
>>>> The other possibility is that the licence database is corrupt. Can you
>>>> examine it successfully with the LICENSE LIST command ?
>>>
>>> I think it's more likely he's just letting folks know he doesn't have
>>> new licenses yet even though he's in the ISV program.
>>
>> Indeed Craig, Simon.  My regrets over the terse post.  I was just heading
>> towards bed, rebooted the system and bang.  I have placed an issue with the SP
>> and already received a response, although as yet remains unresolved.
>>
>> I was aware new licenses would be required at 1-MAY-2024 and the system has
>> been warning "%SHOW-I-TERMIMM, 10 licenses have terminated or will terminate
>> in 30 days".  It's just I imagined 1-MAY-2024 would not mean 11-APR-2024 and
>> rebooted.
>>
>> Incidentally, the SP list of packages available to my account went from a
>> couple of pages down to *eight* items at the beginning of the week (most of
>> which seem irrelevant to my use).  I had assumed it was something to do with
>> the current CLP shakeup.  Was about to chase that up ...
>
> *** mea maxima culpa ***
>
> With the looming license termination at 1-MAY-2024 and no word from VSI, earlier
> in the week I was playing - yes, playing - with the LICENSE command and issued
>
> $ LICENSE ISSUE <blah>
>
> without checking the documentation first.  HELP clearly states
>
> X86VMS$ help license issue
>
> LICENSE
>
>   ISSUE
>
>        Produces a replica of a Product Authorization Key (PAK) that
>        is sent to a file or displayed on your terminal (the default).
>        If the terms and conditions of your license contract allow it,
>        you can then enter this PAK replica in the License Database of
>        another processor. When you enter LICENSE ISSUE, LMF disables
>        the license in the current License Database and marks the license
>        DISABLED. To enable a license that has been marked ISSUED, enter
>        LICENSE ENABLE.
>
> To borrow a line from Angela in The Meaning Of Life (1983),
>    "I'm most dreadfully embarrassed."
>

Well, yeah, and I got bit by that same issue many years ago.  One learns 
quickly, after the first time.

Gotta keep amateurs away from OPA0 ...

:-)

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486