Re: 5250 Data Stream + Async I/O

[benji@xxxxxxxxxxxxxxxx]

>Benjamin;
>
>A).  Forget that paradigm.  He doesn't have to do the work of the OS
anymore.
>    It is smart enough to do the right thing.  Trust it.
>
I think I just couldn't explain my problem. He doesn't do the work of the
OS: he just wants to get notified without having to keep an eye on a
notification object (such as data queue, data area entry, semaphore etc.)
This is not a big deal, even Windows can do it. (My first and only Windows
program was a serial terminal "driver" component, and I used overlapped
I/O.)


>B).  What language are you thinking about using?

Any language... (BTW, I didn't find an ADA compiler for AS/400, nor
FORTRAN. AS/400 is not for REAL programmers :)

>
>If the language is  RPG, COBOL,  or something using embedded SQL,
>the machine will control the I/O and whether it's Async or just Sync.
>
>If you are doing "Sequential"  file processing, (ie Reading records
without
>using a
>key - in RPG/COBOL jargon),  You can do an OVRDBF and use the  NBRRCDS
>parameter to let the system do blocking.   Look up and read on Sequential
>File
>Processing.   It will tell you about the AS/400's  use of Sync and ASync
>file
>processing.  These things also come into play if you use a command like
>OPNQRYF.
>Read about that command and see what you find out.

I'm not speaking about disk I/O, but I/O in general (ie. communications,
tape).

>
>John Carr

Benjamin Budai



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