Access control is an ISPF function, I presume that one of the two locks (LMF or SCLM) is used to prevent concurrent updates of the same member. It must also have some way to serialize the updates of the library. That is an area that I have avoided. I hate working with kludges or black boxes.
The developers of the application chose to have the data maintained in a single, ever-increasing, highly used, frequently updated ISPF library, with no maintenance routines, and no good way to identify obsolete members. The application was already firmly entrenched when Mark and I arrived at Visa. There have been at least three unsuccessful attempts to replace in during my tenure here. The current attempt is nearing completion. With luck, we only have to keep the application running for a few more months. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of P S > Sent: Friday, August 14, 2009 12:32 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: ISPF/PDF CMS MACLIB - Maintenance > > On Fri, Aug 14, 2009 at 2:52 PM, Schuh, > Richard<rsc...@visa.com> wrote: > > Unfortunately, that will not fly with the application. > There are always several users who have the disk MW. It is a > heavily used application and users keep it linked active for > long periods. The main users of it live in the application. > > How is simultaneous use of a library controlled? If I edit > member A, does that "lock" it? If so, could the update > process edit every member, do the update, then quit every member? >
