As we looked into things further on our side, it appears as though the UNIX 'hostname'.  We were able to resolve the issue in UNIX by doing the following to change the hostname to 'mynewhost':

log in as root
hostname mynewhost
echo mynewhost > /etc/hostname

The 2nd line will change the hostname in the current processes, and the 3rd will make sure that the change will persist during a reboot.  

Hope this is helpful to someone else.

@Colin Brough - all great questions!  I'll provide some thoughts and I am sure others will chime in as well.  One question that I have which may impact the answers is what your current source control approach is?  Are you using serverside source control hooks with Studio or some other approach?

  • Take Atelier off the list and drop it from consideration... it is deprecated new work shouldn't be started with it
  • VSCode is the path forward for InterSystems technologies; it used the Atelier REST APIs and therefore you can use it on Caché 2018.x (originally added in 2016.2 IIRC)
  • You can typically use VSCode alongside Studio, depending on your answer to the above question about your source control approach.  If you are using no source control, or if you are using serverside source control, then Studio and VSCode can both be used against the instance in mixed mode (my team has been doing this for years)
  • I can't speak to what you lose with VSCode but I believe that at this point the answer is either 'very little' or 'nothing' for all intents and purposes
  • I can't speak to Studio Templates (hopefully someone else can weigh in)

This video may also be helpful to you: https://community.intersystems.com/post/video-visual-studio-code-objects... 

Hope this is a good starting point.

It is the actual code as it will be executed, so "Do ##class...."

if you import this class into IRIS you will then be able to run the methods.  Look up the docs for $system.OBJ.Load() .. you will load and compile the class and the. you can call the methods like this:

Do ##class(User.Ready.ConvertCSV).ConvertN()

(I assume you cut out the actual logic of the methods when you pastes it above as what you pasted is incomplete)

@Cryze Zhang - it looks like this was an issue in prior versions as well.  

Did you know you can report this directly to the InterSystems Documentation team?  Click on the blue "Feedback" button on the right side of the screen and it will give you a chance to tell Docs directly what is wrong with the page.  Here is the 2021.1 link you can use for your convenience:
https://docs.intersystems.com/irislatest/csp/documatic/%25CSP.Documatic....

 

Thank you for noticing this and bringing it to our attention!  Please confirm once you have reported the issue and it will get addressed.

You are most welcome!  There is a lot of power there at your disposal ... enjoy the discovery process!