From: "Martin, Mike" <[EMAIL PROTECTED]> We have several folks who will be updating parmib and proclib. There is a possibility that we might step on each other's changes. Is there a way to lock member so that only one person can be working on a member (or members) while they have the lock
As you know, a water-tight solution requires the use of a change control product such as Endevor or SCLM (etc). Failing that, one thing that can help is to use merged member lists. For example, enforce a rule that all updates to procs must be performed in a data set called 'UPDATES.PROCLIB'. If the data set is merged with 'SYS1.PROCLIB', the merged member list will show at a glance which procs are being worked on (i.e. exist in Lib 1) and which are not being worked on (i.e. exist in Lib 2).
If a proc exists in Lib 2, simply selecting it for edit will 'lock it' for the length of the edit session. If the member is saved, the member will automatically be copied to and saved in Lib 1, while the member in Lib 2 will NOT be updated.
HTH, Dave Salt SimpList(tm) - The easiest, most powerful way to surf a mainframe! http://www.mackinney.com/products/SIM/simplist.htm ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
