Re: ICF file error "transmission end" during read

I found the problem.  It was on the printer file but I thought it was the
ICF file.  The MSGW was on the ICF file error but that was a normal error.
I got that the old way too.  The printer file error was a PTF issue.  We
will probably be getting it soon.  I guess I hadn't known enough about ICF
files to know if that was normal or not.  As for the OVRICFDEVE, that
temporararily adds the program device entry similar to ADDICFDEVE.  See the
help for OVRICFDEVE.
Thanks all for your help!
Craig Strong

> The difference though is that the old way
> (RPG) would turn on the indicators on the
> "read" rather than blowing up (RPGLE).

This _might_ be a PTF issue, but read on...

> I ran the new way and the old way many
> times over a couple days.  In every case,
> the new way would error out but the old
> way would complete fine.

Have you tried the new program with the old DDS?  Trying to isolate
the problem to a single component...

> Someone mentioned an ADDICFDEVE.  I think
> the overrides are fine for the device as seen at
> the bottom.  I do not need the ADDICFDEVE
> as that occurs in the OVRICFDEVE.

I don't think that's right.  OVR needs something to work on.  DSPFD
the old DDS and the new and make sure they have the exact same device
entries.

> I know it was on the read of the data because
> I could see 2 puts and 2 gets in the dump that
> were from the dialing and logging on.

Hm.  That sounds like the file was opened OK.  Unless there is an
error indicator on the open and it's being ignored.  Did you verify
that the modem is actually being dialed?

Is this synchronous or asynch?
  --buck