It looks like CPYTOIMPF in V6R1 is now treating the parms exactly as documentedâthe FROMCCSID in the below cpytoimpf defaults to *FILEâand the temporary flat file RSPQSPRCCV is 65535. So according to the help below, cpytoimpf will not convert the flat file data. Unless the FromCCSID = 37 or the FromFile is a database file (could use gmiddsc dds(#5000) to create the file with one field). I'm really surprised that this issue did not come up beforeâI remember this issue back in the V5R3 to V5R4 upgrades.
*FILEÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
 The data is converted from the from-file field CCSID. If the CCSID
ÂÂÂ of the from-file field is 65535, the field is not converted and it
ÂÂÂ is treated as binary data.ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ
Â
CPYTOIMPF FROMFILE(QTEMP/RSPQSPRCCV) fromccsid(*FILE --> 37)ÂÂÂÂÂÂÂÂÂÂ
ÂTOSTMF('home\RSPData\srocdran.csv') MBROPT(*REPLACE) STMFCODPAG(*PCASCII)Â
ÂRCDDLM(*CRLF) DTAFMT(*FIXED) STRDLM(*NONE)
Â
The issue I am having is that the data within certain fields is not converting properly (below RCODE and RDESCR fields). Changing CCSID(37) fixed it. The problem is we have nearly 500 programs where we need to change CCSID to 37, which is tough task, I am trying to find if there is any easy solution (perhaps any PTF???)Ârather than Âgoing through all 500 programs and changing them to 37.
Â
RABCID|RCODE|RDESCR|RDD|
T|Ã|ÃÃÃÃ@ÃÃÃ`ÃÃÃÃ|57|
T|Ã|ÃÃÃÃ@ÃÃÃ`ÃÃÃÃ|57|
RCODE is definedÂasÂ1 CHAR and RDESCR is defined as 30 CHAR.
Thanks,
Donna.
--- On Sun, 1/17/10, CRPence <CRPbottle@xxxxxxxxx> wrote:
From: CRPence <CRPbottle@xxxxxxxxx>
Subject: Re: cpytoimpf issue - v6r1
To: midrange-l@xxxxxxxxxxxx
Date: Sunday, January 17, 2010, 2:10 AM
ÂÂÂAFaIK the job CCSID is used by the CPYTOIMPF only for treating
the literals on the command, not for [overriding] the columns\fields
of the database file. Thus the problem is presumably with how the
file was created. That is, I expect that the "temporary file" noted
was created as a program-described file [e.g. CRTPF
RCDLEN(specified) or BLDFILE], which has no support for a CCSID of
its [effectively] one column\field. Remove the temporary file from
processing, or use a temporary file which has its text field(s)
assigned with a CCSID which properly describes the data.
ÂÂÂAs to QCCSID and job CCSID [the question "What is ..." seems
incomplete], the user profile is IMO the best place to define the
CCSID appropriate to the user for their default\expected language
environment. Thus CHGPRF CCSID(desired), and the job CCSID will
automatically be set from that value.
Regards, Chuck
donna lester wrote:
Since the V6R1 upgrade we are having issue with CPYTOIMPF
conversion issue, the implicit data conversion is using the job
CCSID (which is using the system value QCCSID) which defaults to
65535. 65535 means that data conversion will not implicitly
convert the data. So when I build a temporary file, it will
default to the job ccsid 65535. And when I run the CPYTOIMPF to
an ASCII stmf file, the data conversion is ignored and the ASCII
file looks like garbage.
What is the IBM solution other than changing QCCSID system value
to 37 or something thats not 65535 / using CHGJOB CCSID
midrange.com
