|
Bill Robins wrote: > "The CCSID of the current job is different than the CCSID of the job that >last > created this access plan." > > The job's CCSID is 37, so is the file's. I guess the question is how do I get > the plan to reset and use the CCSID 37? Or am I missing something else? The system is normally defaulted to 65535 (or something). Chances are the program was compiled while the CCSID was that default value, or some other and you have (or someone) has changed everything to 37. So... recompile. The access plan is built for static SQL during the compile. ... unless there is a "rebind" or something similar for the *SQLPKG... oh well, in any event, a recompile should get you there. And by recompile I mean an SQL recompile that invokes the preprocessor. -- =========================================================== R. Bruce Hoffman, Jr. -- IBM Certified AS/400 Administrator -- The sum of all human knowledge is a fixed constant. It's the population that keeps growing!
begin: vcard fn: R. Bruce Hoffman, Jr. n: ;R. Bruce Hoffman, Jr. adr: 991 Lucon Road;;;Schwenksville;PA;19473;USA email;internet: rbruceh@ibm.net title: Independant AS/400 Consultant tel;work: 610-222-9707 tel;fax: 610-222-9717 x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.