Re: swap profile handles... -- MIDRANGE-L

× 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 Mark,

What you describe is on my radar, as plan b, if I can't get the swap api's to work.

Mark S. Waterbury wrote:

Hi, Gerald:

Let the program adopt owner authority, and have the *PGM owned by a user profile that has the needed authority to that *OUTQ ... e.g.:

CHGPGM library/program USRPRF(*OWNER)
CHGOBJOWN OBJ(library/program) OBJTYPE(*PGM) NEWOWN(outqowner)

When the program runs, it will still have all authority of the user running the program, and will also adopt authority of the *PGM owner. (Adopting authority is "additive".)

IMHO, this may not be an appropriate use of the "swapping" user profiles approach.

HTH,

Mark S. Waterbury

> Gerald wrote:

I am trying to get spool files copied into a secure outq.
When I execute the swap (via QSYGETPH & QWTSETP) and run DUPSPLF, the
DUPSPLF ends with a CPF4244 - not authorized to output queue...

The user I am swapping to is the owner of the outq, and also has *all object authority on that object(the output queue)...

Could the problem be that the original user would fall in to the *PUBLIC *EXCLUDE authority?

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.