MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » September 2011

RE: Job Scheduler Task



fixed

Hi Robert,

Assuming you are talking about the IBM job scheduler(s) and not
something like Robot/Scheduler you may be able to use a combination of
the List Job Schedule Entries (QWCLSCDE) and Retrieve Job Information
(QUSRJOBI) APIs. QUSRJOBI format JOBI0400 has the date and time a job
became active and the date and time the job ended.

Many moons ago I used RPG III to write a Job Scheduler look alike so
developers could review entries but not run or change entries. I've
used the QUSRJOBI API extensively but not against completed jobs. I
don't see why it wouldn't work though. The information you see when you
run WRKJOB against a job that has completed has to be coming from
somewhere and IBM generally uses its own APIs to do such stuff.

So here are the steps you could follow.

1. Use QWCLSCDE to obtain a list of jobs in the IBM job scheduler.
Format SCDL0200 has the last submitted job information.
2. Read through the job scheduler list to obtain the last job submission
information needed for api QUSRJOBI.
3. Use QUSRJOBI with format JOBI0400 to obtain the job's actual start
date and time and ending date and time.
4. Do your time calculation.
5. Report your findings.

HTH,

Gary Monnier


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Munday
Sent: Thursday, September 08, 2011 4:31 PM
To: Midrange List
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.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact