[Info-vax] Updating expired VSI timed license

[Jan-Erik Söderholm]

Den 2023-07-21 kl. 14:31, skrev Simon Clubley:
> On 2023-07-20, Arne Vajhøj <arne at vajhoej.dk> wrote:
>> On 7/20/2023 1:58 PM, CCS Technology wrote:
>>> I don't see an answer at VSI online on initial review; thought I'd
>>> ask here before going to support because, why not.
>>>
>>> Does VSI VMS on Integrity (V8.4-2L2 U1) offer a means to install a
>>> new current license key if it is booted with an expired key?  Or do
>>> we need to do DVD boot standalone and use that to update the license
>>> on the drive before it will boot at all?   Got an RX2800 system that
>>> was parked on a  shelf until 7 months after its license expired and
>>> we just finally got new paks for it.   I just want to be ready to
>>> deal with the issue (first expiring base VMS license issue ever,
>>> thanks tons, VSI)...
>>
>> You should be able to:
>> - boot normally
>> - login via console (not via network - only via console)
>> - enter the new license manually (unpleasant typing but possible)
>> - reboot
> 
> On a related note, assuming the licences don't expire first, can you,
> during normal system operations, replace a licence that is _about_ to
> expire and then have everything carry on without a problem ?

It would surprise me a lot if a reboot would be required just for a
license update/renewal.

I think you just "load" the new license besides the old one and make
it active, then deactivate and remove the old one.
That is done on-line, as far as I remember...


> 
> IOW, does the always-running networking/VMS code read the licence expiry
> date during system startup and only check at that point (so that you
> can continue running on expired licences until a reboot) or is there
> anything that would force you to do a reboot or subsystem restart after
> new licences have been loaded ?
> 
> I think it's the former, but I can't be sure.
> 
> That obviously doesn't apply to things like compilers which check
> everytime you run one of the compilers.
> 
> Simon.
>