It is a tool on Mainframe .We will save our modules using them. If any changes are made in our modules, updated module can be saved into them by incrementing the version. In this way we can keep track of all versions.
As u might agree in mainframes environment, multiple users are accessing the same resource and same set of programs, jobs, utlility, procs etc. elements to say broadly.
Now multifarious activities are carried out by onsite offshore, client side and also in some cases by other vendors handling a part of same application,
So there comes a need to monitor these changes
using a version control tool like endevor.
entire repository of elemnets is maintained and the change history is kept intact to facilitate retrofits, over rides, etc.
consider there is a element of
type cobol pgm for
sub system prod
Now if u want to make changes to this element pgm1
u need to retrieve the element using the foreground in to ur pds.
copy it to a production pds(deliverable pds) make changes and add/move the element to the test region ( step wise) and then retain the sign out by putting overide signout =y and signout to ur tso id.[/b]
On compilation the version of that element incremnt by 1 and the previous version is over ridden by your changes,
for the guy making changes in the previous version to acces his change he can directly go to his version and find his changes.
Your chnages although comprises both of his changes last made and also the activity done by u.