RE: JBA System/21 Record Locking

[Dan Thomas <DThomas@xxxxxxxxxxx>]

We occassionally have problems with this, but not very often.  The obvious
question is "Why are jobs terminated abnormally?".

> -----Original Message-----
> From: Jim Sehi [SMTP:jsehi@hach.com]
> Sent: Tuesday, May 11, 1999 1:19 PM
> To:   'JBAUSERS-L@midrange.com'
> Subject:      JBA System/21 Record Locking
> 
> We have recently (within that last 2 weeks) implemented JBA System/21
> 3.5.0
> and are experiencing some severe problems regarding record locking.  To
> date, we have encountered JBA tables with 1 byte record lock flags and
> other
> tables typically called xxP99 (where "xx" is the application code).
> 
> When jobs are terminated abnormally, these record locks remain in the
> system, preventing other jobs/users from accessing the data.  The net
> effect
> is a massive number of calls being made to the IS department to manually
> edit the content of the files to remove the active flag and/or delete a
> lock
> record in the xxP99 file.
> 
> Have other companies encountered similar problems (I assume so), and what
> are you doing about them?
> +---
> | This is the JBA Software Users Mailing List!
> | To submit a new message send your mail to JBAUSERS-L@midrange.com.
> | To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> JBAUSERS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner: doug333@aol.com.
> +---
+---
| This is the JBA Software Users Mailing List!
| To submit a new message send your mail to JBAUSERS-L@midrange.com.
| To subscribe to this list send email to JBAUSERS-L-SUB@midrange.com.
| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner: doug333@aol.com.
+---