× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: csv output from cpytoimpf
  • From: Dave Brimeyer <dbrimeyer@xxxxxxxx>
  • Date: Sun, 14 May 2000 20:40:56 -0700

Actually, IBM has a PTF to fix the CPYTOIMPF problem with the comma following 
the
last field.

R420 SF56130
R430 SF56123
R440 SF56124

Dave Brimeyer
Ascend Technologies

Joel Fritz wrote:

> You're right about the Client Access file transfer.  Don't know what I was
> thinking.  The other thing that seems a bit nonstandard with cpytoimpf is
> the comma that follow the last field.  I assume that that's "as designed
> also." (Although it seems like the off by one errors that plague me in my
> own code. <g>)
>
> 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.
> <g>
>
> > -----Original Message-----
> > From: Dave Brimeyer [mailto:dbrimeyer@home.com]
> > Sent: Saturday, May 13, 2000 2:28 PM
> > To: MIDRANGE-L@midrange.com
> > Subject: Re: csv output from cpytoimpf
> >
> >
> > The Client Access Express data transfer to csv file strips
> > trailing blanks from
> > character fields.  When we discovered cpytoimpf does not, we
> > reported to IBM as a
> > bug.  We got their typical "working as designed" response,
> > though they realized
> > it is something that needs to be changed.  Don't know if/when
> > that will happen.
> >
> > Dave Brimeyer
> > Ascend Technologies
> >
> >
> +---
> | 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
> +---

+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.