|
I'm interested. Charles > -----Original Message----- > From: pam@xxxxxxxxxxxxx [mailto:pam@xxxxxxxxxxxxx] > Sent: Wednesday, August 11, 2004 4:53 PM > To: Midrange Systems Technical Discussion > Subject: Re: Break Object Locks > > > Sorry to respond so late, but we have a crude but effective > program that > checks an object, sends a nastygram to all users locking it, and then > kicks them out. No API's were harmed in the writing of that > code. Let me > know if you're interested. > > Pam Phillips > Sr. AS/400 Systems Analyst > Abbott Laboratories > MediSense Products > 4A Crosby Drive > Bedford MA 01730 > pam@xxxxxxxxxxxxx > 781-276-6144 > Fax: 781-687-5246 > > > > > "Condon, Mike" <M1C@xxxxxxxxxxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 08/06/2004 12:12 PM > Please respond to Midrange Systems Technical Discussion > > > To: "'Midrange Systems Technical Discussion'" > <midrange-l@xxxxxxxxxxxx> > cc: > Subject: Break Object Locks > > > I have resumed this again after getting dragged into several > other, um, > things. See below. > > I have looked at the obvious wrkobjlck in a CL program, but > use of it to > get > the jobs & end them in a CL program was not too obvious. What > methods do > you > all use to accomplish this? > > Original Question: > >> > Is there a way to break all object locks on a file? This > would be used in > batch jobs (CL) before an update program (RPG) or perhaps a > backup is run. > > > Reply: > >> > End all the jobs that have a lock on the file. Do it all the > time in our > backups. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > -- > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing > list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > > > > > -- > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
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.