HP3000-L Archives

August 2001, Week 1

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Does ABORTJOB cause Image broken chains?
From:
Dennis Heidner <[log in to unmask]>
Reply To:
Dennis Heidner <[log in to unmask]>
Date:
Mon, 6 Aug 2001 14:15:24 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (21 lines) 
>>I've seen six broken chains(different systems all on 6.0) in the past
twelve
months.

But that doesn't mean abortjob is causing the problem.

Each process running has a special hook put into it such that when it
terminates AND the process has a Image database open, the abort process
handler is called.  It ensures that the database is closed in an orderly
manner.

Broken chains, could be a symptom of an TurboImage bug,  defective
hardware,  using deferred posting AND system aborts.

Phantom broken chains can be reported if you are using a weak locking
scheme, i.e. changing key value or deleting entries while another process
is walking the same chain.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2