RE: Re[2]: csv output from cpytoimpf

["Draper, Dale" <dale.draper@xxxxxxxxxxxx>]

Beautiful!! Ah love undocumented features! Worked like a charm, suddenly a 3
character field became 25. BTW, I did that wrong the first time using an @
and this field became a length of 1(!). Guess it's a variable field?
heheheh.

Now to see if that option helps any.

Thank you again,

Dale

> -----Original Message-----
> From: eric.delong@pmsi-services.com [SMTP:eric.delong@pmsi-services.com]
> Sent: Monday, May 15, 2000 2:16 PM
> To:   MIDRANGE-L@midrange.com
> Subject:      Re[2]: csv output from cpytoimpf 
> 
> 
>      Hmmmm, so you start to type in *TAB and run out of room before you 
>      get the B typed. Try typing a & symbol in that prompt and see if it 
>      will expand your entry field.
>      
>      good luck,
>      eric.delong@pmsi-services.com
> 
> 
> ______________________________ Reply Separator
> _________________________________
> Subject: RE: csv output from cpytoimpf 
> Author:  <MIDRANGE-L@midrange.com> at INET_WACO
> Date:    5/15/00 6:34 AM
> 
> 
> We are trying, and succeeding in using this command along with a few
> others 
> to create files readable by MS products. But I would like to try to change
> 
> the " FIELD DELIMITER  . . . . . . . . FLDDLM         ','  "  field to
> *TAB 
> as shown as an alternative. But this input field is only 3 characters
> long! 
> Is this merely an example of poor documentation?
>      
>      
>      
> > -----Original Message-----
> > From:       Dave Brimeyer [SMTP:dbrimeyer@home.com] 
> > Sent:       Sunday, May 14, 2000 8:41 PM
> > To: MIDRANGE-L@midrange.com
> > Subject:    Re: csv output from cpytoimpf 
> > 
> > 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
> > +---
> +---
> | 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
> +---
+---
| 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
+---