× 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: Why I need to delay less than a second
  • From: "York, Albert" <albert.york@xxxxxxxxxxxxxx>
  • Date: Tue, 13 Feb 2001 11:30:35 -0800

I have a legacy DOS application written in Basic. I need to run it under
Windows (in a DOS window). 

It needs to transfer data back and forth to the AS/400. Using Client Access
I can map a network drive on the AS/400 and have a Basic routine which
writes data to a file in a folder on the AS/400 (remember this is running in
DOS). On the AS/400 I have a program running which checks that file (using
stream file APIs) and when the PC has written data, it processes the data
and sends back a response in a different file. The PC then reads the
response from the other file. It actually works pretty well, except the
AS/400 takes a second to respond, since that is the minimum wait time. If I
don't delay the job it eats up CPU on the AS/400.

Now that I can reduce the wait time to ½ second it works fine.

Thanks for all your help.

Albert York     
+---
| 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 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.