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
hAnyone 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
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
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
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...
FWIW, my money is still on this being caused by the Linux firewall on the server not allowing incoming TCP connections to port 1972.
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?
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
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).
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.
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
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.
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.
When you view the CSP Sessions page in Portal, does the "License Id" column give you any useful information?
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:
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.
Yes, please do that Nicole.
Nicole, this inconsistency between Atelier Explorer (where some packages are shown as white) and Server Explorer (where none are) still exists in 1.2. For example, in AE the %Compiler package is white because it contains no classes, only subpackages:
In SE this doesn't happen:
Is it still on someone's radar there?
Nicole, after starting once with the -clearPersistedState command-line switch I am now able to use my original workspace.
Intriguingly, after doing this both my original workspace and the fresh one I had created after upgrading to 1.2 now complain about connecting to a server whose /api/atelier web app only accepts Unauthenticated access. Before "-clearPersistedState" my freshly-created workspace was willing to connect to such a server (incidentally, that server was a fresh install of IRIS 2018.1.1, which still offers Minimal Security as an install option).
This seems to have been addressed in Atelier 1.2. Using build 118 from the beta repo I get the following when testing a connection to a server installed with Minimal security (which somewhat surprisingly is still an option when installing IRIS 2018.1.1)
To resolve this I must enable another authentication method (e.g. Password) on the /api/atelier web app:
Probably a good idea to deselect Unauthenticated. Even though Atelier doesn't seem to allow anonymous connection to /api/atelier REST service I guess it'd be possible to do this directly.
I switched to my upgraded 1.1 workspace and tried a couple of times launching Eclipse with 'eclipse -clean' but still get the errors. It's not critical for me, as it was only a play workspace. But it might matter more to other folk if they have the same experience.
Update: starting with a fresh Eclipse workspace seems to be helping...
For the record, it seems 1.2 has appeared in the Beta repo that's documented at https://download.intersystems.com/download/atelier.csp#plugin -
https://atelier.artifactoryonline.com/atelier/updates/beta/latest/
Hmm, not looking too good so far:
Sounds like a case for WRC.
Where are you running the GBLOCKCOPY? If on your 2014 environment I think you'll be having the same problem as when you just tried to mount the database there. GBLOCKCOPY needs to mount it before it can copy block from it to your new database.
Most likely, your original database has 2KB blocks. Your problem then is, 2014 can't mount any databases with 2KB blocks. The last version supporting 2KB block databases was 2011.1. See here.
What Cache version are you using?
Do you have login credentials for WRC Online at http://wrc.intersystems.com/ ?
Once you have logged in, use the "Online Distributions" link. You'll need to contact your InterSystems account manager to request a license key.
Alternatively, get your hands on InterSystems IRIS in the cloud here.