AFAIK the InterSystems ObjectScript extension for VS Code doesn't yet implement a convenient way of overriding an inherited method or property. I suggest you use VS Code's 'Report Issue' option from the Help menu to file a Feature Request on the extension. That dialog is a convenient way to route your request to the correct repo.

The ComplexDelete classmethod uses the FileSet query:

ClassMethod ComplexDelete(filename As %String, Output return As %Integer) As %Integer
    Set resultset=##class(%ResultSet).%New("%File:FileSet"),return=0
    Do resultset.Execute(..GetDirectory(filename),..GetFilename(filename))
    Set exit=1
    For {
        Set file=resultset.Data("Name")
        Set r=$$$FileDeleteRet(file) If r,exit Set exit=0,return=r
    Quit exit

The problem is, that query treats ";" as a delimiter separating multiple search patterns.

You could replicate the method but specify another delimiter (e.g. comma) when you Execute the query to get the resultset (untested code):

Do resultset.Execute(..GetDirectory(filename),..GetFilename(filename),,,",")

Maybe someday ISC will enhance ComplexDelete to take an optional delimiter argument.

My guess is this is on Windows, and the Windows service that HealthShare runs as is configured to Log On As a specific Windows account. Check those credentials. Perhaps the password has been changed, or the account has expired, or been disabled. Look in the Windows event logs (probably the Application one). Another source of info is the cconsole.log file in the mgr subfolder of wherever you installed HealthShare.

Your problem doesn't seem likely to be specifically related to Cache Studio.

Answering my own question. It looks like /multicompile=0 does the trick.

The rules about indirection in ObjectScript can be a bit tricky to comprehend. Your last line is syntactically invalid.

Use this instead:

S @("C="_B)

I'm seeing extra whitespace characters at unexpected places in the code fragments you posted. For example between  $ and fromJSON(data)

What is your $ZVERSION value? The $-style methods got introduced at one point, then removed in a later version.

I think your user Laura_Test_DEV needs to be granted a SQL permission to perform an EXECUTE on the relevant SQL procedure in whatever namespace you need:

You might have been able to monitor progress by running the JOBEXAM utility from another session connected to the %SYS namespace.