×
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.
Charles St-Laurent wrote:
Can we consider a subsystem as a job? Can we associate this job to a named
activation group? And if I open database files in that named activation
group and don't close the files, will the ODP of that named activation group
shared to all the (interactive / batch) jobs that are launched in that
subsystem?
Charles:
I'm not sure that you _really_ want ODPs shared across multiple
jobs. Try to picture the result if different, unrelated jobs were
always changing the file pointer to different parts of the file!
What record would be read the next time any job executed a simple
READ op-code? Similarly, file status info, at least some storage
areas and possibly other elements, would also be shared and could
potentially cause chaos.
IIUC, native I/O within a job can be influenced by the OVRDBF
SHARE(*YES) setting; but SQL does any sharing through its own
methods and SHARE(*YES) is ignored. Either way, going _across_ jobs
would be begging for trouble.
Tom Liotta
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
