Re: Startup Program

[Evan Harris <auctionitis@xxxxxxxxx>]

In my case I always change the owner of the start up program to a
QSECOFR level profile and change the program to run with *OWNER. Seen
to many instances where the startup program got stopped doing
something because it wasn't authorised. My rationale for doing this is
that the the startup should always run and run to end in my view of
the world.

I understand that there should be some security around what this
program does but prefer to see that done at the compile/source level
and the ability to change system values rather than running it under a
lesser profile.

On Thu, Mar 10, 2011 at 10:38 AM, Jim Oberholtzer <midrangel@xxxxxxxxxx> wrote:
> Even when I write a custom program for start up I always use QPGMR with
> no additional authority changes.  Keeps things clean.  If there is a
> function that needs higher authority, I'll write an adopted authority
> program for just that function and call it from the start up....
>
> Jim Oberholtzer
> CEO/Chief Technical Architect
> Agile Technology Architects, LLC
>
>
> On 3/9/2011 3:21 PM, Ketzes, Larry wrote:
> > Just a quick poll here folks.  What user profile do you run your startup program under.  I believe the default is qpgmr.
> >
> > Thanks, Larry
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.