RE: Authority to start a writer at the user level

I don't have any issues with a CL running adopted authority, it's a best
practice if I'm not mistaken. I just think that changing the outqueue
and device descriptions is easier. But now that I know that's not going
to work, I'll proceed with the CL approach.
Bryan Burns

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of jmmckee
Sent: Tuesday, October 05, 2010 3:42 PM
To: Midrange Systems Technical Discussion
Subject: Re: Authority to start a writer at the user level

User would also either have to have a CL program behind a menu or not be
a limited user.

Curious: What do you not like about a CL running adopted authority?
Certainly could be an issue if the CL contained any command that
provided a command line. But, STRPRTWTR doesn't.

John McKee

-----Original message-----
From: "Burns, Bryan" Bryan_Burns@xxxxxxxxxxxx
Date: Tue, 05 Oct 2010 14:55:41 -0500
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Authority to start a writer at the user level

Is there any way a user without *SPLCTL and *JOBCTL can start a
printer writer without adopting authority? I've been looking at IBM
Software Technical Document 421165187 which documents the creation of
a CL so a user can start a writer using adopted authority, but before
I take this approach, I want to confirm that if the authority for both

the OUTQ and DEVD is *PUBLIC *ALL and AUTCHK for the outqueue is
*DTAAUT; the user will still not have enough authority to start a

writer.

Bryan Burns
ECHO, Incorporated