RE: ovrdbf SHARE parameter -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

The open data path that is shared is shared _within_ a job,
not across jobs.

Charles, <sigh>even I would realise that </sigh> I didn't see where I
mentioned different jobs.

David, <sigh>I thought the same thing when I read your post</sigh>.

You said (paraphrasing since I don't have the original here) that CLP (which
I hope is actually CLLE) does: OPNQRYF followed by CALL TESTPGM... and
TESTPGM uses the same filename.

Do you have also specified OVRSCOPE(some_value) on the OPNQRYF... and/or
have you utilized OVRDBF ... in some fashion? (What are the parameters?)

Also, it sounds like you're saying you don't want TESTPGM to use this file,
but rather the original. Is that right?

Since this is new development, do you have good reason not to use inbedded
SQL in your application(s)? While it still works, OPNQRYF is rather
outdated for new development (or so it seems to me, given the other
options).

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"The Yankees, as I told you later, are in a slump."
-- baseball great Dizzy Dean

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.