Sure it can.  You abort a job at the wrong time, and you may be looking at a
damaged database.

Gibson Nichols wrote:

> 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 *

--
Ron Horner
HP3000 Systems Administrator
JCPenney Logistics
[log in to unmask]
(414) 259-2274
AIM: hornerrr

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