On 30-May-2011 10:41 , CRPence wrote:
I think my mention for concerns for *JOB scoped override must have
been off the mark. I just did a quick test, and from the results
seen, I infer I had incorrectly recalled the reverse effect. Seems
that a *JOB scoped override is _later_ in the search order than a
call-level scoped override.?

Scratch that... I had inferred too much from order of presentation with the non-merged override view, rather than looking at the effect of [and as presented with the view of] the merged overrides. I should have tested with an actual open rather than only looking at DSPOVR output :-!

FWiW: I also verified in a test that the overridden-to file name was visible in the SQLERRMC data for both the OPEN Csr-Name and the UPDATE WHERE CURRENT OF Csr-Name requests; the former had the cursor name Csr-Name preceding both the file and library names, while the latter had only the file and library names.

Regards, Chuck

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].