Re: D3 b-tree problem

Hi Tony
I do do a READU and RELEASE but it seemed to me that this was putting
unnecessary load on the system when all I want to know is is it locked or
not.
I am fascinated by the remark about the company running on UPDATE because I
understood Rick Davies to say that they were dumping it, maybe he just
meant the VME.
Peter McMurray
"Tony Gravagno" <g6q3x9lu53001@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8c1ls11m0v0t4ho9lc60p7to6b1f618lf2@xxxxxxxxxx
> "Excalibur" wrote:
> >Why for example does the READ statement not return a LOCKED message, it
may
> >be important and it may not but I need to know.
>
> If you want to know if a record is locked, why not do a
> READU/LOCKED/RELEASE? I understand the inelegance of this but if the
> rest of your code is as attentive to how locks work then it shouldn't
> be a problem. If you really want to avoid locking in order to check a
> lock then you could parse the lock table or you could use system level
> LOCK/UNLOCK for the purpose - more inelegant solutions but feasible.
> I'm not refuting the request but as we see here many times, when
> someone says "why doesn't it do X", it turns out that it doesn't
> absolutely need to be implemented systemically because there are other
> ways to accomplish the same task.
>
> >As for REF I believe that you will find it is not the indexing so much as
> >the lock in of UPDATE that causes the grief. A bit like General Motors
who
> >are now loosing 5 billion a year for not listening to customers, I really
> >hope not as I just do not want to have to switch suppliers. I really
never
> >got cruise and zoom to work so I just use <ctrl><alt><e>. A proper
document
> >with some sensible worked examples of more difficult concepts would
> >certainly improve it.
>
> Now that you mention it, REF is one of the best examples available of
> extended use of the Update Processor. Just put it into the VME. RD
> makes extensive use of UP internally - most of the code was originally
> written when *** was on the No WIMPS kick and no one had PCs, but the
> company still runs on it. It would be great for them to publish some
> of their code as examples of extended UP usage, but that'll never
> happen for various reasons.
>
> T


.