Re: CPYTOSTMF and Codepage problem

["Steve Moland" <steve@xxxxxxxxxxx>]

Scott, your suggestion was what I suspected would be correct and I think I 
expressed that CPYTOSTMF "should" be able to do it. My frustration was that 
I had tried that parameter many times a few weeks ago and had no joy in the 
hours I messed with it.

I tried every CCSID number I could find a reference to by googling.  The 
fact that "codepage" and "CCSID" are tossed about together I wasn't sure 
whether they are really the same or only the same "depending" on whatever.

I had no success just now trying your suggestion UNTIL I accidentally 
stumbled on a "How the hell would I know that?" pearl cast before this swine 
(me) by Mr Aaron Bartell.

His suggestion for first creating the file programmatically was

QSH CMD('touch -C 819 /CDPREPDVD/tcodepage.dat')

That worked great, and since I was asking a codepage question I assumed that 
Aaron's '819' was a codepage

I tried feeding 819 to the CPYTOSTMF and it didn't work, BUT since I had a 
existing file out there I got the following message.

 Message . . . . :   Code page attribute does not match STMFCODPAG 
specified.
 Cause . . . . . :   The destination stream file /CDPREPDVD/tcodepage.dat
   exists and the STMFCODPAG value 819 must equal the stream file's code 
page
   attribute 1252 for successful completion of this command.
 Recovery  . . . :   Set STMFCODPAG parameter value equal to the stream file
   code page attribute 1252, then submit the command again.

Prior to this I had not tried to use the STMFCODPAG parameter with a file 
already existing.

SO, now that I know that CCSID 1252 works so well, I googled "CPYTOSTMF 
codepage 1252" and in typical Monday morning quarterbacking style there are 
plenty of references to 1252.

How would I have known about 1252?

Anyway, thanks all for the excellent help that you guys provide so often.

regards for an enjoyable holiday season.