Re: Whats the best way to run a CL every 30 min

 
> Buck Calabro wrote:
> >
> > Brad,
> > "Do I have a JOBQ to tie up forever?" is certainly a viable concern!  The
> > opposing view is that there is a lot of overhead involved in creating a new
> > job.  Count the seconds that elapse between pressing Enter on the sign-on
> > display and the appearance of the command line...
> 

One thing to consider is that looping in the same program forever may
cause unexpected errors due to limitations on individual jobs.

For example there is a limit of 10,000 spool files per job.   There are
others - you don't normally bump into them during normal processing but
on a job that never ends it can be a real problem.  Any kind of memory
leak or similar problem may not crop up until the job has been running
for days or weeks.  As an added bonus if you IPL on a regular basis the
problem may not appear until months later when for some reason you had
to skip a regular IPL. 

I don't think there is a appreciable difference between doing a dlyjob
and a sbmjob for + 30 min.  Either way the system has to check the
status of the job every pass through the job table.  

John Hall
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---