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


  • Subject: Release License API Code
  • From: "Bob Randall" <BLR@xxxxxxxxxxx>
  • Date: Tue, 9 Nov 1999 10:53:13 -0600
  • Importance: Normal

I am coding my first OS/400 Software API <oh the joy>, and I have what is
probably a very basic question.

You can read the detail below, or the summarized version is "What is the
License User Handle information in the LICL0200 format of the QLZARLS API
supposed to look like?"

The detail version is concerns the LICL0200 format used by QLZARLS. I am
trying to release a license for a single user, and the format calls for the
following:

Binary(4) Offset to user
Binary(4) Length of license user
Char(8) License user handle
Binary(4) Offset to additional license user info
Binary(4) Length of additional license user info
Char(*) License user
Binary(4) Number of uses held

All I know when I release the user in WRKLICINF is the user ID. Obviously I
am in the right product and so forth, but I don't care about the other users
that are remaining. What would this table look like (especially the License
user handle) to release a user ID of say "BOB"? Or is that not exactly what
it is intended to do?

TIA,
Bob Randall


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

Replies:

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.