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
On 2024-04-10, Mark Daniel <mark.daniel@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.
On 2024-04-10, Craig A. Berry <craigberry@nospam.mac.com> wrote:
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.
Thanks Craig. I did not consider that possibility.
I wonder if that means none of the ISV people have got their licences yet
or if Mark has been silently dropped by VSI because he no longer qualifies (in the opinion of VSI, _NOT_ in my opinion).
BTW, did VSI manage to sort out licence access for you ?
On 4/10/24 12:25 PM, Simon Clubley wrote:
On 2024-04-10, Mark Daniel <mark.daniel@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.
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@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 ...
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@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."
*** 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>
On 4/10/24 1:21 PM, Craig A. Berry wrote:
On 4/10/24 12:51 PM, Simon Clubley wrote:
BTW, did VSI manage to sort out licence access for you ?
No. I applied for the new CL a day or two after the announcement, and
then, after thinking about it and looking over the requirements, I
applied for the ambassador program a few days later. No reply of any
kind to either as yet.
FWIW, I got a friendly e-mail from VSI today indicating I've been
accepted into the ambassador program and that licenses and additional
info will become available at some point as they work through their long
list of requests. So, the wheels are turning.
On 4/10/24 12:51 PM, Simon Clubley wrote:
BTW, did VSI manage to sort out licence access for you ?
No. I applied for the new CL a day or two after the announcement, and
then, after thinking about it and looking over the requirements, I
applied for the ambassador program a few days later. No reply of any
kind to either as yet.
FWIW, I got a friendly e-mail from VSI today indicating I've been
accepted into the ambassador program and that licenses and additional
info will become available at some point as they work through their long
list of requests. So, the wheels are turning.
------------------------------------------------------------------------------<
------------------------------------------------------------------------------<
On 4/10/24 1:21 PM, Craig A. Berry wrote:
No. I applied for the new CL a day or two after the announcement, and
then, after thinking about it and looking over the requirements, I
applied for the ambassador program a few days later. No reply of any
kind to either as yet.
FWIW, I got a friendly e-mail from VSI today indicating I've been
accepted into the ambassador program and that licenses and additional
info will become available at some point as they work through their long
list of requests. So, the wheels are turning.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 300 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 04:57:28 |
| Calls: | 6,706 |
| Files: | 12,236 |
| Messages: | 5,350,366 |