|
Hi Jeff, I personally like autostart job entries in the subsystem description. Here's an example of what I did and perhaps it can apply to what you are doing. The users here have all spooled files SAVE(*YES) and this can clutter up the output queue. I have a job that is automatically started when the QBATCH subsystem starts up and just moves all the spooled files with a status of SAV to a SAVOUTQ. The subsystem QBATCH has an autostart job entry. Job MOVPR124, Jobd MOVPR124, Lib QGPL. The job description MOVPR124 has job queue QTXTSRCH which has no limit on how many jobs can run at the same time. I specify RQSDTA(MOVSAVSPLF FROUTQ(PR124) TOOUTQ(SAVOUTQ) REPEAT(*YES) DLY(900)) The cpp for my command has the basic logic at the bottom; if &repeat *eq *YES, DLYJOB DLY(&DLY), goto again, endif. You would pass DLY(3600) to get your one hour that you want. Glenn Jeff Schmehl wrote: > Can anyone tell me what is the best way to run jobs every hour without user > intervention on an as/400. I need to keep alive a certain procedure and > have it run every hour until certain time of the day. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.