THEN I WILL USE SUPERC to compare the copy and original and add the changes to the original file. SO THIS WAY MULTIPLE USERS CAN HAVE A COPY AND CHANGES WILL BE SAVED LATER. and then deleted
hope this answer ur question also
THIS WILL ALL BE ACCOMPLISHED USING CODE NO MANUAL PROCESS
Before this is ever
released to someone to use, suggest you make a couple of backup copies of any pds involved. . .
What you propose will only automate the corruption of the primary library. If 5 users are able to make changes to the same module, it will not take long before some user makes a change that destroys some other user's recent modification. Keep in mind that multiple users will make changes to the same parts of the code and there will be no way for the process to determine which change should take precedence.
For example, if Fred makes a change on Monday, and Mary makes a change on Tuesday and promotes this and you make a change on Wednesday and promote your change, then Fred promotes his change, your change and Mary's change will be undone or broken.
A most important part of products like Endevor and Changeman are to protect against this very problem (multiple updates to the same source).