Re: CRTPF and job CCSID

Brad,

CRTPF with no DDS and FILETYPE(*DATA) will always create a file with 
CCSID(65535).  This can be found in the help text behind the CCSID 
keyword.

Not using DDS is essentially an indication the the file will be program 
described.  And as the file is program described it may very well contain 
data in formats such as packed and binary.  If this were true then the 
last thing you would want is for the system to start doing CCSID 
conversions for the file treating, for instance, packed decimal data as 
character.

Bruce Vining




"Brad Stone" <brad@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
05/25/2006 11:35 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Subject
CRTPF and job CCSID






I was under the impression that when you issue a CRTPF (no
DDS, just specifying record length) that the CCSID of the
file would be the job CCSID.

I have a case where a user has job ccsid and default ccsid
f 935 (trad chinese).  When they issue CRTPF it creates the
PF with a ccsid of 65535.

Any ideas?  I have to be missing something here.  :)

Brad