|
On Fri, 2005-04-29 at 09:18 -0500, Jon Sinner wrote: > Occasionally the program will terminate with a normal completion. There > seems to be no consistency in this termination. Sometimes it will terminate > after waiting anywhere from 10 minutes to a couple of hours. > > Has anybody experienced this sort of behavior using the EOFDLY? I know hundreds of clients using a particular package that makes use of EOFDLY with no problems, since System 38 days. I would double check my code to make sure that it can't seton LR from inside the main processing loop. Actually, I would also add a SHTDN check to the processing loop so that it *could* terminate nicely in the event the job is ended via ENDJOB or ENDSBS. The code could also terminate without error if you are trapping the error via *PSSR (or monitor). Also, you might consider coding it in such a way so that if the program drops out of the read loop, wait 30 seconds via DLYJOB, then send it back in to the loop. Have it keep a log or send a message to you whenever it happens. Perhaps you can pin down the cause that way. -- Regards, Rich Current Conditions in Des Moines, IA Clear Temp 46.4F Winds out of the North at 3mph
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.