|
SQL's CREATE TABLE creates an externally described file much like DDS does. For externally described files the job CCSID (or job default CCSID if the job CCSID is 65535) is used by default for character fields. In the case of externally described files/tables 65535 is not used unless you specifically ask for it. It was really this desire to avoid 65535 tagged files that drove the introduction of job default CCSIDs back in V3R1. Prior to that most files were 65535 -- which caused nothing but grief when the system would try to convert the data to another encoding (like ASCII for instance). Bruce Jerry Adams <jerry@xxxxxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 05/26/2006 07:36 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: CRTPF and job CCSID Bruce, Does the 65535 setting also apply if the file is created with SQL's CREATE TABLE function? * Jerry C. Adams *IBM System i Programmer/Analyst B&W Wholesale Distributors, Inc.* * voice 615.995.7024 fax 615.995.1201 email jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx> Bruce Vining wrote: >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 > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.