|
You are correct, sir! Eventually, a CL program gets called which changes
the Run Priority of the job (CHGJOB RUNPTY(11)), adds the physical file
member, then changes the Run Priority back to the original priority. This
CHGJOB command is what causes the error message, not the OVRDBF. I suppose
the changing of the Run Priority is for performance reasons (the entire
process is vendor-supplied) and whether it should be used is open to debate.
Nevertheless, what would one do to allow this to work (given that the
program itself cannot be modified)?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.