× 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: "Mark Willett" <oleblighty@xxxxxxxx>
  • Date: Tue, 11 May 1999 11:38:14 -0700

What is the cause of the xxP99 records being left out there:

1.    Program failure
2.    PC failures
3.    Network failures
4.    User not loggging out of JBA correctly.
5.    Other

If it is no.1 the get JBA to fix their suff.  If it's nos. 2-4 then you can
do something about the cause and not the probelm.  If it is no. 5 then I
have no idea....

Most companies running JBA do NOT have many xxP99 records (if any) on a
regular basis.  Those that have, usually because of 3 and 4 above, put a
small CL or RPG progarm into the overnight routine to clear the required
records.  CL is fine for the financial systems with CLRPFM, but I believe
that Inventory/Wharehousing require certain records in the INP99/WHP99 files
to control their background update jobs.

If you want to e-mail privately, so as not to bore the non-JBA'ers out
there, please feel free.



----- Original Message -----
From: Jim Sehi <jsehi@hach.com>
To: <JBAUSERS-L@midrange.com>
Sent: Tuesday, May 11, 1999 10:19 AM
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.
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.