How does the software determine a true compilation error versus a “job not completed” error from the Software AG return codes?
Because N2O does not use the Software AG utilities for migration, there is no need for the product to determine a compilation error versus a “job not completed” error. N2O Autocompile makes use of the CATALL facility of NATURAL and is able to determine the error codes from the output of the CATALL activity. Question: Is there a way within N2O to define a set of people who can check out objects of an application into a development environment, and a different person who can move the objects of the application into Production? Answer: Yes. By configuring N2O so that all migrations into Production require the authorization of one or more individuals, you can ensure that no migrations are made into Production unless these individuals have approved them. Programmers can check objects out from Production into Development, modify those objects, and request migration into Production. Until approval is given, the objects are not migrated. Thus, the person providing authorization is effectively
Related Questions
- I get an error when downloading the release version of the Macintosh software in StuffIt format. Why would I get an error if I had no trouble with the demo version download?
- How does the software determine a true compilation error versus a "job not completed" error from the Software AG return codes?
- I received a rejected return with an error code. How can I determine what the error code means and how to resolve it?
