[Info-vax] openvms licensing

[BillPedersen]

On Wednesday, February 17, 2016 at 8:15:31 PM UTC-5, Bill Cunningham wrote:
> "Jan-Erik Soderholm" <jan-erik.soderholm at telia.com> wrote in message 
> news:na30ie$fn2$1 at news.albasani.net...
> > Den 2016-02-18 kl. 00:35, skrev Jan-Erik Soderholm:
> >> Den 2016-02-17 kl. 23:45, skrev Bill Cunningham:
> >>> [snip]
> >>>
> >>
> >> [snip snip]
> >>
> >>>
> >>> It is a hobbyist PAK. 112 PAKs. The other email said to run it as above.
> >>> I can get the file onto VMS...
> >>
> >> And exactly HOW did you do that ???
> >>
> >> What do you see when TYPE'ing your file?
> >>
> >> Does it look OK with clean consecutive lines
> >> each starting with an $?
> >>
> >>
> >
> > Sorry, not *all* lines... Not the continuation lines
> > where the line before ends in a dash ( "-" ).
> >
> > The very first couple of lines should read:
> >
> > $!
> > $!                            HP HOBBY LICENSE AGREEMENT
> > $!                                    For OpenVMS
> > $!
> >
> > And then further below there should be 100+ sections
> > looking like:
> >
> > $!
> > $! This PAK issued on 18-Sep-2015 07:34
> > $ SHOW LICENSE ACMS/SINCE/NOOUTPUT/TERMINATION_DATE=dd-mm-yyyy
> > $ IF ($STATUS .EQS. "%X107880D3") .OR. ($STATUS .EQS. "%X107880CB")
> > $ THEN
> > $ LICENSE REGISTER ACMS -
> > /ISSUER=HP -
> 
> DEC -
> 
> > /AUTHORIZATION=HOBBYIST-xxx-xxx-xxx -
> > /PRODUCER=HP -
> 
> I don't think I have this. /PRODUCER
> 
> > /UNITS=0 -
> > /TERMINATION_DATE=dd-mmm-yyyy -
> > /OPTIONS=(IA64,PPL) -
> 
> I definately have no options.
> 
> > /CHECKSUM=2-xxxx-xxxx-xxxx-xxxx
> > $!
> > $ LICENSE DISABLE ACMS/LOG/PRODUCER=HP/ALL
> > $ LICENSE UNLOAD  ACMS/LOG/PRODUCER=HP
> > $ LICENSE ENABLE  ACMS/LOG/PRODUCER=HP/AUTH=HOBBYIST-xxx-xxx-xxx
> > $ LICENSE LOAD    ACMS/LOG/PRODUCER=HP
> > $ ENDIF
> > $ !
> >
> >
>     I do have an entry I believe called activity,
> 
> /ACTIVITY=CONSTANT=100
> 
> I have that yes. So manually with vmslicense.com is going to take some 
> getting used too.
> 
> I have several DV* PAKs and UCX and UCX* PAKs.  don't know all the ones I'd 
> have to enter for minimal functionality. There is one thing I haven't tried 
> I think may work. Loading into linux LDXE or Xfc. Something other than just 
> X which I have been told will work. I might be able to cut and paste there. 
> That will solve my problem. But I am trying many things.
> 
>     Thanks for your inquiry. Yes you can load via the card reader.
> 
> Bill

I am not sure where the IA64 PAK information came from...  You are running a VAX and the only thing that will work with it is VAX PAKs.  Here is an example of a VAX PAK for a product on VMS:

! This PAK issued on 26-May-2015 11:01
$ Call CheckLicense "ABS-CLIENT-ALPHA" "31-JUL-2016"
$ IF ($STATUS .EQS. "%X107880D3") .OR. ($STATUS .EQS. "%X107880CB")
$ THEN
$ LICENSE REGISTER ABS-CLIENT-ALPHA - 
/ISSUER=DEC - 
/AUTHORIZATION=ALLIANCE-1-VMS-160731 - 
/PRODUCER=DEC - 
/UNITS=0 - 
/TERMINATION_DATE=31-JUL-2016 - 
/ACTIVITY=CONSTANT=100 - 
/CHECKSUM=2-xxxx-xxxx-NFFB-KCLM
$!
$ LICENSE DISABLE ABS-CLIENT-ALPHA/LOG/PRODUCER=DEC/ALL
$ LICENSE UNLOAD  ABS-CLIENT-ALPHA/LOG/PRODUCER=DEC
$ LICENSE ENABLE  ABS-CLIENT-ALPHA/LOG/PRODUCER=DEC/AUTH=ALLIANCE-1-VMS-160731
$ LICENSE LOAD    ABS-CLIENT-ALPHA/LOG/PRODUCER=DEC
$ ENDIF

The checksum will not work as I have changed it but it does show you what you should expect for a similar environment.  This PAK for a Alliance-1 as I am a partner but the Hobbyist PAKs are similar but with something dealing with Hobbyist...

Good luck.

Bill.