Re: job schedulers / object authority

[Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>]

Yes, it can....
that was the first choice to fix this...
however...   (always another GOTCHA)
we have a ... unknown number of applications....
that will make decisions based on the user   i.e.     IF USER IS QSYSOPR,
THEN <<different output queue, different output type, etc>>>  ELSE <<normal
user stuff>>

so changing that setting will require us to find the universe of
applications doing that stuff,   Management says easier to add QSYSOPR *ALL
to AUTHLIST, than hunt down and change apps.

at this point I would like to take those few items (CLRPFM, CHGDTAARA) and
make programs, but next issue may be enforcement of that.

On Thu, May 21, 2020 at 11:05 AM Brian May <bmay@xxxxxxxxxxxxxxxxx> wrote:

> Can your job scheduling tool be configured to use a different profile by
> default?   How many scheduled entries are we talking about?  If not a HUGE
> amount, just create a CL program for each entry.
>
> Brian May
> Director
> Pre-Sales and Customer Solutions
> Profound Logic Software
> http://www.profoundlogic.com
> 937-439-7925 Phone
> 877-224-7768 Toll Free
>
>
> UI Modernization. And More!
>
> www.profoundlogic.com
>
>
> -----Original Message-----
> From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
> Gerald Magnuson
> Sent: Thursday, May 21, 2020 10:56 AM
> To: midrange-l@xxxxxxxxxxxxxxxxxx
> Subject: job schedulers / object authority
>
> re: my question yesterday with needing QSYSOPR to have authority to
> database objects,
>
> we have a job scheduling tool, that allow's a command line string to run
> in a scheduled manor...
> 99.90% of these just so happen to be CALLS or SBMJOBs .09% happen to be OS
> commands NOT DB RELATED (ENDSBS,  SNDMSG, etc) .01% are DB RELATED (CLRPFM,
> CHGDTAARA),  and they now fail.
>
> has anybody encountered this?
> --
> 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
> --
> 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