Re: [Security400] Authority annoyances, continued...

["John Earl" <johnearl@xxxxxxxxxxxxxxxxxx>]

> QSYSOPR wouldn't be able to do that. It checks to see if you have
authority
> to the user profile on the job description.  The sbmjob would fail
with a
> "not authorized to profile" message.

True for QSECURITY level 40 machines.  But if the machine is at
QSECURITY level 30 or less, the sbmjob would be successful if the user
merely has *USE authority to the JOBD.

jte


>
> -----Original Message-----
> From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
> Sent: Wednesday, August 22, 2001 12:00 PM
> To: security400@midrange.com
> Subject: RE: [Security400] Authority annoyances, continued...
>
>
> >Create a job description that will be used to submit the
> >back up job to batch. Ensure that the USER parameter
> >of the job description specifies the new user (eg.
> >USER(BACKUPUSER)). Any job submited to batch
> >using this job description will then run under the new user
profile.
>
> Not a guru, so this may be wrong, but can't I (a mere operator) do:
sbmjob
> cmd(grtobjaut...) jobd(backupjobd) and give myself authority to
anything?
> Why is this better than having the CL program adopt required
authority?
> _______________________________________________
> This is the Security Administration on the AS400 / iSeries
(Security400)
> mailing list
> To post a message email: Security400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/security400
> or email: Security400-request@midrange.com
> _______________________________________________
> This is the Security Administration on the AS400 / iSeries
(Security400) mailing list
> To post a message email: Security400@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/security400
> or email: Security400-request@midrange.com
>

--
John Earl - VP & CTO
The Powertech Group
253-872-7788
johnearl@powertechgroup.com
www.powertechgroup.com