|
Do you need an actual date of expiration, or a duration of time in which the product can be used? If a duration, then you could use the OS/400 Software Product APIs to build your product as *KEYED compliance and then specify a grace period (0 to 999 days) for the product. You would not need to specify a serial number in this situation. This approach is intended for those "try-and-buy" type of situations. For further information, see the Software Products chapter of the System API Reference. The above is not to say you cannot also use a specific date, just that I don't know how off the top. Bruce Vining > >Hi > >I'm looking for a way to include some sort of key license control into >our application product. My first thought was of IBM's SystemView >SystemManager. The problem is I have not got it installed, and judging >by the documentation it only allows to license a product for a computer >with a given SERIAL NUMBER. Is that true, or is there a workaround? We >don't care about the serial number, what we need is for the product to >just have an expiration date. >Any ideas are welcome. > >Lo > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@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.