Just as described here

you need to check the already used connections.

and code quality will struggle with it and dislike it

because you use name in write, but you don't set it explicitly

but don't care much about:
it doesn't understand %-variables and global variable scopes
and $$$macros with code inside, and ... and ... and  

to get control over your situation you have 2 key methods:

• $SYSTEM.License.MaxConnections() returns the maximum number of connections a user can make while consuming one license unit.
• $SYSTEM.License.ConnectionCount() returns the number of connections currently associated with the given UserIdentifier. The range of return values is normally 0 through MAXCONNECTIONS. If the value exceeds MAXCONNECTIONS then more than the allowable number of concurrent connections were attempted for a given ID and the system has transitioned to a mode of one connection per license for this UserIdentifier.

So you have to check if your user has exhausted its available connections and block him.
It's anyhow quite interesting how these users are able to trigger so many connections.

I share your suggestion!

When I started with Docker I was highly skeptical after many years with VMware starting before their first release.
It was a hard exercise and I took quite a while digging through docs and helps.
My main problem was that everything was so generic and not at all specific to IRIS (or Caché).

Meanwhile, it became so common to me that I stopped running reviews on packages without docker.
Docker allowed me to have a "clean desk" after testing.
In addition. I saw through this activity so many valid variations that
I doubt to decide how to start and where.
On the other hand, I see in OEX ~450 tested and working examples (a dozen PR still pending) 
Following these examples and trying to understand what will be achieved
could be good food for training designers. 
 

nothing prevents you to load this script at runtime from server.

<script src="myscripts.js"></script> 
from w3schools.com https://www.w3schools.com/tags/att_script_src.asp

So you are outside your Caché
 

I do the same exercise in my package GlobalToJSON-ePython-pure

it should be basically sufficient to replace the JSON packing + writing   by print(...)
see >>> def node(nd,nxt,fil):

in my various examples I took these strategies:

• try to run the Py code in PY shell in a REAL terminal or docker command line console
• error messages directly from the shell are much more useful  
• insert temporary print(...) statements at suspicious points
• what I see by COS <THROW>  is often more obfuscation than a hint  

to my experience, your 'KeyError' indicates that you try to get a value
from a non-existing global or subscript. in COS it would be <UNDEF>

NIce you share a picture of a PDP11  ! 
a few of my heroes:

• Prof. Heinz Zemanek  one of my teachers at university
• Terry Ragon
• Neil Pappalardo

---

I know also some handicapped developers.
BUT: I find it highly insensitive and inadequate to drop their names in this forum

• Vikings
• Dr.Shivago
• Metropolis (F.Lang ,1925/26)
• Gone with the Wind (1939)
• Convoy

• mountain climbing
• long distance walking
• practicing foreign languages
• studying astrophysics, cosmology, nucelar physics,  anthropology, geology

Any sport that requires mental concentration. eg. mountain climbing, 
And I mean REAL climbing, not just moving your body somehow across nature.  

• first I check the logical qualification - e.g. playing chess
• next check the skills in estimating results of simple mathematical calculations  or simple mechanical ckecks or puzzle strategies (without paper and pencil) 
• next, I observe the operation of their mobile phone and ask for explanations
• the very last might be t take a look into suggestions like yours

With 2 very successful sons in software, internet, and project engineering (49yrs. + 36yrs.)
I have a valid benchmark for my strategy.

A real software developer doesn't care about the hardware or operating system.
Specific hardware is a subject for gamers.

I enjoy to solve what was declared to be IMPOSSIBLE before.
I dislike it if it turns out that issue was just a fake and nobody cares about my creations. 

Not of importance but interesting observation anyhow.
$ZPI differs in the last 3 digits .
$ZPI is right according to Wiki 

write "3.141592653589793116  PY",!,$ZPI_"  IRIS",!
3.141592653589793116  PY
3.141592653589793238  IRIS

 --progress plain

This is essential information.
Without it the building log just runs though with no chance for a rollback
and iris.script allows a lot of temporary debugging info.