RE: QLZARTV not returning license info as expected

[Dave Murvin <davem@xxxxxxxx>]

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
+---