×
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.
-----Message d'origine-----
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Charles Wilt
There's no possible way a SHARE(*YES) could cause your job to
affect his job.
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.
The coworker was testing a nightly batch job, after I'd installed my program on the test machine. My modification was the call to myPgm from a procedure used by the batch job.
ie:
CLP : OPNQRYF MyFile
Call RPGPgm
CallP MyProc
Call MyPgm (that also uses MyFile).
We are more and more developers on the test machine and often walking on eachother's toes. This time, this has been an advantage. Without my coworker's test I'd never have seen the problem. The solution, by the powers that be, is to always use a different name for the file of the opnqryf in the future.
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.
midrange.com
