×
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.
On Mon, Oct 7, 2019 at 10:21 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
But that isn't what the article talks to.
True, the article is about migrating applications off IBM i and its native
language environment. There is no mention of anyone providing IBM i on
Power virtual machine environments, except perhaps that ambiguous reference
to "a very similar environment as the AS/400".
My initial thought was that Microsoft doesn't have an environment that is
similar to IBM i, where applications run in the same address space as the
DBMS, and share memory with the DBMS. Microsoft .Net is a virtual machine
and language environment similar to a JVM that runs in processes (Jobs)
that use inter-process communication to talk to a DBMS, which for stability
and scalability reasons would be running on separate server hardware. Those
types of processes are truly "monoliths", often consuming hundreds of
megabytes of RAM, compared to native IBM i jobs that require perhaps 8-15
megabytes of RAM. IBM i supports thousands or tens of thousands of these
lightweight Jobs, whereas Windows keels over if you try to run very many
.Net instances.
midrange.com
