The MACLIB is updated via PDF dialog table services, driven by a number of older REXX EXECs. It contains hundreds of members, which can be updated at any time, and new members are added every day.
I'm unsure if ISPF/PDF "locks" a member, or a table row, each time it's updated. Nevertheless, in order to compress the maclib we'd like to completely halt any possible update activity. Some sort of global ISPF command that I haven't found yet, perhaps. The application runs ISPF in the users' individual virtual machines. ISPF does have a service machine, which runs mysterious "ISPF Services." ---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?
