Em segunda-feira, 23 de maio de 2022 às 06:21:32 UTC-3, Alex Maslov escreveu:
> On Sunday, May 22, 2022 at 8:35:16 PM UTC+3, OldMster wrote:
> > Using YottaDB as the database server and REST interfaces to the browser, modern hardware should easily handle thousands of browser clients.
> Agreed, we have deployed sites with thousands thin or browser clients running a single server. Scaling such a system is its potential problem. E.g. we are running 2000 users, and we need to add extra 500: usually no problem.. And what if we need a 1000 more? How high can it grow, depends on many factors, and if the hardware becomes the stopper, it needs upgrade, and as all we know, it's usually difficult to upgrade even 5 years old server. So, we need a new one, plus another one for failover.
> > With YottaDB replication, any 'expensive' report generation processes could be offloaded to a replicated database
> This approach looks advantageous. We have an initial version and plan to improve it to achieve transparent report start on report server and returning the results to database server.
>
> Alexey

I'm new to the MSM area, I see that people suggest many things, however, I don't have the knowledge to adopt these suggestions.
Does YottaDB work with routines, globals and windows in the same way as MSM? Here at the institution we have clients working with windows and clients working directly on the terminal.
Is it possible to migrate from MSM to IRIS? Does it work with windows too? I'm confused and lost..

On Monday, May 23, 2022 at 8:33:34 AM UTC-4, ti.h...@gmail.com wrote:
> Em segunda-feira, 23 de maio de 2022 às 06:21:32 UTC-3, Alex Maslov escreveu:
> > On Sunday, May 22, 2022 at 8:35:16 PM UTC+3, OldMster wrote:
> > > Using YottaDB as the database server and REST interfaces to the browser, modern hardware should easily handle thousands of browser clients.
> > Agreed, we have deployed sites with thousands thin or browser clients running a single server. Scaling such a system is its potential problem. E.g.. we are running 2000 users, and we need to add extra 500: usually no problem. And what if we need a 1000 more? How high can it grow, depends on many factors, and if the hardware becomes the stopper, it needs upgrade, and as all we know, it's usually difficult to upgrade even 5 years old server. So, we need a new one, plus another one for failover.
> > > With YottaDB replication, any 'expensive' report generation processes could be offloaded to a replicated database
> > This approach looks advantageous. We have an initial version and plan to improve it to achieve transparent report start on report server and returning the results to database server.
> >
> > Alexey
> I'm new to the MSM area, I see that people suggest many things, however, I don't have the knowledge to adopt these suggestions.
> Does YottaDB work with routines, globals and windows in the same way as MSM? Here at the institution we have clients working with windows and clients working directly on the terminal.
> Is it possible to migrate from MSM to IRIS? Does it work with windows too? I'm confused and lost..

Simple answers this time:

Routines - yes - the same with minor adjustments due to non-standard extensions that might have been used (Z* & $Z* commands/functions)
Globals - yes - the same
Windows - no - these were entirely an MSM 'thing', and no equivalent in any other M system exists that I'm aware of (including IRIS). Multiple options to migrate to, but would be the biggest development effort to migrate to any M except MSM

Mark

Em segunda-feira, 23 de maio de 2022 às 11:45:42 UTC-3, OldMster escreveu:
> On Monday, May 23, 2022 at 8:33:34 AM UTC-4, ti.h...@gmail.com wrote:
> > Em segunda-feira, 23 de maio de 2022 às 06:21:32 UTC-3, Alex Maslov escreveu:
> > > On Sunday, May 22, 2022 at 8:35:16 PM UTC+3, OldMster wrote:
> > > > Using YottaDB as the database server and REST interfaces to the browser, modern hardware should easily handle thousands of browser clients.
> > > Agreed, we have deployed sites with thousands thin or browser clients running a single server. Scaling such a system is its potential problem. E..g. we are running 2000 users, and we need to add extra 500: usually no problem. And what if we need a 1000 more? How high can it grow, depends on many factors, and if the hardware becomes the stopper, it needs upgrade, and as all we know, it's usually difficult to upgrade even 5 years old server. So, we need a new one, plus another one for failover.
> > > > With YottaDB replication, any 'expensive' report generation processes could be offloaded to a replicated database
> > > This approach looks advantageous. We have an initial version and plan to improve it to achieve transparent report start on report server and returning the results to database server.
> > >
> > > Alexey
> > I'm new to the MSM area, I see that people suggest many things, however, I don't have the knowledge to adopt these suggestions.
> > Does YottaDB work with routines, globals and windows in the same way as MSM? Here at the institution we have clients working with windows and clients working directly on the terminal.
> > Is it possible to migrate from MSM to IRIS? Does it work with windows too? I'm confused and lost..
> Simple answers this time:
>
> Routines - yes - the same with minor adjustments due to non-standard extensions that might have been used (Z* & $Z* commands/functions)
> Globals - yes - the same
> Windows - no - these were entirely an MSM 'thing', and no equivalent in any other M system exists that I'm aware of (including IRIS). Multiple options to migrate to, but would be the biggest development effort to migrate to any M except MSM
>
> Mark

Does the cache itself which is the evolution of MSM not have the window system?

On Monday, May 23, 2022 at 1:33:18 PM UTC-4, ti.h...@gmail.com wrote:
> Em segunda-feira, 23 de maio de 2022 às 11:45:42 UTC-3, OldMster escreveu:
> > On Monday, May 23, 2022 at 8:33:34 AM UTC-4, ti.h...@gmail.com wrote:
> > > Em segunda-feira, 23 de maio de 2022 às 06:21:32 UTC-3, Alex Maslov escreveu:
> > > > On Sunday, May 22, 2022 at 8:35:16 PM UTC+3, OldMster wrote:
> > > > > Using YottaDB as the database server and REST interfaces to the browser, modern hardware should easily handle thousands of browser clients.
> > > > Agreed, we have deployed sites with thousands thin or browser clients running a single server. Scaling such a system is its potential problem. E.g. we are running 2000 users, and we need to add extra 500: usually no problem. And what if we need a 1000 more? How high can it grow, depends on many factors, and if the hardware becomes the stopper, it needs upgrade, and as all we know, it's usually difficult to upgrade even 5 years old server. So, we need a new one, plus another one for failover.
> > > > > With YottaDB replication, any 'expensive' report generation processes could be offloaded to a replicated database
> > > > This approach looks advantageous. We have an initial version and plan to improve it to achieve transparent report start on report server and returning the results to database server.
> > > >
> > > > Alexey
> > > I'm new to the MSM area, I see that people suggest many things, however, I don't have the knowledge to adopt these suggestions.
> > > Does YottaDB work with routines, globals and windows in the same way as MSM? Here at the institution we have clients working with windows and clients working directly on the terminal.
> > > Is it possible to migrate from MSM to IRIS? Does it work with windows too? I'm confused and lost..
> > Simple answers this time:
> >
> > Routines - yes - the same with minor adjustments due to non-standard extensions that might have been used (Z* & $Z* commands/functions)
> > Globals - yes - the same
> > Windows - no - these were entirely an MSM 'thing', and no equivalent in any other M system exists that I'm aware of (including IRIS). Multiple options to migrate to, but would be the biggest development effort to migrate to any M except MSM
> >
> > Mark
> Does the cache itself which is the evolution of MSM not have the window system?

Not that I'm aware of. Caché 'inherited' the least from MSM. In fact, I don't know of a single feature in Caché that came from MSM, but someone more familiar with MSM might have better information. Most of the inheritance was from Datatree (DCP which became ECP, namespaces), and Intersystems original mSQL (.INT, .OBJ, .INC, compiler, SQL mapping which morphed into part of the basis for Caché Objects).

On Monday, May 23, 2022 at 1:33:18 PM UTC-4, ti.h...@gmail.com wrote:
> Em segunda-feira, 23 de maio de 2022 às 11:45:42 UTC-3, OldMster escreveu:
> > On Monday, May 23, 2022 at 8:33:34 AM UTC-4, ti.h...@gmail.com wrote:
> > > Em segunda-feira, 23 de maio de 2022 às 06:21:32 UTC-3, Alex Maslov escreveu:
> > > > On Sunday, May 22, 2022 at 8:35:16 PM UTC+3, OldMster wrote:
> > > > > Using YottaDB as the database server and REST interfaces to the browser, modern hardware should easily handle thousands of browser clients.
> > > > Agreed, we have deployed sites with thousands thin or browser clients running a single server. Scaling such a system is its potential problem. E.g. we are running 2000 users, and we need to add extra 500: usually no problem. And what if we need a 1000 more? How high can it grow, depends on many factors, and if the hardware becomes the stopper, it needs upgrade, and as all we know, it's usually difficult to upgrade even 5 years old server. So, we need a new one, plus another one for failover.
> > > > > With YottaDB replication, any 'expensive' report generation processes could be offloaded to a replicated database
> > > > This approach looks advantageous. We have an initial version and plan to improve it to achieve transparent report start on report server and returning the results to database server.
> > > >
> > > > Alexey
> > > I'm new to the MSM area, I see that people suggest many things, however, I don't have the knowledge to adopt these suggestions.
> > > Does YottaDB work with routines, globals and windows in the same way as MSM? Here at the institution we have clients working with windows and clients working directly on the terminal.
> > > Is it possible to migrate from MSM to IRIS? Does it work with windows too? I'm confused and lost..
> > Simple answers this time:
> >
> > Routines - yes - the same with minor adjustments due to non-standard extensions that might have been used (Z* & $Z* commands/functions)
> > Globals - yes - the same
> > Windows - no - these were entirely an MSM 'thing', and no equivalent in any other M system exists that I'm aware of (including IRIS). Multiple options to migrate to, but would be the biggest development effort to migrate to any M except MSM
> >
> > Mark
> Does the cache itself which is the evolution of MSM not have the window system?

You might find this page hosted by George James Software (Thanks George and company!) useful. I'd forgotten it was an implementation of the M Windowing API (MWAPI). AFAIK it was the only implementation of MWAPI to make it to production.

https://www.georgejames.com/ws

Mark

On Monday, May 23, 2022 at 1:33:18 PM UTC-4, ti.h...@gmail.com wrote:
> Em segunda-feira, 23 de maio de 2022 às 11:45:42 UTC-3, OldMster escreveu:
> > On Monday, May 23, 2022 at 8:33:34 AM UTC-4, ti.h...@gmail.com wrote:
> > > Em segunda-feira, 23 de maio de 2022 às 06:21:32 UTC-3, Alex Maslov escreveu:
> > > > On Sunday, May 22, 2022 at 8:35:16 PM UTC+3, OldMster wrote:
> > > > > Using YottaDB as the database server and REST interfaces to the browser, modern hardware should easily handle thousands of browser clients.
> > > > Agreed, we have deployed sites with thousands thin or browser clients running a single server. Scaling such a system is its potential problem. E.g. we are running 2000 users, and we need to add extra 500: usually no problem. And what if we need a 1000 more? How high can it grow, depends on many factors, and if the hardware becomes the stopper, it needs upgrade, and as all we know, it's usually difficult to upgrade even 5 years old server. So, we need a new one, plus another one for failover.
> > > > > With YottaDB replication, any 'expensive' report generation processes could be offloaded to a replicated database
> > > > This approach looks advantageous. We have an initial version and plan to improve it to achieve transparent report start on report server and returning the results to database server.
> > > >
> > > > Alexey
> > > I'm new to the MSM area, I see that people suggest many things, however, I don't have the knowledge to adopt these suggestions.
> > > Does YottaDB work with routines, globals and windows in the same way as MSM? Here at the institution we have clients working with windows and clients working directly on the terminal.
> > > Is it possible to migrate from MSM to IRIS? Does it work with windows too? I'm confused and lost..
> > Simple answers this time:
> >
> > Routines - yes - the same with minor adjustments due to non-standard extensions that might have been used (Z* & $Z* commands/functions)
> > Globals - yes - the same
> > Windows - no - these were entirely an MSM 'thing', and no equivalent in any other M system exists that I'm aware of (including IRIS). Multiple options to migrate to, but would be the biggest development effort to migrate to any M except MSM
> >
> > Mark
> Does the cache itself which is the evolution of MSM not have the window system?

Ack! That caused another old brain cell to wake up! Ouch!
I believe John Murray who is now with George James Software was the main developer of MSM Workstation. It was good stuff, but it didn't do well enough in the marketplace to get the funding it needed to be maintained.

Em segunda-feira, 23 de maio de 2022 às 17:34:05 UTC-3, OldMster escreveu:
> On Monday, May 23, 2022 at 1:33:18 PM UTC-4, ti.h...@gmail.com wrote:
> > Em segunda-feira, 23 de maio de 2022 às 11:45:42 UTC-3, OldMster escreveu:
> > > On Monday, May 23, 2022 at 8:33:34 AM UTC-4, ti.h...@gmail.com wrote:
> > > > Em segunda-feira, 23 de maio de 2022 às 06:21:32 UTC-3, Alex Maslov escreveu:
> > > > > On Sunday, May 22, 2022 at 8:35:16 PM UTC+3, OldMster wrote:
> > > > > > Using YottaDB as the database server and REST interfaces to the browser, modern hardware should easily handle thousands of browser clients..
> > > > > Agreed, we have deployed sites with thousands thin or browser clients running a single server. Scaling such a system is its potential problem. E.g. we are running 2000 users, and we need to add extra 500: usually no problem. And what if we need a 1000 more? How high can it grow, depends on many factors, and if the hardware becomes the stopper, it needs upgrade, and as all we know, it's usually difficult to upgrade even 5 years old server. So, we need a new one, plus another one for failover.
> > > > > > With YottaDB replication, any 'expensive' report generation processes could be offloaded to a replicated database
> > > > > This approach looks advantageous. We have an initial version and plan to improve it to achieve transparent report start on report server and returning the results to database server.
> > > > >
> > > > > Alexey
> > > > I'm new to the MSM area, I see that people suggest many things, however, I don't have the knowledge to adopt these suggestions.
> > > > Does YottaDB work with routines, globals and windows in the same way as MSM? Here at the institution we have clients working with windows and clients working directly on the terminal.
> > > > Is it possible to migrate from MSM to IRIS? Does it work with windows too? I'm confused and lost..
> > > Simple answers this time:
> > >
> > > Routines - yes - the same with minor adjustments due to non-standard extensions that might have been used (Z* & $Z* commands/functions)
> > > Globals - yes - the same
> > > Windows - no - these were entirely an MSM 'thing', and no equivalent in any other M system exists that I'm aware of (including IRIS). Multiple options to migrate to, but would be the biggest development effort to migrate to any M except MSM
> > >
> > > Mark
> > Does the cache itself which is the evolution of MSM not have the window system?
> Ack! That caused another old brain cell to wake up! Ouch!
> I believe John Murray who is now with George James Software was the main developer of MSM Workstation. It was good stuff, but it didn't do well enough in the marketplace to get the funding it needed to be maintained.

Hello, follow msmlog logs when the crash problem occurs

[Jun-01-22 10:03:41] And mumsm ended (proc=#20316374, status=90009)
..................... And ...abnormal termination, signal # = 9
[Jun-01-22 10:03:41] very ended (proc=#14221630, status=0)
[Jun-01-22 10:03:41] very ended (proc=#8257564, status=0)
[Jun-01-22 10:03:41] very ended (proc=#64749588, status=0)
[Jun-01-22 10:03:41] very ended (proc=#44957844, status=0)
[Jun-01-22 10:03:41] very ended (proc=#64684234, status=0)
[Jun-01-22 10:03:41] very ended (proc=#42401856, status=0)
[Jun-01-22 10:03:41] very ended (proc=#65405012, status=0)
[Jun-01-22 10:03:41] very ended (proc=#39125020, status=0)
..................... And ...abnormal termination, signal # = 9
[Jun-01-22 10:03:44] And muserver ended (proc=#61014236, status=90009)
..................... And ...abnormal termination, signal # = 9
[Jun-01-22 10:03:44] And muserver ended (proc=#32571450, status=90009)
..................... And ...abnormal termination, signal # = 9
[Jun-01-22 10:03:44] And muserver ended (proc=#27132320, status=90009)
..................... And ...abnormal termination, signal # = 9
[Jun-01-22 10:03:44] And muserver ended (proc=#33685614, status=90009)
..................... And ...abnormal termination, signal # = 9
[Jun-01-22 10:03:44] And muserver ended (proc=#23789816, status=90009)
..................... And ...abnormal termination, signal # = 9
[Jun-01-22 10:03:44] And muserver ended (proc=#4194584, status=90009)
..................... And ...abnormal termination, signal # = 9