|
Mark: On Wed, 13 February 2002, "Mark Phippard" wrote: > If it is your own command, then you should change the CPP to ALCOBJ *EXCL > on some *DTAARA object and release the lock when it is finished. Just out of curiosity, why lock an external object? The lock can still be established against the *PGM object even if the program establishes it itself. And subsequent attempts will fail until the lock is released. Although establishing a lock will not prevent a program from being run, the lock still exists and can be tested. I suppose the program could even adapt itself by retrieving its own name so that a rename wouldn't upset the basic scheme, though renaming the object of _any_ lock attempt can be trouble. Tom Liotta -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
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.
midrange.com
