|
One of the easiest ways to xfer a S36EE file is to use the Nlynx ETU/400 ($495) product. It will do comma separated values if the file is defined on the AS400 with DDS. If it is flat you can define a logical over it to get the field separation you need. Jerry Jerome Draper, Trilobyte Software Systems, since 1976 Network and Connectivity Specialist -- Mac's, LAN's, PC's, Windows, Linux, Sun, and AS/400 Representing Synapse, CLI, Nlynx, Perle, Lucent, 3Com and Others ..... http://www.trilosoft.com - (415) 457-3431 - (415) 258-1658fax - jdraper@trilosoft.com ----- Original Message ----- From: Paul Tykodi <paul@intermate-us.com> To: <midrange-l@midrange.com> Sent: Monday, December 03, 2001 9:18 AM Subject: S36EE Client Access File Transfer Question > Dear List, > > I was recently speaking with an AS/400 (V4R2) end user about a remote > printing problem and they mentioned during the conversation that they were > also experiencing a Client Access file transfer request problem as well. I > mentioned that some years ago I used to build Client Access file transfer > requests to test twinax emulation cards and that as a last resort type of > problem resolving option I would be willing to at least look at their > problem. > > The end user has decided to accept my offer and has let me know the target > file on the AS/400 that holds the data they need is a database file for a > custom RPG II application they wrote in-house that runs within the S36EE on > their machine. > > I was wondering whether anyone knows if the Client Access SQL logic for file > transfer support can retrieve data from an RPG II formatted file that is > stored in the S36EE? If yes, are there any special customization steps > required in the creation of the file transfer request? > > Thanks. > > Best Regards, > > /Paul > -- > Paul Tykodi > Director, Printer Connectivity Product Management > LCI-Intermate US, Inc. > > p: 603.431.0606 x115 > f: 603.436.6432 > paul@intermate-us.com > www.intermate.com > > _______________________________________________ > 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. > >
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.