|
Dan, At 08:56 AM 6/5/00, you wrote: >Please do not go offline with this topic. This definately holds my >interest. I can't speak for anyone else, but I think we are through. I have learned more about the Software product APIS and how they work for tracking usage. Although I may re-evaluate how I am using the APIs in the future or if problems arise during testing at client sites, I think I will stay with the way I am using the APIs for the following reasons: The manuals suggest that when you Request a product licence, you first Retrieve the license information to check the license handle against the license handle that was generated during the Add Product License process. The retrieve license information API returns, among other information, the product license handle and the license expiration date. Each of my main application programs calls this API during the *INZSR process to verify the license handle and that the license has not expired. As far as I can tell, this gives me all the license information I need and I do not need additional calls to the Request License and Release licence APIs. Remember that I am not tracking usage, only that I have a valid product license. The only fly in the ointment is that I had to create an exit program for the install process that generates a temporary key because the default license has no expiration date (without using the methods previously described by Lo and others). The exit program wasn't too much trouble because I already had code for retrieving serial number and generating the permanent license. So, by generating the temporary license one time, I reduce the number of license API calls for each application program from 3 to 1. I did have to generate my own "demo will expire on xxxx" type messages, where the Request license API generates these error messages for you. I guess the final reason is that my results are good enough for my purposes and I have spent enough time on this project. I want to move on to WebSphere and Java. 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 +---
As an Amazon Associate we earn from qualifying purchases.
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.