Re: Software Product APIs

["Carsten Flensburg" <flensburg@xxxxxxxxxx>]

Hello Bill,

Here you'll find a redbook offering some details and code examples:
http://publib-b.boulder.ibm.com/Redbooks.nsf/9445fa5b416f6e32852569ae006bb65
f/8aceafed2db0e9968525659d002a566b?OpenDocument

Best regards,
Carsten Flensburg

----- Original Message -----
From: <bill.reger@convergys.com>
To: <Midrange-L@midrange.com>
Sent: Wednesday, December 05, 2001 10:31 PM
Subject: Software Product APIs


> 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.
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>