$ZTRAP is pretty much the same idea as ONERROR that you find in
BASIC, VB, VBA, JavaScript  and some other old languages.  
a left over from M
 

in docker-compose.yml

change

command: --key /dur/key/iris.key

to

command: --key /dur/key/iris.key -b "sleep 2000" 

so the container starts but IRIS is not started
2000 is just some hang for your investigation (2000 sec)

in a 2nd session run

docker-compose exec iris bash

and start IRIS manually to see all details of what might be wrong
 

I share your suspicion on reserved Verbs.

You may try 

m.Name as "myName"

Or even

m.Name as "Name"

Just a guess from the  hip

first you need to install a valid DSN: Defining an ODBC Data Source on Windows
for PS you may take the same approach as described here

Wrap your SELECT in an Outer  SELECT LIST(...inner select ...)
try:

SELECT LIST(DIAGNOSE) FROM (
 SELECT MRDIA_.....->MRCID....
 FROM ......
 WHERE .....
 ORDER BY ......
)

What you describe is indeed named Global:
and the syntax could be  ^ehr.IP to follow your question.
It is visible over the whole namespace.
If you use ^%ehr.IP the % makes it available over all namespaces of your installation.

Set ^%ehr.IP="whatever you need" is creating it   
 

A quite interesting feature.
Did you take a look on how backup management is affected / involved by this design ? 
I just fail to imagine how to keep all this in synch.
e.g. if spread over several drives:
Are they backed up in total or in volume junks ?

Principal limit: HTML just knows about JavaScript
JavaScript is executing an XHTML call to your Ensemble carrying along all required credentials.
e.g. sessionid,  encryption, cookies, ....
In your namespace SAMPLES zipcode.cls ia a detailed example,
your call looks like this;

#server(..validateZipCode(zipcode))#

But the generated code is this:

("cspHttpServerMethod")_"('"_(..Encrypt($listbuild($classname()_".validateZipCode"))_$select(%session.UseSessionCookie'=2:"&CSPCHD="_%session.CSPSessionCookie,1:""))_"',zipcode)",!

HTML has no idea about all this
 

OOUHH. Weblink had end of life more than 20 years ago
It was the unloved predecessor of CSP. 

Being happy married for 55 years I find the subject of such a calculation just disgusting.

I just would refuse to marry a partner calculating impact of the wedding costs on his retirement.
I'd rather prefer one that attempts to raise his income by working more and harder
and not thinks of forecasting retirement before the wedding.

it's best described in docs

• %DeleteExtent()

classmethod %DeleteExtent(concurrency As %Integer = -1, ByRef deletecount, ByRef instancecount, pInitializeExtent As %Integer = 1, Output errorLog As %Status) as %Status

Delete all instances of this class from its extent. On exit instancecount contains the original number of instances while deletecount contains the number of instances actually deleted.

Internally, %DeleteExtent() iterates over the set of instances in the collection and invokes the %Delete() method.
Refer to Object Concurrency Options for more details on the optional concurrency argument.
The option pInitializeExtent argument allows the user to override the default behavior of calling %KillExtent() when all instances are successfully deleted. %KillExtent() is called by default when the extent is empty so that empty globals can be killed. If %KillExtent() is not called then some empty globals can remain as well as the ID counter if it exists. The default value for pInitializeExtent is 1. Unless the caller specifies a false value for pInitializeExtent the globals used by the extent will be killed. If the process' GlobalKillDisabled flag is enabled and not the default of false the process' GlobalKillDisabled flag will be changed temporarily to false to allow the operation to complete without a possible error. In some cases, the globals used by the extent are not used exclusively by the extent. In those cases it is possible that some globals will still be defined even when pInitializeExtent is true. By default this call to %KillExtent() will not delete default stream storage global, but if you pass '2' in pInitializeExtent and if the entire extent was deleted we will call %KillExtent passing the 'killstreams' flag to ask it to remove kill the default storage global.

Returns a %Status value indicating success or failure.

• %KillExtent()

classmethod %KillExtent(pDirect As %Integer = 1, killstreams As %Boolean = 0) as %Status

%KillExtent performs a physical kill of the extent. No constraints are enforced. This method should not be used in place of %DeleteExtent. Only physical storage occupied by this extent will be killed. If this extent is a subextent of another class then no data is killed. Indexes that originate with this extent will be killed. %KillExtent will be called on any subextents and on any child extents (the extent of the type class of a relationship whose cardinality = children is a 'child' extent) of this extent.
This method is not meant for production applications. It is meant to be a development utility to quickly clear extent physical data. Also this will not remove stream data associated with these instances.
If killstreams is true (default is false) it will also kill the default stream storage global.