It is interesting that you are asking this as we have tried, for well over a year, via various mediums, at various levels within Intersystems, to get an answer as to the future of IDE's given that previous announcements and responses from WRC state that both Atelier and Studio are end-of-life.

We have never received a response even after Evgeny pinged such a request to John fried and others after some posts.

Your statements seem to indicate that Studio is not end-of-life so it would be nice to have some clarification as even WRC are saying non-critical fixes or changes will not be done.  You also indicate work being done on VSCode integration, again any details would be appreciated.

The reason for wanting to know is that is difficult to commit to a particular toolset or plan changes to DevOps etc... if the future of the tools to be used is unknown, the actual answer and whether it is an individuals or companies preference is immaterial, it is simply that an answer is required but everyone has been reluctant for a long time now to commit to anything.

Coming back to your questions, we use Studio with our own version control based on StudioHooks and some use of Serenji for debugging.

We have tried Atelier but noone liked using it and we have worked in VSCode via Dmitry's plugin and have also tried the Serenji plugin both of which were generally a good experience but migration would require changes to development processes and version control. 

We are likely to move to a GIT based Version control and whether this is intergrated with Studio or VSCode will likely depend on Intersystems commitment to the IDE though I suspect there would be a preference to stick with Studio as it is familiar and has integration to Cube etc... though as we continue to do more Web based development in VSCode this may change.

You can also do allot of this using %CHARWIN rather than native escape codes

https://cedocs.intersystems.com/latest/csp/docbook/pdfs/pdfs/GCHW.pdf
 

As you are talking about locks and transactions, and as others have noted, you can nest transactions it might be worth warning people about locks inside transactions and the fact that the unlock will not take place until the tcommit.

These can cause issues, especially where this is a method using transactions and locks which calls another that does the same.

Does the instance on the test server run with the same credentials as the production server, it could be permissions, also is the test server the same OS as some server versions are more strict if this is a shared printer on another machine.

As this is a printer I assume X is "|PRN|printername_or_UNC" ?

If you can't see it open already then a failure to open can also indicate a problem with the printer.

We commonly get sites log an issue and it turns out they have changed UNC path/permissions, or the printer is offline/showing an error, and it is this which is the issue.

Could you tell us the OS and open command you are using, it might help with suggestions.

Open devices for a process can be seen in the Processes section of the portal.  The initial process list shows the principal or current device and in the individual process page it shows all open devices, this can also be found using the %SYS.ProcessQuery OpenDevices
 method so you could write code that goes through all processes checking.

What these show may depend on how you open the device in the first place.

I know Jeff and Raj are busy people but there never was a response.

Intersystems simply need to commit to an answer as at this point the actual answer isn't really important anymore, just getting an answer so commitments to any change can be made.

That looks better than the WRC supplied code when I fist noticed the binary rather than hex values returned.

set text = "message digest"
  set md5hash = $system.Encryption.MD5Hash(text)
  set md5HashHex = ""
  for i=1:1:$Length(md5hash) {
   set md5HashHex = md5HashHex _ $Zhex($Ascii($Extract(md5hash,i)))
  }
  write md5HashHex, !

I am in the same position as you, only selectively using full commands or function names, being too much in the habit of MUMPs abbrevations.  Like you though I tend to extend when iterating or using something less usual in the code, I have also found curly braces to be much better for readability than the old block structure.

I also agree that I find it faster to read and write abbrevated code for things like sets and do's and especially for functions such as $p and $g.  Hopefully I can get into the habit of less abreviation as I do notice the new programmers finding this harder.

Probably the biggest habit I have broken is also shown in the bad examples given and shows how long I have been using MUMPS, yes it's entering everything in UPPERCASE.  I finally use camel case and also more meaningful/longer routine and variable names.

Thanks for adding that, in the case of a preview it might be worth adding this to the "Notes" section to save cross referencing with release notifications or the usual downloads page.

The answers given should help with the $ZU's you have listed but if you have further queries or new entries then the Cache 2008 documentation available at the link below should help.

https://cedocs.intersystems.com/ens20082/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_C24792

Thanks for the clarification.

The fact that the current download is slightly different from the norm due to a Global Summit launch does highlight the need for a brief explanation of the version you are downloading though.

I second having the conatiners available in the same place.

Also could you show the version number available before downloading and are these production releases or previews?

We had a similar issue at a site and it turned out the routine index was corrupt, recompiling all routines solved this.

Just a quick note.

I found that when creating a new database it was best to initially use SYS.Database so you can specifiy max size etc..

s db=##class(SYS.Database).%New()
s db.Directory=directory
s db.Size=initialSize
s db.MaxSize=maxSize
s db.GlobalJournalState=3
s Status=db.%Save()

Then finalise with Config.Database

s Properties("Directory")=directory
s Status=##Class(Config.Databases).Create(name,.Properties)
s Obj=##Class(Config.Databases).Open(name)
s Obj.MountRequired=1
s Status=Obj.%Save()

This might not be the best way to do it, I'm open to improvements.

Hello Dmitry,

I have used the extension and am very impressed but obviously any change in toolset has to be agreed accross the business and will require changes to the development and version control process, hence a reluctance until we know what Intersystems have planned.

Apologies if I have missed a feature post but does the extension replicate the Studio Add-Ins such as the SOAP Wizard as these are very useful to us.

Regards

David

Hello Evgeny,

Thanks for the response, of course I am aware of the various plugins hence my question of relying on 3rd party tools.

That old post does not really answer the question on what Intersystems future plans for development tools are, it just confirms effective end of life for the current ones.   Also, only fixing critical issues means reported problems will generally not be fixed anymore as they are pretty stable, something I have already experienced.

I don't have a particular problem with moving to VSCode supported by 3rd parties but some confirmation of this from Intersystems so developers can plan to move in that direction would be appreciated but noone seeems to want to commit to any answers.  It also starts the question of how will Intersystems provide the ability for these 3rd party tools to replicate and extend the functionality available already, again there are no answers.

Regards

David