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:
Gibson Nichols <[log in to unmask]>
Reply To:
Gibson Nichols <[log in to unmask]>
Date:
Fri, 3 Aug 2001 15:30:46 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines) 
Great.  Thanks for all the feedback.  I've confirmed some of my long
standing suspicions and learned some new things too.

"Gibson Nichols" <[log in to unmask]> wrote in message
news:9ke9ri$pft3@eccws12.dearborn.ford.com...
>
> 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 *

ATOM RSS1 RSS2