[Info-vax] openvms licensing

[johnwallace4 at yahoo.co.uk]

On Thursday, 18 February 2016 01:47:49 UTC, Bill Cunningham  wrote:
> "BillPedersen" <pedersen at ccsscorp.com> wrote in message 
> news:8b64bd77-a8e8-4785-b236-a588e3b4bf7b at googlegroups.com...
> 
> ok, from the sound of this and others later it suggests you have either 
> loaded some initial licenses or you just booted on a workstation and so you 
> have the minimal DECwindows environment.
> 
> The issue with loading the ASCII PAKs is that you need to do this in such a 
> way that you do not break the command lines.
> 
> This can be done by either having a window which is more than 80 characters 
> wide (and terminal characteristics know that) or by setting the terminal 
> /NOWRAP.
> 
> Then, you need to take the PAK and do a WINDOWS or LINUX "cut and paste" 
> where you open the PAK in an editor of your choice on your NON-VMS 
> environment.  Select the contents and "copy" them to the paste buffer.
> 
> Now go to your VMS system.  Start an editor (like by typing "EDIT 
> pak_file.com") to receive the contents of the PAK.  Now, PASTE the contents 
> of the PAK file into the editor screen.  You should then eventually see at 
> the bottom of the file something like "end of PAK file" or similar.
> 
> Exit the editor.
> 
> invoke the new command file:
> 
>     @pak_file.com
> 
> It should then work its way through loading the new PAKs for the software.
> 
> Now IF you get an error you need to copy it so we can help you by showing 
> the entire error.
> 
> An alternative to using an editor is to use CREATE.  To do this type:
> 
>     CREATE pak_file.com
> 
> Then repeat the paste operation.
> 
> After the paste as completed do a Control-Z to exit the CREATE command.
> 
> Then execute the command procedure like above.
> 
> Good luck.
> 
> Thanks much. There's 3 things I'm trying to do here. So if you think I'm 
> wasting your time that's fine. It sounds like your using some kind of 
> desktop. I'm trying not to resort to that. But I can. I am in console mode. 
> I install Xterms and I'm not getting anywhere there so I will install more. 
> In console mode, just loading a few PAKs sounds like the way to go. I'm a 
> purist :) I guess you can say.
> 
>     I'm also trying to get the files into the OS through simh without 
> damaging them. As you say that's difficult. I have several DV* PAKs and UCX 
> PAKs too. I might have to load them all. There is a VAX-VMS PAK. I am 
> assuming as others have sounded like they've said, that's the main PAK for 
> functionality. Minimal functionality.
> 
>     Learning that vmslicense.com syntax can be hairy. So I know where to put 
> activity now and for me it's always
> 
>     constant=100.
> 
> From Xterms I can't envelope all the text in dark image to cut it and paste 
> to the next xterm window. That's not going anywhere. I will log all further 
> attempts.
> 
> Bill

VMSLICENSE.COM for two PAKs entered by hand (the base OS one which
you have been provided, whose name is not known to us, and similarly
the networking one) has been suggested already by multiple people.

That approach is probably a whole lot simpler (albeit more tedious)
than whatever you're currently trying to achieve with "cut and paste
in Xterms" (for which, some weeks later, we are still awaiting the
*exact* details, and you are seemingly still ignoring the
trustworthy known-to-work suggestions from people here and
elsewhere).

It might even be simpler and less error-prone (for small amounts
of data, such as the data from one or two PAKs) than the various
"media transfer" approaches which people have been helpfully 
offering.

Once you've got VMS and networking PAKs registered successfully, 
*then* worry about cut+paste in xterms, and other such delights.

Keep it simple, see.

Best of luck.