|
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 ] Thanks for the reply, and of course your right... I didn't ask my question correctly... But here's are problem... We have an ICFF set up that has been working great for the past 8 years, and now were switching to a new bank, and when we send the file to the new bank, there getting the file, but there is a duplicate record, and now the word << exchange rje blah blah >> is showing up on the bank side, so it seems the communication line is adding data to our records... I was wondering if you had any ideas where to start looking for the problem? thanks, tim > -----Original Message----- > From: Buck Calabro [SMTP:Buck.Calabro@commsoft.net] > Sent: Monday, May 06, 2002 11:54 AM > To: midrange-l@midrange.com > Subject: RE: ICF File... > > Tim wrote: > > >If I have written data to an ICF file, is > >there any way to look at the data in the file? > > No. > > >The bank says were sending an extra trailing record, > >and we were looking for a way to test the data, > >without bothering the bank... > > Not readily, but you can do a post-mortem sort of thing by running a > communications trace (STRCMNTRC and TRCICF). > > The reason you can't see data that's in an ICF file is that there isn't > any > data in an ICF file. Being a device file, it routes data from your > program > to the far end of the communications link. Nothing is stored there. > > If you are familiar with ICF files, you could set up an Intra subsystem > and > write a companion to your existing 'send' program to do the receive side. > Perhaps the easiest thing to do is to look at the line trace and see if > you > can see what the HLL program is doing. > --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.
As an Amazon Associate we earn from qualifying purchases.
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.