| Title: | FOCUS, from INFORMATION BUILDERS |
| Moderator: | ZAYIUS::BROUILLETTE |
| Created: | Thu Feb 19 1987 |
| Last Modified: | Mon May 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 615 |
| Total number of notes: | 1779 |
I'm back with another question. The proposal that I am working on
deals with an online system of about 60-80 users. This number must be
expandable to +75%. To be honest, I am fighting the use of FOCUS for
this. I feel that the sloution is for a true TP system (ACMS etc.).
However, I am getting a lot of pushing back from others about still
using FOUCS. I am concerned about response time, Rdb locking etc.
People here say that internally Digital has 300 licenses - so why would
we have so many licenses if this product was not that good?
What I would like to find out is how people are using FOUCS. My
'naive' guess would be for end user reporting and queries and NOT for a
real TP system. Any informations such as support from IBI, number of
concurrent users, size of VAX, etc would be appreciated. I want to make
sure that we give the customer the correct solution. He is asking for
a 4GL - in my opinion it is just a buzzword to him and he thinks that
this application (about 20-30 transactions) can be rewritten in a few
weeks with a 4GL.
Any information is greatly appreciated!
Dave (AUNTB::KULVETE or Dave Kulvete @GNO)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 337.1 | In the Old europe | MACAN::MACCANI | Thu May 03 1990 10:50 | 31 | |
In the old Europe Focus is used mainly for reporting end End user query as you said. Consequently the experiencxe is not high in the transactional field; I insert here-after a note from Glen Addelton detailing one of the problemms found with RDB. Note 138 FOCUS notes file (SHIRE::) We have noticed here in ADG that when using FOCUS with Rdb databases, FOCUS will bind to our database _ONCE FOR EACH RELATION/VIEW USED_. I guess FOCUS is treating each relation as a file, and so doesn't really care that they are all in the same database. This means that when running reports, each user is typically bound to the database several times - in our case typically 6 times. Although there are performance implications with this at bind time, as long as no-one is doing updates from FOCUS it shouldn't be too much of a problem as it still seems to run faster than the equivalent RMS system. However, one must be careful not to exceed the maximum number of users for the database. The default for this is 50, which means 9 of the above type of reports, running on the same cluster would blow this limit. Does anyone know if maybe we've described our database to FOCUS in a way which might be causing this - to paraphrase, is there a work-around which can stop this happenning? Failing that, is it likely to be addressed in a future release of FOCUS? Thanks for any assistance, Glenn | |||||