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



Thanks for the reply Scott.

The reason I asked about the maximum size is that the maximum size of a user index entry is 2000.

Not sure that qsort will solve my problem. Doesn't it expect a structure with fixed length entries?

Thanks

Paul

Scott Klement wrote:
On Tue, 24 Jun 2003, Paul Tuohy wrote:

I am using the QSYLOBJA (List Objects a User is Authorized to, Owns, or
Is Primary Group Of) with format OBJA0110 to retrieve a list of IFS
objects owned by a user profile.

The returned list is not in any sequence. Any suggestions as to the best
way to get it into name sequence? (Database, User Index.......)


I think I'd probably use qsort()  Though, a user index might also be a
possibility.


Also, any idea what the maximum size of a path name is?



I didn't think there was a maximum size?   It's probably a good idea to
use a method that doesn't limit you to a certain size if that's possible.

I assume that this API returns data in the standard "list API" format?
If so, the API should return header information into the user space, one
of the fields in that header info should be the "size of each entry".
Then, use that "size of each entry" to create your temporary user index,
and/or to be the size used by qsort(), etc.

That's why I prefer these methods over a database.  You don't have to
hard-code a limit to the size of the pathnames...



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.