|
>From what I read from the infocenter, > there are a few sql variables to check > to make sure there were no errors... > But I was wondering if sqlcod was > enough... I'd use SQLSTT instead of SQLCOD. You might see better performance if you don't use a dynamic statement. Something like this might work: c eval julianChar = %editc(julian: 'Z') C/Exec Sql Declare C1 Cursor for C+ Select distinct prpoid from pmppr C+ where prhreq= :julianChar and C+ prco < ' 090' C/End-exec The reason you may see better performance is that you are giving the optimiser the ability to create an access plan (at compile time). Anyway, something to mull. --buck
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.