go to post John Murray · Jul 17, 2018 You can create a Studio project interactively from within Studio. There are a few hints in the Studio doc here.Or if you want to create/amend Studio projects programmatically, use the %Studio.Project class.
go to post John Murray · Jul 12, 2018 Not a direct answer to your question, but did you consider using the Size query of the %SYS.GlobalQuery class, as shown by this DC comment from @David Loveluck on another DC post?https://community.intersystems.com/post/database-table-size#comment-12401
go to post John Murray · Jul 11, 2018 Though it now seems that 1.3 is the end of the Atelier road, right?https://community.intersystems.com/post/atelier-and-studio
go to post John Murray · Jul 11, 2018 There's a table at http://georgejames.com/deltanjiEditionsThe free Solo edition is intended for, well, solo situations, with one developer wanting straightforward checkout/checkin source versioning for their namespaces on their local Cache / Ensemble instance.In your context the Team or Enterprise editions are more likely to be appropriate, particularly since the comparison table shows LUTs not being supported by Solo.Deltanji is capable of a lot more than simple code versioning. Please contact me via the George James Software website if you'd like to evaluate Team or Enterprise editions, or if the capabilities of the Deploy edition are of interest to you.
go to post John Murray · Jul 10, 2018 Since you're using Ensemble, you may also like to know that Deltanji integrates with the Portal-based editors and with Studio, as well as with Atelier. It is server-side source control, so has no problem with scenarios where multiple developers work as a team in a single namespace.
go to post John Murray · Jul 10, 2018 Yes, Deltanji handles LUT and HL7 components natively. And yes, it's a paid product, though there is a free Solo edition.
go to post John Murray · Jul 10, 2018 Manish, I highly recommend you use the normal support channel for this, i.e. contact WRC.
go to post John Murray · Jul 10, 2018 IMO your best chance of getting this issue addressed by InterSystems is to engage with them through WRC (Worldwide Response Center).
go to post John Murray · Jul 10, 2018 Are you "committed" to using GIT as your source control? If not, maybe take a look at Deltanji from George James Software (my employer).
go to post John Murray · Jul 6, 2018 It worked for me (2017.2.2 on Windows): C:\InterSystems\Ens172\bin>CSESSION ENS172 < c:\s\try.script Node: TIN, Instance: ENS172 USER>zr USER> ; Test routine created by try.script file USER> w !,"This is written by INT routine ",$t(+0) USER> w !," which is created from a script injected to csession." USER>zs MyBootRoutine USER>d ^MyBootRoutine This is written by INT routine MyBootRoutine which is created from a script injected to csession. USER>; Clean up USER>zr zs MyBootRoutine USER>h C:\InterSystems\Ens172\bin> Maybe your indented script lines (the ones to insert into the routine) aren't starting with $C(9)
go to post John Murray · Jul 6, 2018 Has InterSystems yet published any guidance to help existing Caché or Ensemble users move their code onto IRIS? I haven't yet found that kind of document at https://docs.intersystems.com/
go to post John Murray · Jul 6, 2018 Make your script create an INT routine and run it. Example try.script below. Your lines of code either begin with the TAB character or with a label followed by TAB. zr ; Test routine created by try.script file w !,"This is written by INT routine ",$t(+0) w !," which is created from a script injected to csession." zs MyBootRoutine d ^MyBootRoutine ; Clean up zr zs MyBootRoutine h
go to post John Murray · Jul 5, 2018 Anyone watching this thread may find the following answer from @Alexander.Koblov on another thread helpful.https://community.intersystems.com/post/atelier-connection-broken-error##node-450031
go to post John Murray · Jul 5, 2018 Anyone watching this thread may find the following answer from @Alexander Koblov on another thread helpful.https://community.intersystems.com/post/atelier-connection-broken-error##node-450031
go to post John Murray · Jul 5, 2018 Anyone watching this thread may find the following answer from @Alexander Koblov on another thread helpful.https://community.intersystems.com/post/atelier-connection-broken-error##node-450031
go to post John Murray · Jul 5, 2018 Interesting! I've been suffering from the same problem, so I've just added those two lines in the hope they're a solution. Time will tell...
go to post John Murray · Jun 29, 2018 FWIW, my money is still on this being caused by the Linux firewall on the server not allowing incoming TCP connections to port 1972.
go to post John Murray · Jun 29, 2018 Those look correct.Is there perhaps a firewall blocking your Studio host's TCP/IP access to port 1972 on your server?Is the %Service_Bindings service enabled? Does it have any IP restrictions specified?
go to post John Murray · Jun 29, 2018 Probably not. But prior to 2010.1 we didn't have $NAMESPACE, and its forerunner $ZNSPACE couldn't be NEWed. So code might look like this: set currentNamespace = $znspace znspace "%SYS" // do stuff znspace currentNamespace
