James,

The last time I discussed this with an IBMer, the recommendation was to stop using givedescriptor/takedescriptor. Off the top of my head, I don't remember their reasoning.

They recommend using the sendmsg/recvmsg routines as a replacement.

-SK


On 2/26/2021 1:07 PM, James H. H. Lampert wrote:
Fellow geeks and geekettes:

We've got a customer that's been trying to work out a way to avoid
running our server from a user profile with *ALLOBJ authority (and I
think it's ideological, since the child-server jobs run under the
individual users' user profiles).

And I've just found a very large obstacle, the long-forgotten reason why
our product specs call for the server job to run with *ALLOBJ authority:

From a 20-year-old "UNIX-type API" manual:

The givedescriptor() function is used to pass a descriptor from one
OS/400 job to another OS/400 job.

To give a descriptor, the source thread must be running under one of
the following user profiles:
*   A user profile that is the same as the job user identity of the
target job
*   A user profile that has all object (*ALLOBJ) special authority

Have any changes since V4 relaxed this requirement in any way?

Is *OWNER authority on the program that calls "givedescriptor()" an option?

--
JHHL

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.