|
Peter Colpaert wrote: -snip about program looping for ONE user- >C #HRRN CHAIN SFL02 5152 >C *IN51 DOWEQ *OFF -snip- >C #HRRN CHAIN SFL02 5152 >C ENDDO I think you are correct when you think it is a communications problem. This code traps I/O errors (indicator 52) and then ignores them. Add the file information data structure, especially the major/minor return codes (401-404) and *STATUS. Add the program status data structure. Add h debug. When 52 is on, DUMP the program and terminate. The major/minor should tell you if it is a comms error. Buck Calabro Commsoft; Albany, NY "Nothing is so firmly believed as that which we least know" -- Michel Montaigne Visit the Midrange archives at http://www.midrange.com +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-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.