If you use the N2O Autocompile feature, does PREDICT have to exist in the Development, Test, and Production environments at the site?
N2O Autocompile requires that files exist in PREDICT, just as CATALL does. If programs are to be cataloged against views of those files, the correct files must be in PREDICT for any environment where Autocompile is to occur. Question: Does N2O permit an application to be defined, so that when an object is moved into the application library and should operate on different databases or files, it is automatically changed to point to the new databases or files? Answer: Yes. By using the Autocompile feature of N2O, it is possible to ensure that applications are automatically recompiled in the application library. This will ensure that the applications are automatically updated to point to the new databases and files. This is different from other products, which offer “translation tables” that must be continually maintained by the site. Such translation tables have reportedly required constant effort to keep current.
Related Questions
- Does PROFILERs overhead affect how and where a site should use the product? Is PROFILER more likely to be used in Development/Test environments than in Production environments?
- If you use the N2O Autocompile feature, does PREDICT have to exist in the Development, Test, and Production environments at the site?
- Does N2O have to be installed in each environment at a site (e.g., TEST, PRODUCTION, DEVELOPMENT, and QA)?
