Re: Policy for Job Scheduler User Profiles

I like to setup profiles that cannot sign on, and have them
run the job schedule jobs. I never want an end user or programmers
id on a scheduled job.
Jim Franz

----- Original Message ----- From: "Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>
To: <MIDRANGE-L@xxxxxxxxxxxx>
Sent: Wednesday, August 13, 2008 9:55 AM
Subject: Policy for Job Scheduler User Profiles

What's your policy on the user profile to be used for scheduled jobs? In the past we've all used our own profiles but that's not the best approach because the user might leave the company. In fact, our invoicing job was running under a user's name long after he left the company until I finally changed it.

Furthermore, auditors don't think that I - the operator / administrator - should even have access to the JS due to the need for "separation of duties". Well, management said they'll accept the risk on that one and put detective controls in place.

And by the way, thanks to everyone who replied to my post about QSECOFR user profiles - they were very helpful.

Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich, Illinois

--
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.