RE: QLZARTV not returning license info as expected

Dave,

there are different ways of using IBM APIs. But from my perspective, it
always pays off to be consistent. You may care for the number of concurrent
users and you may not. But the most natural thing for an application program
to do is to request a licence using a proper API. You can, of course, do it
the other way round: never use this API but instead retrieve licence
information using a different API and check the expiration date (that's how
I read your message). 
Each way you have to use an API in the application(request a licence vs.
retrive licence information), otherwise the aplication would not be
protected.

So, you saved nothing in terms of effort, unless for some reason you find it
easier to retrive licence information than request a licence. But you
definitely created an additional problem: now you had to write an exit
program generating temporary keys. 

If you would like to further discuss it, I suggest we go offline.

Lo

> -----Original Message-----
> From: Dave Murvin [SMTP:davem@drme.com]
> Sent: Monday, June 05, 2000 11:46 AM
> To:   MIDRANGE-L@midrange.com
> Subject:      RE: QLZARTV not returning license info as expected
> 
> Lo,
> 
> At 09:20 PM 6/1/00, you wrote:
> >maybe I'm missing something, but then again, maybe you are. :-)
> 
> I have solved the problem.  Maybe we both missed something.
> 
> In you original post, you mentioned requesting and releasing a license in 
> all the applications programs to cause the number of users to be 
> exceeded.  Since I do not care about the number of users using the 
> application, I have just been checking the expiration date of the license 
> by retrieving the license information and not requesting/releasing 
> licenses.  The problem is that when you initially add the license 
> information to the product and create the product, the product expiration 
> date gets set to *NONE (never expires).
> 
> What I have done to solve the problem is different that your suggestion.
> I 
> have added an exit program to product that runs after RSTLICPGM.  The exit
> 
> program generates a temporary key that expires 30 days from the current 
> date for the serial number the program is being installed on.  This seems 
> to work for my purposes.  I can extend the temporary key or create a 
> permanent key for the product based on the serial number and never have to
> 
> worry about how many people are using the product.
> 
> I can see where your solution would work if I used the request/release 
> license process, but then I would have to code additional API calls and
> add 
> the request/release process to my applications.  I will keep your solution
> 
> in mind if I decide to go that way,
> 
> Thanks for the help.
> 
> Dave Murvin
> DRM Enterprises, Inc.
> davem@drme.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
> +---
+---
| 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
+---