New post
AllAccepted answers
Ben Spead · Mar 3, 2022

@Vitaliy.Serdtsev  - you make a fair point about downloading the full Eval kit just for a few pieces of it ... unfortunately that is the only distribution mechanism that I know of currently available for non-supported customers.

Thank you for all the time you've spent over the years helping to find ways to make Caché more robust!!  It sounds like you've been able to identify quite a few areas of improvement.  There was significant effort put into streamlining things and solving known issues in the rebirth of Caché as InterSystems IRIS.  You might find it interesting to download the Community Edition (IRIS version of the SU kit but much more powerful with fewer restrictions) and see if the bugs you reported are still present there or not.  What do you think about that approach?

I got clarification that we still create an SU version of Caché which is available in the WRC because some of our large partners/APs rely on it for people to learn on (which makes sense).  Obviously we won't want new prospects playing with it, which is why it is no longer publicly available and instead we provide the InterSystems IRIS Community Edition.

Ben Spead · Mar 3, 2022

@Vitaliy.Serdtsev - you could download the Community Edition of InterSystems IRIS from evaluation.InterSystems.com and just install Studio from that if you wish.  Also, is there a reason you want the SingleUser version of Caché rather than the InterSystems IRIS Community Edition (which is freely available to everyone)?  

Ben Spead · Feb 28, 2022

@prashanth ponugoti - a couple of things to look at:

1) When you open the first link in /csp/healthshare does it open for you after authenticating?

2) Is your /csp/test web application definition set to work in the same namespace as /csp/healthshare?

3) Is a copy of your person.csp file moved to the web application root that you defined for /csp/test?

Hope that helps get you started on finding a solution.

Ben Spead · Feb 23, 2022

@Evgeny Shvarov  - you cannot use "!<cmd line>" from the Output window of Studio.  It is often very helpful to run a command from the context of a serverside Caché/InterSystems IRIS process which you can do via the Output Window with the above command, but not with "!":

!whoami
whoami - Error <SYNTAX>

Kill stream Set sc = ##class(%Studio.SourceControl.ISC).RunCmd("whoami",.stream,,1) w ! do stream.OutputToDevice() If 'sc { Write $System.Status.GetErrorText(sc) }
CMD: whoami
irisusr

Again, this is particularly useful when running server-side source control commands (if you need to debug or augment hooks)

Ben Spead · Feb 22, 2022

This is great, thank you Evgeny!!  Here is another one that I use, often from the Output window in Studio in order to execute an OS-level command (I most frequently use this for p4 commands to interact with my Perforce server from my IRIS server).  IIRC, original credit goes to @Timothy Leavitt 

Kill stream Set sc = ##class(%Studio.SourceControl.ISC).RunCmd("<insert OS Command here>",.stream,,1) w ! do stream.OutputToDevice() If 'sc {​​​​​ Write $System.Status.GetErrorText(sc) }​​​​​