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
go to post John Murray · Jun 29, 2018 If you are indeed telling Studio to use the same Web Server Port that you're successfully using with Atelier, then that's your problem. Studio connections are handled by the Superserver port (e.g. 1972), not the Web Server one (e.g. 57772).
go to post John Murray · Jun 18, 2018 Alongside the CACHE.DAT file is there a cache.lck file? If so, this could be preventing the new Cache instance from mounting the CACHE.DAT file by indicating that the database is currently mounted by another instance.
go to post John Murray · Jun 18, 2018 How about also updating the beta repo to 1.2.119 ? As things stand I had to add the 1.2 Stable repo to my list of sites in order to update my 1.2.118 beta to 1.2.119
go to post John Murray · Jun 15, 2018 I doubt if Studio will be able to compile them faster than Terminal can. After all, when Studio compiles them, it asks the server to do the work. That's also where your Terminal compile happens.
go to post John Murray · Jun 13, 2018 It sounds like you're seeing the same value in the "License Id" column as in the "ID" column. So I guess your Cache was installed with Minimal security and you're not requiring Portal users to supply credentials, right?It's my experience that when CSP users (e.g. Portal users) have to authenticate, the "License Id" field of their CSP Session record includes the IP address they're connecting from, as well as the username they logged in with. This can be useful in working out who is using all the sessions.
go to post John Murray · Jun 13, 2018 When you view the CSP Sessions page in Portal, does the "License Id" column give you any useful information?
go to post John Murray · Jun 12, 2018 If you use the IF style, I suggest you also consider using the ELSEIF clause. See doc here. set caseSwitch = 1 if (caseSwitch = 1) { write "Case 1" } elseif (caseSwitch = 2) { write "Case 2" } else { write "Default case" }
go to post John Murray · Jun 12, 2018 Yes, the badges seem to get awarded retrospectively. But for some reason the Challenges section of my Global Masters page still lists the associated challenges for two badges I've already received:
go to post John Murray · May 31, 2018 Manish, IMO you really need to open a support ticket with InterSystems about this kind of issue. DC isn't a substitute for the excellent support that InterSystems WRC can offer.
