× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE:Releasing Locked Objects
  • From: John Carr <74711.77@xxxxxxxxxxxxxx>
  • Date: Fri, 11 Sep 1998 20:16:06 -0400



RE:     Releasing Locked Objects

>Hi, does anyone know how to release an object that is locked?  For example,
>I want to copy a file over at night, but if its being updated it will not
>let me.  Is there some way to wait or take control of the file?  If there is
>someone way to wait and then take control and then give it back or to just
>make whomever or whatever release it that would work too.  
>Gary Lehman

Why are you getting a an error on the CPYF ?  It doesn't seem like you
should get one since the CPYF's Open is for Read Only. If you have a file
that you can't get a shared-lock on to do a CPYF, it would seem that you
have worse problems than not being able to do a CPYF.   Is someone else
doing an Exclusive ALCOBJ ?  If so they better have an extremely good reason
AND a note from their mother, or else "Hang Them".

I would use the ALCOBJ as the VERY, VERY, LAST resort.  You have no idea
what you are about to do to the whole application base.  Lets say you do 
grab the object lock with the allocate,  and for some reason your CPYF
has an error and the message sits on the system console over night.
If you have any other process that uses that file,  YOU just broke them.
They'll go down with a CPF message as sure as (Fill in your favorite cliche).  
And I'll guarantee that the rest of your application base is NOT monitoring
for exclusively locked objects in every program.  (Maybe the programs that 
will blow up will be something un-important like "Daily Cash Posting" or the
 "End of Day" routine.)

So before you do something as drastic and as close to as dropping a "depth 
charge" into your apps,  find out the reason you CAN'T do the CPYF with it 
being just an "Open for Read Only"  situation.   

Of course those are just my opinions and are limited by my 18 years of 
experience, and are probably wrong.

John (my opinions are worth what you paid for them) Carr
EdgeTech



+---
| 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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.