|
Nope,
the program hits the read and the program knows it is an ICF file and the
program goes into an ICFW status (ICF wait). The program is waiting to
receive some records via the device file. It chews up NO
CPU.
cjg
Carl J. Galgano
EDI Consulting Services, Inc.
550 Kennesaw
Avenue, Suite 800
Marietta, GA 30060
(770) 422-2995 - voice
(419)
730-8212 - fax
mailto:cgalgano@ediconsulting.com
http://www.ediconsulting.com
AS400 EDI, Networking,
E-Commerce and Communications Consulting and Implementation
http://www.icecreamovernight.com
Premium Ice Cream Brands
shipped Overnight
"You ain't gonna learn what you don't want to know" -
rw
Carl,
Thanks for the reply. So the RPG program just sits
there looping until it gets records??? I assume that the read will
generate an error until records actually start arriving and you put some kind
of delay in to keep it from chewing up the system.
Bill
----- Original Message -----
<Snip>
The code is really petty simple, the program sits
in a wait (read) of the ICF file. The call comes in on the line, and
the controller list is checked to see what controller is associated with the
line. It then looks up the device to see what ICF file is associated
with it. The ICF file is attached to the program. You have
to have the BSC receive program running at all times. Create a SBS and
create an autostart job that runs the receive program. After you
receive data, go back and wait for another call.
<Snip>
|
midrange.com
