Hello Malcolm,

You should consider using a VIP (Virtual IP) to let users connect to the current primary regardless of a mirror switch.

Usually, the arbiter machine, does not require IRIS to be installed, only the ISCAgent service, but if you have IRIS there with a license server than you lose the HA for licensing (in case arbiter machine is down).

1. Usually this indicates that the IRIS is sending an incomplete certificate chain
2. The fact that you can access IRIS SMP has nothing to do with the outgoing HTTPS request, which I assume you do with %Net.HttpRequest and using the SSL property that match the SSL config
3. I recommend accessing the  https://myserver.com/api/gap/... from a browser and to check the certificate chain. Usually you will see 3 certificates (root CA, intermediate authority, the certificate itself) - you should put all those certificates (one after the other) in the PEM file that is configured in the SSL config in IRIS. Depending on the CA (which might be public, or company self-generated) you need to ask your sys admin 

in retrieval code use: Set {*} = ... 

instead of having each property stored with its name as a subscript, (e.g. ^Student(1,"Name") = "Alice" / ^Student(1,"Age") = 29 etc.)
its much better to use the same format the class compiler is storing data on the D global:
^Student(1)=$LB("Alice",29 ... )

when having globals with millions (or billions) of records it will have a huge impact on performance and storage footprint.

on any class that extends  Ens.Request or Ens.Response you may use:

Parameter COMPRESS = 2;
Property JSON As %Stream.GblChrCompress;
On large messages (or in a system with billions of messages per day) the save on storge is huge!
- Visual trace working fine
- You may search within the compressed property (but it will take time)
- Property is visible in SQL queries against Ens.MessageHeader / Ens.MessageBody 
- The "out of the box" purge working fine

try to open developer tools (shift-ctrl-P) then search for "developer tools" - check in console if there are any errors 

try to change:
<Route Url="/{id:[0-9]+}" Method="GET" Call="NewsGetItem"/>

See those articles:
Accessing the IRIS Terminal: A Comprehensive Guide for Visual Studio Code
How to run ObjectScript commands in the VS Code integrated terminal |
and documentation:
Run and Debug Your ObjectScript Code | Use Visual Studio Code as a Development Environment for InterSystems Applications | InterSystems Components and Tools
 

look at Ens_Config.Item there is a property called "Enabled"

I would consider, replacing the lock + and lock - with setting/killing a (temporary) global, which can be mapped to IRISTEMP for better performance, and avoid journaling. It might be easy to implement such in parallel to the current lock mechanism (add those while keep the old in place) then migrate the management page in the application to loop on this global instead of the entries in lock table. The new approach can also have the timestamp for the lock and then have a function that will auto-retain locks (kill) based on a time interval.

The is a core process called GARCOL which is used to handle large global kills.
Securing Caché, Ensemble, And Operating System Resources | Caché & Ensemble 2018.1.0-2018.1.3
 

for sure direct global access, especially looping on indexes is faster than SQL. It seems that the index global you used: ^PatientD("Date",FromDate)) should be: ^PatientI("Date",FromDate)) 

Using queue manager (for each "FromDate") will do this in parallel which will speed things much more!

I would day that the bot answer is not relevant to what you asked.

there is no directive to do looping in macro definitions, however, you could look at a directive called #execute where you should be able to execute any valid COS code, but there are some limitations:
#execute | ObjectScript Reference | InterSystems IRIS Data Platform 2025.2
 

HTTP 401 means "Unauthorized" check that the web application /terminal has the correct credentials and correct authentication methods (password, LDAP etc.)
(the /terminalsocket should be always unauthenticated, its the default)
to help you resolve this, you may use auditing, to see if there is a "login failure" when you try to access.

Norman,
If terminal is ok for you, but studio isn't, maybe you should try the VSCODE Lite terminal.

I'm using: IRIS for Windows (x86-64) 2024.1.4 (Build 516_1U) Sat May 31 2025 13:15:40 EDT
I get the same in Terminal (Telnet) and also in VS-Code Lite terminal:
MSCEME>write $ascii("♥") 
9829