When code can be compiled and executed locally, I would expect an application to follow this model:
Local Development <--> Source Control --> Remote Target
Applying this model to our environment, in which we are working with Natural for the Mainframe, is proving tricky. Right now we are trying something like this:
Eclipse (local) <-- Mainframe (remote) Eclipse (local) <--> Subversion (source control) Eclipse (local) --> Mainframe (remote)
This works, but it leaves open the possibility that the source code put on the Mainframe does not match the source stored in Subversion. I’m comfortable with this model for libraries under active development, but not for stable libraries. I’d like to ensure that our stable libraries do match our Subversion stores.
How does Software AG recommend this be configured? I read the help document on Architecture, but that didn’t answer this question for me.