Re: Job Scheduler - User question

We have some job scheduled reports for a person with certain responsibilities, where there is turn-over with that person.

1. When we disable the password so it cannot be signed on, the job scheduled in that person name runs fine.

2. Then we need to change the job scheduler job to be in another person name. This has to be done by security officer, because our users security won't let them change another person's job. The change needs to be tested in case the job uses something where the new person security not quite right for it. Alternatively we can copy the info in the old scheduled task to another with same details except another person. This is safer, because we not kill old approach until new one tested running Ok.

We use description of job to include name of who it is for, so it is not just matter of changing owner of job, and relevant message queur.

Of course we using this for reports so that when our crew shows up to work, they have wating for them certain reports up to date, already run (in wee hours). If your scheduled reports are doing updates that you not want skipped a day or done twice, you need a different approach.

3. I had proposed, but rest of company did not go along with it, that we create summy user with name like SALESDEPT to have their own OUTQ MSGQ scheduled jobs etc. then all in the dpet know where to find their stuff, and not have to be messing with this every time there is turn-over of personnel.

I want to avoid situations that get the JOBQ hung. It is now so rare, that when it happens, no one notices for 1/2 a day or more.

What happens if the user who scheduled a job is removed from the system? Is
there a way to change one user to another? Changing the owner of objects
does not work.

I did a quick check of the archives, but found no answer.

Thanks!

--
Jim Essinger
Senior Programmer/Analyst
GCO Servicing Corp.
6905 Highway 95
PO Box 1000
Fruitland ID 83619-1000
208-452-9547 (Voice)
208-452-5848 (Fax)

--

The information contained in this email may be confidential and privileged
information and is intended only for the individual or entity to whom it is
addressed. Any unauthorized use, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify the GCO Servicing Corp. immediately.
--
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.