|
Sorry, everyone. I have led you astray. Let me try again. I have a set of SQL's running in batch (using Pro Data's SQL4/Less product) that is taking longer than I would like. So, I started debug and set the job parameters to tell me everything that is going on. -- We are running under V3R2. Here is what is disturbing me: some of the access paths that -I- would have chosen to use in the query are not used due to reason 8 - "The CCSID of the current job is different than the CCSID of the job that last created this access plan." I would think that if this were a true message that the current run of this job would reset that access path so that the next run of this program would not create this message, but that is not true. 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? Bill +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.