An ABORTJOB could not interrupt an Image operation in such a way as to result
in broken chains.

If an application isn't using logical transactions and is just doing DBPUT's or
DBUPDATES singularly then an ABORTJOB could interrupt the process in between
those operations leaving some data in the database and some not.  Whether logical
transactions are used or not all operations on the database are covered by transaction
management so any I/O in progress at the time of an abortjob will either complete or
be completely rolled back.

So, no an ABORTJOB cannot cause a broken chain in a database.

HTH

Bill
HP/CSY


> A programmer asked me if doing an ABORTJOB on a program will cause a broken
> chain in an Image database.
>
> Also we've seen cases where one record out of two will be on a database.  We
> suspect that the second record didn't make it because of an ABORTJOB.  In
> this case I was attempting to tell the programmer about the concept of
> logical transactions and using DBBEGIN and DBEND.  The programs are not
> written with the concepts of logical transactions.  They just write one
> record then a second.
>
> So, does using ABORTJOB cause IMAGE problems?
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>

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