|
Larry Bolhuis wrote: > Venu, > > I heartily endorse Patricks suggestion to use a data queue. <<snip>> > > > Many people don't realize the overhead required to start and stop jobs > on the AS/400. <<snip>> I'll second that one Larry. Good point. When I first read your post Venu, I too thought "change the jobq" as many responses indicated. It's a quick off the cuff answer. But the data queue technique is a better solution. If you are producing a report, let's say a pick slip, for each record being processed, you can open and close the spool file for each data queue entry processed and essentially have document on demand processing. Not only do you save on job initiation time, but also on any additional file open/close and have a better handle on CPU utilization and overall job management. One more thing, when we mapped our data queue entry, we added a "verb" field which could contain a *END value to do a graceful program end. There are other verbs we could send to the program such as modification of timeout period so the program could be shifted from demand mode which required open/close for each entry to batch mode that would open once, run many then close. As a side note, the thread about design shift will eventually get around to data queues. Eventually it will get to Rob Dixon's neural network. The data queues are an essential part of the "closed" feedback system I mentioned earlier and are one of the methods for providing feedback to a learning system that can alter behavior on the fly. If you've followed the thread at all, there was mention to dynamic HTML as a screen painter and how a browser would have to test every refreash for replaced format. A data queue could inform a program when a change occured therefore the overhead of an "every refreash" test could be eliminated and do away with the overhead cost of constantly checking for timestamp on a panel format. But that's for another post ;-) James W. Kilgore qappdsn@ibm.net +--- | 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.