go to post David.Satorres6134 · Sep 3, 2024 Hi Scott, Maybe you could can simply use mapping to split the globals from each namespace in different databases and have them in different disks. In my experience, this speeds up the system as reading from different disks at the same time avoids the problem on the max IO reached by the reader daemon. And you can even have different blocksizes that match better with the global structure. Splitting routines and globals might sound nice, but you'll end up with a very small one (routines) and a massive one (the data).
go to post David.Satorres6134 · Aug 27, 2024 Hello Eddy, You might try this: ##class(HS.Hub.HSWS.WebServicesClientAPI).WebMethod("AddFacility").Invoke(##this,"http://www.intersystems.com/hs/hub/hsws/HS.Hub.HSWS.WebServices.AddFacility",pRequest,.pResponse) There is an AddFacility method in HS.Hub.HSWS.WebServicesClientAPI.
go to post David.Satorres6134 · Jun 29, 2024 Yes, I would totally recommend running it after any version upgrade. Won't do any harm, and surely solve issues related to changes on depending intersystems classes.
go to post David.Satorres6134 · Sep 29, 2021 Finally opened a WRC and got an answer: update to 2021.1 as categories have much improved. :)
go to post David.Satorres6134 · Nov 24, 2020 Answering myself: For a system with 8 cores, we will be allowed to use maximum 16 workers. So, to be able to do it and let other processes work with the default queue, we we just need to set the global: s ^%SYS("WQM","MaxActiveWorkers","User.Testing")=16 so, when creating the queue it can be done attaching the workers to this queue: set queue=$SYSTEM.WorkMgr.%New("/multicompile=1",16,"User.Testing")
go to post David.Satorres6134 · Jun 20, 2020 I answer myself, in case someone is in the same issue. WRC response was:The short answer is that unfortunately there is no stand-alone kit for Atelier, as it is distributed only as a plug-in for Eclipse, and as such it follows the official Eclipse distribution mechanism. But they gave me a few hints. Finally, I downloaded all the atelier package using wget from another computer, zipped it, copied to the computer and have it installed as local zip package. Worked like a charm :-)
go to post David.Satorres6134 · Jul 3, 2019 My mistake... the odbc driver name was wrong :'( I can connect now :)But I see that I have to rewrite the functions because the prepare, execute, fetch, etc attributes doesn't exist in pyODBC :'(UPDATE: just by changing a few lines allowed me to work with pyODBC.
go to post David.Satorres6134 · Apr 11, 2019 I can't remove the question, so I answer myself. The problem was at the routine called by the queue: a "lock" instruction seemed to break down everything.So, removing the line solved the problem :-) Now I just need to know why locking a global messes the whole thing up :-O
go to post David.Satorres6134 · Feb 26, 2019 Sorry, I just saw I can do:Index NewIndex On Test(ELEMENTS).Name
go to post David.Satorres6134 · Sep 11, 2018 I just installed 1.3 and it still not there :O And Intersystems announced they won't be any enhancements from now on.So I guess this is all we'll get.
