|
Thanks ed, I'll give that a try in the am... Ken Ed Chabot wrote: > > If I understand correctly, you are getting the key AND your data field for > each record with a comma separating the two fields and all you want is the > data field. If this is correct, make sure that the logical field number of > the key field is set to 0. This will tell DLINK to EXCLUDE this field from > the logical record. HTH. > > Ed Chabot > The Marlin Firearms Company > 100 Kenna Drive > North Haven, CT 06473 > (203)985-3254 > > -----Original Message----- > From: midrange-l-admin@midrange.com > [mailto:midrange-l-admin@midrange.com]On Behalf Of ken shields > Sent: Thursday, January 10, 2002 7:15 AM > To: midrange-l@midrange.com > Subject: Re: Nlynx/Idealink > > Scott > Designed a Read XFW, EBCDIC record length 167. > The problem I'm having is the 'KEY' definition. > I define 1-4 as key > 1-167 data , but I keep getting some variation of that key in the >outpt > record. > eg,---------- 5100,5100abcdefg......etc > OR > If I define the key as some blank location in the records I get > -------------- ,5100abcdefg......etc > The comma up front blows the output > The key, as you'll remember was mandatory > used option 0, variable ascii > any ideas? > Thanks > > Scott Klement wrote: > > > > I used IdeaLink (the IDEAComm MRC version) back in the early '90s. It > > wasn't an FTP program, but rather was it's own custom file transfer > > software, more similar to the Client Access file transfer than FTP. > > > > I have no idea who produces that software today. But, go ahead and ask > > your question, and I'll help if I can remember answer :) > > > > On Wed, 9 Jan 2002, ken shields wrote: > > > > > This product was originally Ideacomm midrange client. > > > One of the programs was theit ftp program called Idealink. > > > Is there anyone on the list who has had any exposure to the > product, I > > > have a question. > > > ps > > > I think it's currently under the Decision Data umberella. > > > Thanks > > > > _______________________________________________ > > 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. > > -- > Best Regards > Ken Shields > Home phone: 905 404-2062 > Bus phone 905 725-1144 (326) > _______________________________________________ > 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 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. -- Best Regards Ken Shields Home phone: 905 404-2062 Bus phone 905 725-1144 (326)
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.