• Subject: Re: exporting to .csv file
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Thu, 22 Jul 1999 14:49:07 -0600

Dan,

This command is part of the parallel data loader support added via 
PTF with V4R1.  It wasn't fully supported until V4R3 and was very rough 
up through that release.  It is still a little rough, just try to specify *TAB 
as a delimiter for an example, but can be very useful for transferring 
data between systems.  The help text is all upper case on the PTF 
version.

You can use this command to convert the format of data being transferred 
to or from another platform.  It can also convert the code page at the same 
time.  It is supposed to be very fast, but in reality it doesn't appear to 
be any faster than CPYTOPCD or CPYTOSTMF.

It appears as though the author intended to support setting the code 
page at run time, but the implemented falls short.  It states that you 
can set the code page if the target file's code page is 65535.  I have 
used these commands quite a bit from within application programs 
which makes it easier to get around the limitations, but it would be nice 
to have the interface enhanced to support an output code page.

David Morris

>>> "Dan Bale" <dbale@genfast.com> 07/22/99 12:48PM >>>


Roger,

You lost me.  I've never used CPYTOIMPF.  The prompts & help on the command is
all uppercase; is this an IBM command?  Command help sayeth:

THE COPY TO IMPORT FILE (CPYTOIMPF) COMMAND COPIES AN EXTERNALLY DESCRIBED FILE
TO AN IMPORT FILE.  THE TERM IMPORT FILE IS USED TO DESCRIBE A FILE CREATED FOR
PURPOSES OF COPYING DATA BETWEEN HETEROGENOUS DATABASES.

Huh?  I must'a been sleeping through that class.  Can you give me (us) a short
lesson on this command and how it differs from CPYTOPCD?

Thanks,
- Dan Bale

> I'm trying to export an AS/400 physical file to a comma separated
> variable file in a folder so I can email the data to someone who can
> open the file in Excel.  Right now I am doing it in two steps.
>
> Step 1. Export the file:
>
>  CPYTOIMPF FROMFILE(EDI002P) +
>            TOSTMF('qdls/folder/edi002') +
>            RCDDLM(*CRLF)
>
> Step 2. Convert to ASCII using the COPY command:
>
>  COPY OBJ('qdls/folder/edi002') +
>       TOOBJ('qdls/folder/edi002.csv') +
>       TOCODEPAGE(*PCASCII) +
>       DTAFMT(*TEXT)

It's still a little grungy and requires the existence of a target template,
but that isn't that big of a deal. And, this method eliminates a
time-consuming copy of a large file after it's been CPYTOIMFed.  Why in the
%@#$@%@!# doesn't CPYTIMPF provide a codepage parameter!?

1. Create a single, empty correctly code-paged template target file in a
folder (with with CPY or from the PC).

2. Before you do the CPYTOIMPF, use CPY to copy the template target file to
the approrpiate folder with the appropriate name.

3. Use CPYTOIMPF to copy to that new target file. CPYTOIMPF will preserve
its codepage.

rp






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


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

This mailing list archive is Copyright 1997-2019 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 here. If you have questions about this, please contact [javascript protected email address].