Re: Hobbyist License problems (was: Re: llcense problems)
From: Hoff Hoffman (hoff_at_hp.nospam)
Date: 01/28/04
- Previous message: Wilko Bulte,Arnhem - the Netherlands,+31-24-3529162,+31-26-3623823,TZ=WET From:: "Re: Alpha 4100 power supply"
- In reply to: Michael Grunditz: "llcense problems"
- Next in thread: Charlie Hammond: "Re: Hobbyist License problems (was: Re: llcense problems)"
- Reply: Charlie Hammond: "Re: Hobbyist License problems (was: Re: llcense problems)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 28 Jan 2004 21:35:40 GMT
In article <5d8887774c.michael@privat.utfors.se>, Michael Grunditz <michael.grunditz@telia.com> writes:
:Last time when I was forced to relicsense my OpenVMS hobbyist system
:I ended up in reinstalling the machine. I hope that there is another
:way, but I cant find out how.
When your licenses expire, boot conversationally on the console per
the information included in recent editions of the OpenVMS Frequently
Asked Questions (FAQ). Load your licenses. Reboot.
If you want to clean up the old licenses, you could delete them, disable
them, or re-create the entire license database and load the new licenses.
I generally save the text files containing the old licenses, as it is an
easy edit to the file to change the load commands into a collection of
disable commands.
I also tend to set a DECwindows calendar alarm or such, so I can go get
new licenses before the current ones expire -- and thus avoid having to
use the conversational bootstrap sequence.
:btw. is there a easy way to change the format of the license files
:emailed from montagar.com ? I allways ends up in haveing unuseble
:files whith no linefeed.
Unusable files with no line feed sounds like a file with a bogus record
format seting.
I haven't seen the file and particularly the record organization setting
involved with these (assumed) text files, but I'd be surprised if it
could not be cured with the approrpriate SET FILE/ATTRIBUTES command.
(I did just request some licenses and received some mail messages,
which would imply that however these files were exported to text and
hauled over to OpenVMS -- assuming the target system for the license
mail is not OpenVMS -- is the source of the record attributes mismatch.)
Are these (assumed) text files containing the licenses being transfered
through a Microsoft Windows system or another operating system, for
instance?
You might want to ask the montagar folks for help here, both in terms
of the license file format information (and commands needed to repair
the files) and for obvious enhancements like updates that zip the text
of the licenses.
Depending on the intermediate system, create a copy of the file on
OpenVMS, and try setting the copy of the file to use Stream Linefeed or
Stream CR with SET FILE /ATTR=RFM=STMLF or SET FILE /ATTR=RFM=STMCR.
OpenVMS questions are probably best asked in comp.os.vms, too.
---------------------------- #include <rtfaq.h> -----------------------------
For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq
--------------------------- pure personal opinion ---------------------------
Hoff (Stephen) Hoffman OpenVMS Engineering hoff[at]hp.com
- Previous message: Wilko Bulte,Arnhem - the Netherlands,+31-24-3529162,+31-26-3623823,TZ=WET From:: "Re: Alpha 4100 power supply"
- In reply to: Michael Grunditz: "llcense problems"
- Next in thread: Charlie Hammond: "Re: Hobbyist License problems (was: Re: llcense problems)"
- Reply: Charlie Hammond: "Re: Hobbyist License problems (was: Re: llcense problems)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|