× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: JBA System/21 Record Locking
  • From: Jim Sehi <jsehi@xxxxxxxx>
  • Date: Wed, 12 May 1999 08:39:23 -0600

I find it hard to believe that other companies are not seeing the same
magnitude of problem we are.  We have hundreds of employees in JBA all day
long, many of them using Explorer.  There are many things that can happen to
cause the residual locks such as power outages, network connection failures,
abnormal job terminations, etc.  If they close the task via Explorer
improperly, this also can cause problems.

I would say that 98% of the time, we know why the jobs are terminating
abnormally... these are caused by users closing Explorer sessions improperly
or communication problems.

-----Original Message-----
From: Dan Thomas [mailto:DThomas@lpw-mdi.com]
Sent: Wednesday, May 12, 1999 6:25 AM
To: 'JBAUSERS-L@midrange.com'
Subject: RE: JBA System/21 Record Locking


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.
+---
+---
| 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.
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.