RE: IFS - CPYTOIMPF

[Steve Cotes <Steve@xxxxxxxxxxxxxxxxx>]

Vance,

This is a command that I think needs a bit of work,
you are not alone in finding it frustrating.

If you are copying or creating a file in the IFS
then the TOCCSID parameter is ignored, it is used
when you are specifying the TOFILE (data base file)
parm.
In the IFS, if you are creating a new file it appears
you get the CCSID of the FROMFILE. If you are
copying (or replacing) an existing file, you get
the CCSID of the existing file.

By using FTP to create files I found that 819 was
the CCSID that gave me the translation I needed.

So to use this command, I keep a dummy file around
with CCSID 819. Then I make a copy of the dummy file
giving it the name I'll use in the TOSTMF parm.
Then when I run the command I specify MBROPT(*REPLACE).

There should be an easier way, but I haven't found it.

 - HTH,
 - steve cotes
 - steve@returnsonline.com




-----Original Message-----
From: Vance Stanley [mailto:w_vance_stanley@yahoo.com]
Sent: Tuesday, January 02, 2001 2:18 PM
To: MIDRANGE-L@midrange.com
Subject: IFS - CPYTOIMPF


Sorry about this because I think its been covered
before but I am having trouble with the CPYTOIMPF cmd
when I use it to copy from a db2 file to an IFS /ROOT
strm file. It looks as though I am not getting it to
Convert to ASCII. I have provided it a CCSID of 00037
and I have tried others as well. Maybe I am missing
the point and this command does not do the conversion.
If this is the case then I know of other was to
accomplish what I need. 

Thanks in advance!

   

=====
W. Vance Stanley
Sr. Programmer Analyst
DEVON SFS OPERATING INC. 
Houston, Texas
713-507-5536

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