Re: CPYTOPCD end-of-file character

["David Morris" <dmorris@xxxxxxxxxxxxx>]

Tak,

If you are on V4R2 (via PTF) or later, you can use CPYTOIMPF to create 
a CSV file. The PTFs for V4R2 are SF53333 and SF46911. You should 
check to see if they have been superceded or have any other pre-requisite 
PTF's.

If you created your .CSV file in the IFS or QDLS file system, it can be a 
little 
tricky to specify the code page.  CPYTOIMPF uses the CCSID of the output 
file.  If it is not correct, use the MOV or CPY commands to change the output 
file and retry the copy.

David Morris

>>> <Tak_Lai@intrinsicsol.com.au> 04/08/99 12:42AM >>>

Hi,

As the new tax changes in NZ 1 April 1999. They require companies to send
electronic file monthly schedule in comma separated file format  - CSV.

I have created a physical file with a single field in a record, i.e a field
contains of info like 4,,HAN,FFF,5678888     etc . Then I do a CPYTOPCD
into a folder. The problem is if I specify *TEXT, it will  add an
end-of-file character at the end of the file which the inland revenue
department does not accept it and rejects the file automatically.

If I specify *NOTEXT and add the carraige return & line feed charater for
each record in the program, it will create fix length records and the EXCEL
file cannot recognise the carriage return & line feed character or it add a
long space trailer after the last char.

I know there is some stream file API to do it but is there any smart way to
use CPYTOPCD  and get rid of the end-of-file char or other command ??

Thanks in advance

TAK


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