RE: Running .Net Natively on IBMi

I'm not really smart enough to know if your definition of native is better than mine, but with all your technical points I'll give you the edge.

I just know that Python, PHP, Node and many other things PASE run smokin fast on the box and are pretty easy to integrate to traditional RPG and CL workloads as needed.

And I like to integrate so it keeps things fun.

Oh and back to the native .Net running in PASE. If it happens awesome, but if not I'll use what's native to IBMi when needed and .Net for everything else.

You might say I'm a universal connector...................

Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------

message: 4
date: Fri, 12 Jan 2018 16:20:49 -0700
from: Nathan Andelin <nandelin@xxxxxxxxx>
subject: Re: Running .Net Natively on IBMi

On Fri, Jan 12, 2018 at 3:27 PM, Justin Taylor <JUSTIN@xxxxxxxxxxxxx> wrote:

IMO, if "x" runs as an active job on IBMi, it's native.

My definition of "native" has additional qualifications. I'll try to explain why. If you and others do not agree with my perspective, or my rationale, then that unfortunately leaves us without a common understanding.

PASE is quite literally a subset of AIX. PASE applications are quite literally AIX applications:

- PASE doesn't run on top of the technology independent machine interface.
It rather uses a "syscall" interface.
- PASE doesn't utilize single level store.
- PASE objects are little more (if anything) than stream files.
- PASE is an operating environment that is essentially separate from IBM i.
- PASE runs in Power PC mode rather than Amazon 64-bit mode.
- PASE uses a memory address space that is separate from the one used by IBM i.
- PASE doesn't run ILE or OPM language programs.
- PASE does run several language environments that don't run on IBM i.

In regard to "active jobs", the ones that bind to PASE typically load a full-fledged language environment such as Java, Node.js, PHP, Python, Perl, Ruby. Those Jobs typically have CPU and Memory requirements that amount to something like 50 times that of an ILE program.

The IBM i virtual machine may run tens of thousands of Jobs that activate ILE programs, and manage those workloads without breaking a sweat. But you can destabilize a machine by launching and running more than a few hundred PASE jobs.

The way that IBM i manages workloads is a critical distinction from the way that PASE manages workloads, and also how multi-threaded language environments like Java manage threads.

To me it doesn't make sense to look at a Job that binds to PASE, and not make a mental note of the distinctions from ones that run in the "native"
virtual machine.