If the individual segment transformations are common across all ADT DTLs, you could implement your DTLs with subtransforms (these work at the segment level). As long as the gross structure of the messages rarely changes, the maintenance is all done in segment DTLs.

As you suggested, git is likely the culprit. It has an option for handling line-endings; see Configuring Git to handle line endings - GitHub Docs. 

With #2 (at least for me anyway), the issue seems to be related to running iris session when using the Windows version of ssh.exe (called from VS Code, configured in settings under node terminal.integrated.profiles.windows). Home and End work normally at the Linux shell prompt, but when running iris session the effect is that either key produces the same result as pressing the Enter key. The current command is executed and a new IRIS prompt is generated.

It doesn't seem to be a VS Code problem so much as an ISC problem, at least on Windows.

This should work (no looping required):

I'm using the parenthesis syntax with the Matches() function to locate a pattern of any number of punctuation characters (.P) followed by 8 numeric characters (8N) followed by any number of any character (.E).

The parenthesis syntax returns the repeating values in the form "<><><20230512191543><>" where <> represents an empty iteration of the repeating field (and fortunately qualifies as a punctuation character).

And an upgrade, since the foreach action didn't exist in 2017.2 😉

According to a StackOverflow thread I just read, the connection url below is purported to work on Linux and authenticate with the MS JDBC driver:

jdbc:sqlserver://[server]:[port];database=[db];trustServerCertificate=true;integratedSecurity=true;user=[user without domain];password=[pw];authenticationScheme=NTLM;domain=[domain];authentication=NotSpecified

ISCAgent is running on primary, alternate and arbiter? It has to be running on all 3. IRIS Windows installation by default will install ISCAgent but will not enable it for auto-start.

I couldn't even get that class to compile until I set the ENSLIB database to mount R/W. And yes, I was attempting to compile it in a conventional "interoperability-enabled" namespace. That's on I4H 2022.2, fyi.

Does it compile without error on your system?

The error in your previous post seems to indicate that no filename was available for creating or appending. The path shown in the error does not include a filename.

If the outbound operation is configured to use %f as the filename and has the Overwrite checkbox unchecked, the output file will have the same name and all records from the input file.

You mostly likely will have the input service and output operation set for different directories. Relying on the source file name may prove to be problematic if the inbound file has the same name every time it's received.

I assumed there would be a way to accomplish this with a form of OS/Delegated authentication, but I may be wrong. It wouldn't be the first time 

EDIT:​​​​​ Let me amend that. OS authentication works only for users whose OS accounts exist in IRIS, right? So don't create any IRIS users that have matching OS accounts ... With the exception of the account that needs OS authentication.

@Padmaja.Konduru5974's solution works from the IRIS/Caché prompt when in the proper namespace.

If you need to be able to script this from the OS, there will be additional steps required, such as piping command input to iris session <instance> from the OS shell. You will likely need to include a username and password in the piped input, which is generally not a good idea. Enabling OS authentication may be an option, but that's a global setting and not (easily) configurable per-user.

While $$$FormatText() is a great tool, I'd give my left ... uh, leg to have a sprintf() workalike that handles left/right justification, padding, number precision formatting, date element tokens, etc.

I guess we'll just have to make do with Python f-strings ... 

EDIT: Hah, I guess you posted your solution as I was typing this ... and yeah, sort of what I thought it might be 

Are you calling (and testing) this from a DTL? If yes, have you looked through the DTL rules to see if the returned string's variable is being used as an argument to something like $system.Status.GetErrorText()?

Does the same thing happen when you execute it from the IRIS prompt?

Set tStrm=##class(%Stream.GlobalBinary).%New()
Do tStrm.Write("SGVsbG8gV29ybGQh")
Do tStrm.Rewind()
Write ##class(<packagename>).DecodeBase64HL7ToFile(tStrm,"<ancillary>","</path/to/outputfile.ext>")

Replace <packagename>, <ancillary>, and </path/to/outputfile.ext> with values appropriate for what you're testing, of course ...

ImageMagick is likely available for your platform and can be called using $ZF(-100). It has a LOT of image conversion options.

A sample command line for svg to png conversion:

$ convert -background none -density 1000 -resize 1000x myvector.svg myraster.png

Example using $ZF(-100):

Class User.Util.Image [ Abstract ]
{

ClassMethod Convert(pSourceFile As %String, pDestFile As %String, pDensity As %Integer = 1000, pResize As %String = "1000x", pBackground As %String = "none") As %Status
{
    Set OsCmd = "/usr/bin/convert"
    Set OsArgs(1) = "-background"
    Set OsArgs(2) = pBackground  // "none" for transparent and black for formats w/o alpha channel
    Set OsArgs(3) = "-density"
    Set OsArgs(4) = pDensity // set the vector width before resizing for best image quality
    Set OsArgs(5) = "-resize"
    Set OsArgs(6) = pResize // image output width/height (default is width 1000 keeping aspect ratio)
    Set OsArgs(7) = pSourceFile
    Set OsArgs(8) = pDestFile // file type controlled by extension; .png, .jpg, .gif etc.
    Set OsArgs = 8
    Set tRC = $ZF(-100,"",OsCmd,.OsArgs)
    // On Linux, a return code of 0 indicates success
    If '(tRC = 0)
    {
        Return $$$ERROR(5001,"OsCmd "_OsCmd_" Returned Error Code ["_tRC_"]")
    }
    Return $$$OK
}

}

Called like this:

Set tSC = ##class(User.Util.Image).Convert("/path/to/filename.svg", "/path/to/filename.png")