× 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.



We are looking to license our software with expiration dates and the like,
and therefore, I have begun to look through the Software Product APIs
manual.  Talk about having a headache!  Can someone give me a brief
overview of what APIs I need to use and which I don't?

I am fairly sure I need to work with these APIs (but please correct me if
I'm wrong!):

Create Product Definition (ASZCRTPD) API
          (to create the *PRDDFN object that I must include with my
software)
Generate License Key (QLZAGENK) API
          (to generate the license keys that my customers need to know to
use/install the software)
Retrieve License Key Information (QLZARTVK) API
          (to retrieve license key information in the software to verify if
expiration date has passed)

Do I need to use the Package Product Option (QSZPKGPO) API to create my
software deliverable?  Or can I just use the normal deliverable creation I
have always used (save files to CD/Tape) and include the *PRDDFN object in
my deliverable?  What about National Language support?  How is this done?
Must I use the PTF APIs to issue fixes?

I realize I'm babbling here.  There are a load of APIs in this manual (more
than 25!), but I don't want to spend my whole (working) life to get all
this going.  I can (and already have) written code to generate my own keys
based on my own imagination.  But these APIs are certainly more foolproof
if I can understand them and justify the time.

Thanks for any assistance!  Bill

--

NOTICE:  The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential.  If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.