|
I had already considered the MONMSG followed by WRKOBJLCK to be my only resort. Unfortunately it does not (I don't believe nor does IBM) return control back to the CL so that I may perform these tasks until after the CPYLIB command completes. It takes over an hour for the CPYLIB to complete. I assume I would run into the same problem trying to use the API? Thanks for your help. :-) -----Original Message----- From: Simon Coulter [mailto:shc@flybynight.com.au] Sent: Thursday, January 14, 1999 3:44 PM To: MIDRANGE-L@midrange.com Subject: Re: Object lock culprits Hello Roger, Assuming the locks are applied by other jobs rather than internal tasks the WRKOBJLCK command should show them. If you want to determine the locks programmatically the List Object Locks (QWCLOBJL) API should do it for you. It is described with the Work Management APIs rather than the Object APIs Regards, Simon Coulter. //-------------------------------------------------------------- // FlyByNight Software AS/400 Technical Specialists // Eclipse the competition - run your business on an IBM AS/400. // Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 // Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au // // Windoze should not be open at Warp speed. //--- forwarded letter ------------------------------------------------------- > X-Mailer: Internet Mail Service (5.5.1960.3) > Date: Thu, 14 Jan 99 14:35:53 -0800 > From: "Roger Boucher" <RBoucher@stanpac.com> > To: MIDRANGE-L@midrange.com > Reply-To: MIDRANGE-L@midrange.com > Subject: Object lock culprits > > I am running a CPYLIB and the last few nights I have found that there > have been some object locks which are preventing some of my data files > from copying. This is a process that has been in place for awhile > without any such problems and there are no users on the system (QINTER > is ended). I am trying to find a way to determine what is locking these > files AT THE TIME THEY ARE BEING LOCKED. I think I already know the > answer... tough bananas... but anyone have any ideas? > > Thank you for your consideration. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.