|
Submit the jobs to batch and you can have multiple occurrences running. We have a subsystem dedicated to transaction processing. We have 2 occurrences running as a minimum setting with a max of 5. We age the transactions on the queue, if over 6 seconds, we start another occurrence until the max of 5 is reached. We use a 3 digit data area to control the min and max setting so we can change them to fit the resources available. If you have a feeder program dumping transaction to the data queue, you must be sure that you do not overflow the data queue max size of 16M. With a keyed data queue /w no sender ID and max length of 2000, it is about 8208 entries. The smaller the max size, the more entries you can post. If you have lots of processing per transaction it is a great way to speed things up. Make sure your feeder program checks the number of entries on the queue every xx number posted. If over xxxx, wait and check again. If under xxxx, send some more. Hope this helps you to design the work flow and helps you to avoid the pitfalls of data queues. Christopher K. Bipes Sr. Programmer/Analyst CrossCheck, Inc. chrisb@cross-check.com ----- Original Message ----- From: <boothm@earth.Goddard.edu> To: <midrange-l@midrange.com> Sent: Tuesday, June 06, 2000 4:26 PM Subject: Starting jobs to read from a data queue I have a job that runs 14 hours. It needs to run in a shorter period of elapsed time. Lo Raikov told me of a way using RRN and OVRDBF to split the file up and run programs against the overridden file segments (Very neat, Lo, thank you) but would it also be possible to use a feeder program to fill a data queue and then have 14 instances of a program running, each being fed from the data queue? I got it all working except How do you start 14 instances of a program? Opening 14 Client Access sessions seems err... nonprofessional. _______________________ Booth Martin booth@martinvt.com http://www.MartinVT.com _______________________ +--- | 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.