|
midrange.com
Just like with V4R4, you won't get those extra parms in V4R5 without the
proper PTF's. Trust me, I know. I think that this will change in the
follow on release.
Rob Berendt
==================
Remember the Cole!
Angela Wawrzaszek
<wawrzaszeka@AUSTEE To:
"'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
L.com> cc:
Sent by: Subject: RE: converting
files and many views
owner-midrange-l@mi
drange.com
03/12/01 01:26 PM
Please respond to
MIDRANGE-L
I did use the *none on the cpytoimpf to specify no quotes. We are on V4R4
- going up on V4R5 at Easter, so we do not have the extra parameter for
code page. That is why I tried just doing the cpy obj toobj ... and
specified *pcascii on that command hoping it would accomplish the same
thing.
However the size of the files are different thus i think the line wrapping.
My file is samll - only 49 positions. However if I use cpytoimpf the
resulting file is 8mb, importing to excel and saving as .csv is only 5mb.
Hopefully when we go up on the new release I can eliminate this problem
with
the cpytoimpf extra parms.
Angie Wawrzaszek
M.I.S. Department
-----Original Message-----
From: Joel Fritz [mailto:JFritz@sharperimage.com]
Sent: Monday, March 12, 2001 12:34 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: converting files and many views
There is no comma delimited file standard--it's just custom and personal
preference. I think the quoted string is more common than the strings
without quotes.
I don't think Client Access file transfer allows you to eliminate the
quotes
on character fields, but CPYTOIMPF does with the STRDLM parameter. It
allows
you to specify anything you want, including *NONE as the string delimiter.
(Different parm from the field delimiter)
I don't understand the problem with lines wrapping with CPYTOIMPF. That
would imply that there are extraneous carriage returns, line feeds, or CRLF
pairs in the lines that are wrapping. I've converted a lot of files with
reasonably large record lengths using CPYTOIPMF without seeing this
problem.
I just sent out a test file with a 369 byte record length this morning.
Once you get past the code page problem (see recent thread) CPYTOIMPF is a
pretty good utility. It offers you a lot of flexibility in the type of
text
file and also allows you to specify date and number format.
-----Original Message-----
From: Angela Wawrzaszek [mailto:wawrzaszeka@AUSTEEL.com]
Sent: Monday, March 12, 2001 8:44 AM
To: Midrange Mail List (E-mail)
Subject: converting files and many views
I am curious as to why transferring data is not standard
ie. I take a as/400 file and transfer it in the following ways and each
one gives me a different file.
1. Transfer into excel, then do saveas to .csv This produces the
desired file. No quotes on the char fields and no line wrapping. However
I
can not seem to find a way to automate this.
2. AS/400 data transfer (.dtf file) and then do as/400 command cpy
obj(myfile.csv) toobj(newfile.csv) fromcodpag(*pcascii) dtafmt(*text)
This produces a csv file but it has quotes around the char fields which I
do
not want.
3. AS/400 data transfer (.dtf file) and then do with strpco I copy the
csv file to the desired name. This also produces a csv file with quotes
in the char fields.
4.CPYTOIMPF - creates csv file no quotes however it line wraps.
5. FTP through a .bat file - creates gibberish.
Is there a way to NOT put quotes on the char fields using CA dta transfer?
This seems to be the only way the file gets created normally with out
having
to manually bring it in to excel and do a saveas.
I have been going through the archives and it seems everyone is using
cpytoimpf and the cpy obj commands. However when I try these I am still
not getting the file I desire.
Thanks!!!
Angie Wawrzaszek
M.I.S. Department
+---
| 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
+---
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.
