× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



At 08:12 AM 9/30/98 -0400, you wrote:
Hi Buck,
No, you shouldn't have to do this - the only problem I'm aware of with
timeout values not being effective are with bisync and SNA switched
connections where the first I/O (or ACQ for SNA) cannot be timed out using
"normal" methods. Make sure you always issue an invite before every read
and that the read (in RPG) is from the file name not the record format
name, otherwise the timer is not in effect. If this is not your problem let
me know and I can suggest something else.
   

>We have similar problems using Async comm lines to talk to credit bureaus, 
>telephone switches, paging terminals, etc.  I believe (not confirmed) that 
>the AS/400 is trying some internal error recovery, because the RPG program 
>never regains control: I have been able to view this while in debug, so I 
>know for a fact that for *some* classes of comm error, the RPG program 
>never regains control.  Yes, I have WAITRCD specified, and yes, I am 
>checking the major/minor after *every* I/O op.
>
>I suspect your CL program is encountering the same condition.
>
>The only way out that I've been able to come up with is to set up a 
>watchdog timer: the comm process sends a message to the watchdog every 15 
>minutes.  If 20 minutes elapse and the watchdog hasn't heard from the comm 
>process, the watchdog kills the comm job, varies off line/ctl/dev and 
>restarts the comm job.  Resetting the config works every time.
>
>Please, somebody tell me I don't need to do this!
>
>Buck Calabro
>Commsoft, Albany, NY
>mailto:mcalabro@commsoft.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
>+---
>
+---
| 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 thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.