|
Hi Brian: I saw your previous post to Marty. Good luck with the implementation. I think FTPing to the IFS is ALWAYS the right way to go. Then you never have to worry about wrapped/unwrapped data, etc. cjg Carl J. Galgano EDI Consulting Services, Inc. 600 Kennesaw Avenue, Suite 400 Marietta, GA 30060 (770) 422-2995 - voice (419) 730-8212 - fax mailto:cgalgano@xxxxxxxxxxxxxxxxx http://www.ediconsulting.com AS400 EDI, Networking, E-Commerce and Communications Consulting and Implementation http://www.icecreamovernight.com Premium Ice Cream Brands shipped Overnight Visit our website to subscribe to our FREE AS/400 Timesharing Service -----Original Message----- From: Brian J. Eckenrod [mailto:beckenrod@xxxxxxxxxxxxxxx] Sent: Thursday, February 19, 2004 8:09 AM To: Midrange Systems Technical Discussion Subject: RE: FTP Receive Question Thanks for the reply Carl. Seems I was on the right track (always nice to know) :-) I will grab that utility and try to incorporate it later on. Certainly more clean than copying spooled output to a PF and reading it. About the looping, I am doing that as well. I create the file listing based on a wildcard, like if I am pulling Purchase Orders, I look for '/path/to/files/PO*' and then CPYFRMSTMF in to one PF and then process that one PF. I assume that is what you meant when you said 'CPYTOSTMF' below you really meant CPYFRMSTMF. Thanks again for the help and for the utilities. Brian -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Carl Galgano Sent: Thursday, February 19, 2004 7:58 AM To: 'Midrange Systems Technical Discussion' Subject: RE: FTP Receive Question Hi Brian: I would go ahead and use the IFS, and as suggested, use the CPYFRMSTMF or CPYFROMIMPF command. If you go to our website (URL below), click the link for DOWNLOADS, there is a free AS400 utility that will do a DIR command to an outfile. The you can simply read the outfile in a loop and execute the CPYFRMSTMF command. We have lot of EDI customers that FTP files to us, into the IFS and we use this technique. Then you don't have to worry about the files being the proper names, etc. If they send 3 files, you do a CPYTOSTMF command into a single PF, and then process the single file. Really a pretty decent solution. cjg Carl J. Galgano EDI Consulting Services, Inc. 600 Kennesaw Avenue, Suite 400 Marietta, GA 30060 (770) 422-2995 - voice (419) 730-8212 - fax mailto:cgalgano@xxxxxxxxxxxxxxxxx http://www.ediconsulting.com AS400 EDI, Networking, E-Commerce and Communications Consulting and Implementation http://www.icecreamovernight.com Premium Ice Cream Brands shipped Overnight Visit our website to subscribe to our FREE AS/400 Timesharing Service -----Original Message----- From: Brian J. Eckenrod [mailto:beckenrod@xxxxxxxxxxxxxxx] Sent: Tuesday, February 17, 2004 4:00 PM To: midrange-l@xxxxxxxxxxxx Subject: FTP Receive Question I have a problem I am trying to solve with something clever and not a big change. Someone is trying to send a large stream of data to our AS400 via FTP. This data is EDI data and not wrapped (one long string of chars). Problem is, with the record size limit on the DB2 side of the AS400, there would be the possibility of truncating the data, if it is written as one long string of data. Of course I built my processes expecting the data to be dropped on the DB2 side of things and would rather not change to receive the data from the IFS. So, I am looking for a way, if there is one, to 'put' a stream of data in to a fixed width file on the AS400. My plan would be for the FTP initiator to create a PF on the 400 with a remote command and then put the data in to it and have it somehow 'magically' wrapped :) If that is not possible, is there a DSPFD equivalent on the IFS that I could create a list of similar files in an IFS folder. Like show me all files that begin with TX* in folder XYZ? Thanks everyone, Brian _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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.