RE: ICF dynamic read problem was: bug

["Carl Galgano" <cgalgano2@xxxxxxxxxxxxxxxxx>]

Tim:
Is this BSC?  In the ICF trace it shows the BLOCK length not the record
length.  Usually a block is transmitted with multiple logical records in
it.  If you look in the 81st position in the trace what is the
character.  There should be a Interrecord separator, usually a hex 1E or
1D.  These BSC control codes are not passed to the ICF file.  The
unblocking of the data is handled by the BSC protocol, you just have to
specify the correct IRS either on the DEVD or the ICFDEVE.  Can you post
a few block of data from your trace here so we can have a look at it.
Thanks,
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
FREE AS/400 Timesharing Service -
http://www.ediconsulting.com/timeshare.html
"You ain't gonna learn what you don't want to know" - rw


-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com] On Behalf Of Hatzenbeler, Tim
Sent: Thursday, May 16, 2002 6:00 PM
To: 'midrange-l@midrange.com'
Subject: ICF dynamic read problem was: bug


This message is in MIME format. Since your mail reader does not
understand this format, some or all of this message may not be legible.
--
[ Picked text/plain from multipart/alternative ]
I'm stuck again.....

The bank told me, that if I send all my 80 character detail lines to
them, after they get the trailor record, they will send me back an 80
character confirmation line back...

But thats not actually true... When I look at the ICF trace the back in
sending me back 1077 bytes....  All the the confimation lines from all
my testing...  So I'm trying to figure out how to read this variable
number of lines...

If my record length in my dds is set to 80, it says my buffer isn't big
enough...  So if I set the buffer to 5000 bytes, the read will time out,
because it didn't get the othe 4000 bytes...

So I'm stuck...  I would like to read 80 characters, and then check, to
see if there is another 80 to recieve, and then read those... and when
there are no more bytes left to read... Quit...

How would I do that?

Thanks, tim



> -----Original Message-----
> From: Buck Calabro [SMTP:Buck.Calabro@commsoft.net]
> Sent: Thursday, May 16, 2002 6:57 AM
> To:   midrange-l@midrange.com
> Subject:      RE: ICF bug
>
> Tim,
> Generally speaking, I have the 'receive' record placed physically
> first in the DDS like so:
>
> A                                      INDARA
> A                                      RCVDETACH(35 'RCVD DETACH')
> A                                      RCVENDGRP(40 'RCVD ENDGRP')
> A**63                                  DETACH
> A          R RCVDTA
> A            RCVREC        80
> A          R BOAREC
> A            DATARC        80
> A          R DETACH                    DETACH
>
> Then don't try to READ against the record format, instead, read
> against the file.  This will allow the timeout to kick in.  But I'm
> not at all certain that this is your issue.  Are you certain that the
> far side is actually sending the data at the time you expect it?  What

> is the major/minor when you do the read?
>   --buck
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
This e-mail message, including any attachments, is for the sole use of
the intended recipient(s) and may contain confidential or privileged
information.  Any unauthorized review; use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact
the sender by reply e-mail and destroy the message.
_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@midrange.com To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.