× 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.


  • Subject: RE: Time out on DDM data area
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Wed, 30 Sep 1998 11:40:37 -0400
  • Organization: commsoft

On Wednesday, September 30, 1998 10:48 AM, Tim McCarthy 
[SMTP:twmac@mindspring.com] wrote:
> 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.

Yup.  Always doing the INVITE then the READ from invited.  More often than 
not, the failure is on the ACQ, but this is not a given, as I also get 
failures on the READ and very rarely on a WRITE (with data, not an 
INVITE.)  WAITFILE is 60 and WAITRCD is 15.  Some applications use TIMER 
to override WAITRCD.  All these things work just great for days on end   
then boom; ICFW and no CPU usage.  While the job is "running" the 
line/ctl/dev show ACTIVE with the job attached.  End the job, vary off and 
the line shows FAILED.  Vary on, restart the job with the exact same 
transaction and it goes just fine.

Very puzzling.  The one thing I've never had a good explanation for.

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
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.