|
I second Al Macs question. One of my customers at one point was complaining that inventory transactions were always way behind. They were submitting one job for each inventory transaction. Even on a large system the jobq was often thousands deep and hours behind. Changing to *DTAQ logic in this case vaporized the backlog. The problem was the 'expense' of starting the job, opening the files, doing one thing, closing the files, terminating the job. The actual doing of the thing was probably only 1% of the work in each job. - Larry MacWheel99@aol.com wrote: > > > Is there a limit on the number of entries you can place in a job queue? > > I'm wondering about 150,000 entries or so at one time. > > I am just curious ... what kinds of jobs might these be in what kind of > application? -- Larry Bolhuis | Cogito ergo mercari iSeries Arbor Solutions, Inc. | (616) 451-2500 | (I think, therefore I buy iSeries.) (616) 451-2571 -fax | lbolhuis@arbsol.com | #3 1951-2001 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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.