@Urban_Science wrote:
...
The biggest challenge with using Dev/Test/Prod environments is not the SAS program file references, instead it is library references for where SAS data sets are saved to. When using Dev/Test/Prod environments, the last thing you want to do is overwrite a file in production when you are currently trying to develop something. My solution to this is to add a config file/process settings file to the beginning of the EG flow and then to update that file with the path to save/reference data sets.
...
This problem can be partially solved by using different levels / configurations for each environment. Additionally developers should not have any access rights to production environments, preventing unwanted changes of data or code. Unfortunately all steps i can think of, aren't capable of solving all issues, e.g. if you are using libraries defined in metadata and multiple developers are working on the same project, i can see no way to prevent conflicts without using different library names and having to rename (edit code) before the project is moved to test/prod.
... View more