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



Basically comes down to the fact that you shouldn't be creating a child job
for a specific user profile.

Instead, you'd have a generic no special authority profile (think QUSER,
QTMHHTTP, ect ) and the SPAWN'd job, given the connecting user's ID and
password, would do a profile swap to that user's ID.

Thus the reason IBM has (since v3? v4? v5?)
- changed WRKACTJOB to show Current_user instead of JOB USER
- included current user in the program status data structure.

My $0.02
An *ALLOBJ server job and child jobs that showed under a specific JOB USER
profile, might have been an option 20 years ago.
But it's not the way it should work today.

Charles


On Thu, Mar 4, 2021 at 12:42 PM James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

With no apparent way to make spawn/sendmsg/recvmsg work for creating
entirely separate child-server jobs under a specified user profile, at
least not without months of re-engineering the sign-on protocol for the
application, I found a few minutes to test my idea of having the
"verification-server" program run under owner authority.

And it actually works!

At least under V6. Of course, that's no guarantee that somebody trying
to make life as difficult as possible for those still using
givedescriptor/takedescriptor hasn't deliberately broken this in V7, but
at least I have proof-of-concept.

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com


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.