On 28-Mar-2012 15:16 , DeLong, Eric wrote:
I would also mention that changing that system value seems to be
safe for most systems, especially those here in the US, where CCSID
00037 is most common.
Setting the value in a User Profile limits the scope, and allows
customization according to the environment\language specific to the user.
For this specific case, you might just try this before your
CHGPF FILE(QTEMP/SQLTEMP3) CCSID(037)
The CHGPF is best avoided to change the CCSID of a database physical
file, except for source files, and only when the text data in all of the
source members is known to be in the newly specified CCSID; i.e. just
tagged incorrectly presently. The original design intent of the CHGPF
CCSID(specified) is to assign a CCSID from when before CCSID support
existed, and thus has [potentially undesirable] consequences beyond just
changing the CCSID of the column(s); i.e. all /text/ CCSIDs for the file
are set to the specified value even if they are already correct, and for
which LABEL and COMMENT would have to be re-applied to recover. AFaIK
the support is not modified to be in any way /smart/ about avoiding that
Also as the OP already responded, a database /flat file/ [aka a
program described database file] can not be assigned a CCSID because the
flat file is inherently undescribed... just rows\records of binary data
of the fixed record length.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.