RE: csv output from cpytoimpf

There are ptfs available for this one.  There was a posting on the Ignite400
list week before last about it.  I didn't save it, because we're going to
v4r4 at the end of the month and hope to see them the morning after the
install.

I've had to do some file extracts for import into (gasp)an NT based package
recently, so it's more of a sore subject for me than it might be otherwise.


I've also been playing with the IFS recently, and have found a lot of good
things to say about it.  Sure wish it were documented better.  Finding out
how to do some simple things is like trying to learn to boil water from a
book on alchemy.

> -----Original Message-----
> From: Gwecnal@aol.com [mailto:Gwecnal@aol.com]
> Sent: Monday, May 15, 2000 9:20 AM
> To: MIDRANGE-L@midrange.com
> Subject: RE: csv output from cpytoimpf
> 
> 
> > It's not a matter of life and death for me, but it's 
> bizarre how cpytoimpf
> > seems to follow its own path for the comma delimited 
> format.  I'm belaboring
> > the obvious here, but CSV is _supposed_ to be a standard 
> for file exchange.
> 
> Amen, brother.  As long as we are on the topic - in order to 
> get an exterally 
> described file into a comma delimited ASCII format that Excel 
> can read, I 
> have to do a CPYTOIMPF followed by a CPYTOSTMF.  If I do the 
> COPTOIMPF direct 
> to a stream file (which is an option) I get garbage because 
> there is no place 
> for the CVTDTA table.  Am I the only one who has to do this?  
> TIA, Lance  
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---