× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Displaying License Keys
  • From: "Carsten Flensburg" <flensburg@xxxxxxxxxx>
  • Date: Fri, 4 May 2001 13:24:16 +0200
  • Organization: Novasol Data AS

Hello Neil,

You could use the outfile option of the DSPLICKEY command: DSPLICKEY 
OUTPUT(*LICKEYFILE)  LICKEYFILE(LICKEY) - the license key value is part of the 
information retrieved. The QLZARTVK API (Retreive license key information) is 
another option.

Best regards,
Carsten
 
----- Original Message ----- 
From: <owner-midrange-l@midrange.com>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, May 04, 2001 11:14 AM
Subject: RE: Displaying License Keys


> 
> 
> DSPLICKEY PRDID(5769RG1)
>           LICTRM(*ALL)
>           FEATURE(5050)
> Subject: Displaying License Keys
> 
> 
> Anyone know of a way to display the 18 byte license key that has been
> entered via ADDLICKEY ?
> (Maybe a DMPOBJ of the *PRDLOD object  - although I can't seem to see it
> there).
> 
> We have a customer who has licensed RPG & Dev Tools.  As is all too
> common, IBM's records are screwed up and they don't show the customer
> having Dev Tools - yet the license key has been entered on the system with
> *NOMAX for users - and who else BUT IBM could have given them the license
> key in the first place ?  I figure if we tell them the license key they'll
> have to admit the customer must have been licensed for it and fix their
> records.  I wouldn't have thought they would have made it difficult to
> display the key - after all, it's only good on the system you would be
> displaying it from.
> 
> Yes the customer screwed up and can't locate the paper with the license
> key or the "proof of purchase" document that IBM ships in that garish pink
> & black striped cover (hoping I suppose that it will be seen and kept -
> but maybe it was spotted by the fashion police and thrown out).
> 
> ...Neil
> 
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
> 

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.