Re: Another question on getting a file to CSV format

Paul,

This works great.  I didn't realize I could recreate my file on the 400, 
instead of going to QDLS first.



Thanx,

Nick


PS - the fishing has been pretty good this year.  I filled out a couple of 
times a week or so ago.  The dumb fish just wouldn't let me have a my 
beer!  :--)

Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct  (320) 679-6683
Toll free  (800) 388-2155  ext. 6683
Fax  (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



pnelson@xxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
06/28/06 10:23 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Another question on getting a file to CSV format






Here's a sample of what one client is using:

cpytoimpf  fromfile(ifpa/producer) tofile(ifpa/prodweb) 
                          mbropt(*replace) rcddlm(*eor) 
                          strdlm(*none) flddlm('^') 

We are using a carat as the field delimiter because the data fields have 
commas in them. Once the prodweb file is populated it is sent via FTP 
straight to an SQL server as a .csv file. There is no reason to need to 
put it into QDLS. As a matter of fact, you should not be using QDLS if you 

can avoid it. Way too slow.