Look into using Interoperability. The classes EnsLib.REST.Operation and EnsLib.HTTP.GenericOperation should do what you are looking for depending on if you are calling a REST service or it is plain HTTP

We have several business operations that use EnsLib.REST.Operation, each with pool sizes of between 2 and 60. Providing the http response indicates the connection can be maintained, they will keep the connection open.

A little longer, but far more flexible, I've always liked

write $translate("DdMmCcYy", "CcYy-Mm-Dd",  $zdate($now(), 3))

Just provide the format you want in the first argument.

However, it would be even more helpful to be able to override the default error display. This would need some changes to the dispatch and implementation class generators.

The dispatch class generator would need to call the specific implementation class to format the error, instead of the implementation superclass.

The implementation class generator also (really) needs to be able to accept an override for the implementation superclass via the swagger document (as there is for the dispatch class).

Then the try/catch would not be needed at all, and the default error handling would do everything needed.

This is as of Iris 2022.1. I'm not sure if this has been added in later versions.

Assuming you are using generated disp and impl classes from a swagger document, the simplest option you have at the moment is to edit the code in the impl class:

• Use try/catch within your implementation method
• the catch block to set %response.Status = your required status code
• Create a json object with your required payload
• return this object instead of the usual payload object

This will bypass the default error handling of the disp class.

It isn't ideal though.

e.g.

ClassMethod myFunction(arg1 As %Integer) As %Stream.Object
{
    try {
        set ret = {"data": "value" }
        if 1/0 // Force an error
    }
    catch err {
        set ret = ##class(SomeClass).FormatError(err)
        Set %response.Status = 500
    }

    quit ret
}

The global delock means the global will stay locked until the top most transaction completes (tcommit or trollback), this is to protect against another process updating the global (assuming it uses locks) whilst your load is running.

You can effectively achieve the same with your own lock instead of the top level tstart

lock +^TEST 
for I=1:1:N { 
    set ^TEST(I) = $lb("", "123") 
    
} 
hang 5 
lock -^TEST

Depending on your requirements, a timeout and lock failure handling might be needed