go to post Evan Gabhart · Mar 14 See my reply to Ben, below. Unfortunately it seems the first process is not necessarily correct for instances with an upgrade history from Caché to IRIS.
go to post Evan Gabhart · Mar 14 Thank you for asking this, Ben. The superserver is not the first process and comes after auxiliary write daemons. I also found multiple cases for instances that upgraded from Caché to IRIS where the first process uses cacheusr but the superserver uses irisusr. So this will not work. I think we may be stuck with looking for the superserver process.
go to post Evan Gabhart · Mar 14 I found no direct documentation but got some information from the method documentation of the NextProcess class method in %SYS.ProcessQuery: https://docs.intersystems.com/iris20243/csp/documatic/%25CSP.Documatic.c... So, it seems passing an argument works like $order on the list of running processes with the caveat a halted process is treated like $zjob("") and returns the first process id in the list. I think this will do the trick, thanks Alice!
go to post Evan Gabhart · Feb 26 It sounds like what you want is to use XMLNIL. This will export null object Properties as xsi:nil="true". Then on import the default behavior is to set such a valued Property to be a new instance of that object with no Properties set. See Handling Empty Strings and Null Values | Projecting Objects to XML | InterSystems IRIS Data Platform 2024.3for more information.
go to post Evan Gabhart · Apr 25, 2024 One way I can think of is to get the name of each config item that is enabled via an SQL query such as:SELECT Name, ClassName FROM Ens_Config.Item WHERE Production = '<production name>' and Enabled = 1Then for each of these call ##class(Ens.Director).EnableConfigItem("<production name>||<config item name>|<config item class name>", 0)I am not sure of any method to do it all at once.
go to post Evan Gabhart · Apr 23, 2024 Hello Larry, thanks for pointing this out! I believe this is caused by a bug that caused extra end of line characters in certain circumstances that has now been fixed. The fix will be part of 2024.1.1 and 2024.2.0. If you have any further questions, I encourage contacting support to see if they can help.
go to post Evan Gabhart · Mar 26, 2024 I really enjoy taking things apart and breaking them down into basic components to see how they work. I found it useful to insert break statements in a confusing piece of code and run it from terminal (can also use the ObjectScript debugger from VS Code with breakpoints). Then I could write out the values at each break and reverse-engineer what the command/method must do. I also really enjoy the ability to drill down into the code and read the definition of a method. If you are curious how any method works you can just Ctrl+Click from VS Code to go to that method's definition(Ctrl+Shift+G from Studio).
go to post Evan Gabhart · Feb 21, 2024 @Brett Saviano I do suppose $System.OBJ.Load and LoadDir from a terminal in VS Code is the next best thing until my work involves UDL exported routines. Thank you for the quick response!
go to post Evan Gabhart · Oct 6, 2023 I had forgotten how the MPP works. Then outside of copying the compiled expression I cannot use macros in a break from a terminal session. Thank you!
go to post Evan Gabhart · Oct 6, 2023 I am specifically referring to using terminal/command line. Otherwise, the debugging tools offered by Studio or VS Code would be a decent solution.
go to post Evan Gabhart · Oct 5, 2023 I have found a tentative solution in checking the compiled .int code and copying the resulting lines from there into terminal. It still would be helpful to know if there is a way to access the individual macros directly from within a break.
go to post Evan Gabhart · Sep 14, 2023 If this was tied to your Windows password and you recently changed it then you may need to change the credentials for the service.Try searching for "Services" in the windows search box and open the app. Then find the service associated with this instance (I think it would be InterSystems IRIS Controller for LATEST) and open properties and go to log on tab. Change the credentials here to match your OS credentials and then try starting your instance. Hope that helps!
