|
Incidentally, this is something that has been tidied-up and rationalised in Aurora. There is now a new 'application' that controls all the subsystems and background jobs, and one set of functions for starting and stopping jobs. It should now be easier to set up test subsystems. We found one rather strange problem with it, namely that if you start your background jobs from the blank environment and then try and stop them from the default environment, the control program dumps. Geac have apparently put in a fix to prevent you submitting the background jobs from the blank environment, but have no plans to put a similar restriction in the interactive programs. Obviously it's easy to avoid this happening, but I had always understood that the blank and default environments should be identical (apart from modification libraries if you have them), and it shouldn't matter which one you use. I have always used the default environment, but I know some Geac consultants who normally use the blank environment. Is the blank environment just something that exists but which you are not supposed to use, or do some people use it deliberately? Would you expect the system to work normally if you selected the blank environment? Regards, Chris
As an Amazon Associate we earn from qualifying purchases.
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.