|
> Why would you want the lock to persist when the file isn't open? > Getting rid of the lock sounds like a good thing to me. For the same reason why you might do an ALCOBJ for some file, data area, program, or other QSYS.LIB object: so that one job can keep all other jobs out of that object. In this case, it is a client-server application, and the idea is to download the object to the client for modification, lock all other jobs out of the object, then release the lock when the client either uploads the modified object, abandons the modification process, or disconnects (and ends its associated server job). -- JHHL
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.