|
I do agree with your opinion regarding JBA and System 21 bugs, however I feel your comparison of System 21 and all other AS/400 software vendors is unfounded. I have been a user and developer of software on both the AS/400 and Windows NT for many years and feel the AS/400 and the software on it is much more stable than much of the stuff I have seen on NT. I don't think you can characterize all AS/400 vendors in with JBA International. I simply think the System 21 software is simply lacking stability. -----Original Message----- From: Rob Rogerson <rogerson@interlog.com> To: 'JBAUSERS-L@midrange.com' <JBAUSERS-L@midrange.com> Date: Saturday, June 13, 1998 7:01 AM Subject: RE: Record Locks >I agree that this is a painstaking task. If a program has dumped is it not >JBA's responsibility to find the route of the problem and fix it? It seems >to me (my only experience is with PRMS, System 21 and MAPICS on a 36) that >the vendors on the AS/400 platform create these applications that are >functionally robust, but error prone. It seems that this is acceptable on >this platform but would never be allowed on other platforms (NT, Unix). Am >I alone in this feeling? > >Back to your problem. If a dump is produced then JBA should fix it so the >fix can be included in the next PTF or how ever they actually create fixes. > If the fix is made locally, by the client or a regional JBA office, and >never reported and fixed in the UK the bug will continue to exist >throughout the development of System21. > >Rob Rogerson > >-----Original Message----- >From: Jim Sehi >Sent: Friday, June 12, 1998 2:28 AM >To: JBAUSERS-L@midrange.com >Subject: RE: Record Locks > >Yes, we have thought of this.... But I don't have a clue how a staff of 4 >people are going to address record locks for up to 400+ users... ouch! >Maybe we'll be ok... > >At 07:12 PM 6/11/98 -0400, you wrote: >>Jim, I see you have had a good response to this. One point that I would >>like to make (I'm sure that you have considered this but...) normally a >>record lock remains because some program at some point dumped. Make sure >>that when a record lock exists a reasonable effort is make to distinguish >>what caused the record lock in the first place. If the original program >>which caused the lock is fixed then eventually you will get a lot less >>records left locked. >> >>Rob Rogerson >> >>-----Original Message----- >>From: Jim Sehi >>Sent: Wednesday, June 10, 1998 6:02 AM >>To: JBAUSERS-L@midrange.com >>Subject: Record Locks >> >>Has anyone else had problems with record lock issues besides us? >> >>I have found many files such as SLP99 that contain record lock >information, >>but have also found "active" flags within order entry that indicate the >>order is in use (ACTF40 in file OEP40), but don't provide any further >>information in regards to who owns the lock. >> >>What solutions have others standardized on for resolving record lock >issues >>when the system goes down, etc? >>****************************** >>Jim Sehi >>Sr. Programmer/Analyst >>Hach Company >>5600 Lindbergh Drive >>Loveland, Colorado 80538 >> >>Email: jsehi@hach.com >>Phone: 970-663-1377 x2538 >>Fax: 970-669-2932 >>****************************** >> >>+--- >>| 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. >>+--- >> >> >****************************** >Jim Sehi >Sr. Programmer/Analyst >Hach Company >5600 Lindbergh Drive >Loveland, Colorado 80538 > >Email: jsehi@hach.com >Phone: 970-663-1377 x2538 >Fax: 970-669-2932 >****************************** > >+--- >| 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 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.