Re: Job Scheduler Task

The menu for the job scheduler (wrkjobjs) will take you into the history of the jobs - there are options to see the history - you can see the run time on the screen for the past times executed, and then review job logs thru the menu. I would assume the job logs are just spooled files in an outq. You could programmatically read the spooled files, but a quick look thru the schedule menu, pick your long jobs, & then drill into job logs could give you an idea.
Analyzing a system's performance could take days to describe.
If sql involved then check out the iNavigator's SQL Index Advisor (if you have iNav on your desktop). .
Jim


----- Original Message ----- From: "Robert Munday" <rwmunday@xxxxxxxxxxxxx>
To: "Midrange List" <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, September 08, 2011 7:31 PM
Subject: Job Scheduler Task

Greetings from the sunny south.

My client has another task for me which is more suitable for a DBA than a
developer. I have not worked with Job Scheduler.

My charge is to dump or review the statistics from the Job Scheduler
History and look for long-running jobs to determine if changes would
improve the throughput of the processes. I found some *JS* libraries
right before signoff this afternoon. From what I saw the members were
programs and not files. I have also briefly looked at the Midrange.com
archives and a few Google results.

Where would I need to look to find these history files? Any tips on how
to determine the resource hogs?

Thanks,

Robert Munday
Munday Software Consultants
Montgomery, AL
on assignment in New Albany, OH
--
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.