RE: CL problem

If you don't have the ptfs for cpytoimpf that allow you to specify the code
page of the destination file, you'll have to create it first using cpytostmf
(codepage *PCASCII) or a PC text editor.  You should then be able to use
cpytoimpf directly.  

If you have the ptfs for cpytoimpf, you can copy directly,  *pcascii.  

We have been using this a lot in the last few months, both batch and
interactive since I learned the code page trick right here on this list.
Are you sure you're using the same parameters for the command in the CL and
on the command line? 

-----Original Message-----
From: Draper, Dale [mailto:dale.draper@seu.sega.com]
Sent: Friday, June 23, 2000 2:01 PM
To: 'MIDRANGE-L@midrange.com'
Subject: CL problem


Curious problem, I am creating a flat file to be read by a PC by using the
CPYTOIMPF and then CPYTOSTMF commands. This works perfectly when run off a
command line, however when I put this into a CL it is not translating, in
fact it does not even look like a normal untranslated file, just a bunch of
garbage.  
Has someone come across this and know of a fix?

TIA

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