http://<server>:<port>/csp/......
refers to the private webserver installed and used in past releases

_SYSTEM is just another user name with role %ALL
any other account with the same role can do it as well.
Tying some code to a Username  ignoring the power of roles is an elementary design error. 

Hi @Otto Medin !
HTTP is basically US ASCII 7bit with some "handcrafted" extensions
- somehow "UTF 7.6" 🤪 focussing on octets
it works for äöü  but NOT for €  (x20AC)  >>> in URL  %u20AC

for details: https://softwareengineering.stackexchange.com/questions/304419/what-encoding-are-the-http-status-and-header-lines

my hint: Try to avoid it in HTTP headers and stick with 7bit ASCII to be on the save side
browsers are less risk for problems but old applications are

YES, concurrency applies to persistent objects once the are sved the first time
this means: it doesn't apply when the object is NEW and has no ID yet.

in XML the construct with ![CDATA[  gets used if the string contains any
character that may cause conflicts in XML parsing:
In your case it is the & (Ampersand)  that triggers the different use.

THIS causes the ![CDATA[ in a string field!
.

Start reading the documentation:
Running the Terminal Application from the Command Line

once you know what namespace you are looking at you may list available schemata by

SELECT * FROM INFORMATION_SCHEMA.SCHEMATA

which returns 750  rows for namespace HSCUSTOM

 

And here is the full documentation
Processing Errors at the Terminal Prompt

2d  indicates that you are 2 stack levels down from Command prompt last entered by do
enter QUIT to return  to top  

do ^%STACK may display your way  down to your actual point 

x "for x="_customString_" do something(x)"

the date format is most suspicious to me.
in SMP you can set it to
- Logical Mode  >>>  66453  like +$horolog
- Display Mode  >>> 2024/03/25    as you did. It is depending on default display settings.
- ODBC Mode    >>>  2024-03-25

more drastic: KILL  does an ObjectScript Kill on all related Globals. Quick and Fast
DELETE loops on subscripts and mimics a SQL DELETE row by row and has definitely more overhead
 

LOAD DATA requires activation of JavaGateway.

>> active in docker community version by default

your CASE statement  is wrong in multiple ways:
and doesn't work in ENSEMBLE /Caché either

1. double quotes " mark column names, strings require single quotes '
2. !=""  is an Objectscript construct
3. you have to write NOT IS NULL instead 

select CASE WHEN StarterKitName NOT IS NULL THEN ....

See also example in ENS/Caché  docu :
https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=RSQL_case 

As you now explained what you really are looking for:   $System.SQL.Schema.SetDefault()

From Docu:

classmethod SetDefault(schema As %Library.String = "", ByRef oldval As %Library.String, Namespace As %Library.Boolean = 0) as %Library.Status

Sets the default schema used by SQL.
This configuration setting provides the ability to define a default schema name other than SQLUser, the default. When an unqualified table name is encountered in an SQL statement (and there is no #import statement specified), the default schema will be used. This setting has nothing to do with the mappings between SQL schema names and the class package name, it only specifies the default schema. Parameter:

schema

String containing the default SQL schema name. If schema is "" or not defined, the default schema will be set to SQLUser.

oldval

Passed By Reference. Contains the previous value of the setting.

Namespace

Boolean 1/0 flag. If TRUE, set the default schema for the current namespace only. The default for Namespace is FALSE

Returns:

Status Code

NOTES:

- You must have the "USE" permission on the %Admin Manage Resource in order to change this configuration setting.

- Changing this configuration setting will affect all processes immediately.

Hi @Michael Davidovich !
you hit exactly what I addressed in in my recent article
  The bewitched line terminator

As long as you get (text-) files from your own OS the default is OK
BUT: if you work cross OS platforms - rather likely for CSP pages -
the approach of  %CSP.BinaryStream is the best for import.

For output stream you have to decide based on the expected target OS.

My personal trigger to that subject was file transfer between
WIN as Docker host and a Container (Ubuntu) causing a lot of  confusion until detected.
 

System Utility %ETN.int takes a snapshot with all actual variables somehow similar to WRITE command
Description:  Using %ETN
It may give you some feeling how to analyze a running process.
ATTENTION: 
reading requires some experience in ObjectScript
you might get lost

you describe 2 different record layouts that reside within the same storage 
#1 - just a name
#2 - a name + a "transferred" property

depending on the situation you use either layout #1  or layout #2 for INSERT
reading might be OK for layout #2 in both cases.

Caché once had a somewhat similar sample with Person
and Employee extending Person. 
available here: https://docs.intersystems.com/iris20241/csp/docbook/Doc.View.cls?KEY=ASAMPLES
this Repo:
https://github.com/intersystems/Samples-Data/tree/master/cls/Sample

eventually better to check for longer lists

USER>s x=$lfs("Purple,Black,Yellow,Pink")
USER>s y=$lfs("Red,Green,Orange,Yellow")
USER>f z="y","x" f i=1:1:$ll(@z) i $i(dif($li(@z,i)))
 
USER>zw dif
dif("Black")=1
dif("Green")=1
dif("Orange")=1
dif("Pink")=1
dif("Purple")=1
dif("Red")=1
dif("Yellow")=2
 

looping with $o() over dif() allows programmatic check