|
Given that break-handling programs can handle this automatically via the RESET() parm of CHGMSGQ, I'm not sure why any other solution is needed. Tom Liotta On Tue, 07 August 2001, "Steve Richter" wrote: > Simon said: > > >Receiving the last message and waiting for the next message is the correct > >way of handling this rather than half-arsed suggestions about using magic > >messages or checking dates and times. > > > The stop,start msg method also works well with the data queue/background > processor setup. The bp is pgm'd to end when the stop msg is rcvd. Sometimes > the bp starts, rcvs an old "stop" msg and ends. Adding a "start" msg solves > that problem. The bp ignores "stop" msgs until a "start" msg is rcvd. > > Another example of the algorithm/template solution being superior to the > technical solution: The algorithm solution has more than one application. > The technical solution only solves one problem. > > Steve Richter -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
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.
midrange.com
