go to post Vic Sun · May 6, 2020 Hello, I'm able to reproduce the behavior with emergency mode requiring you to enter the emergency mode user/pass to shut down. You are certainly welcome to reach out to the WRC to confirm if this is intended behavior, but I suspect that it is. I am wondering what the use case is here as emergency access mode is a special mode, intended for use "under certain dire circumstances, such as if there is severe damage to security configuration information or if no users with the %Admin_Manage:Use or %Admin_Security:Use privileges are available". In those situations you would be taking manual steps so uninteractive shut down would not be necessary. Could you simply use a normal login and not emergency mode?
go to post Vic Sun · Apr 30, 2020 Hi Michael, For issues with learning courses I would recommend reaching out to online.training@intersystems.com (from the Report Issue/Feedback sidebar on the learning pages).
go to post Vic Sun · Apr 30, 2020 You can check the mgstat's RouLas (routine loads and saves) - see this article that includes discussion of sizing routine buffers, among many other tips for sizing a system's memory config! https://community.intersystems.com/post/intersystems-data-platforms-and-performance-part-4-looking-memory
go to post Vic Sun · Apr 29, 2020 The other commenters have good suggestions but I would recommend additionally collecting a pButtons to compare. Try and determine if there are any differences other than OS - hardware, memory configuration, global mappings, or anything else. We want to make sure we're comparing apples to apples! If everything seems to be the same, then you could reach out to the WRC who can help investigate this further.
go to post Vic Sun · Apr 28, 2020 Hello Eric, I'd recommend reaching out to the WRC for this at 617-621-0700 or support@intersystems.com.
go to post Vic Sun · Apr 27, 2020 As far as I know I don't think this behavior has changed in 2020. While I was testing the monitor myself recently I noticed the dropdowns getting cleared but when I saw that auto-refresh was disabled in newer versions I didn't think I needed to follow up on this. If you disable the refresh global you'll find that the tagline of 60s refresh no longer appears as well. If you really felt this was worth changing I'd recommend that you reach out to your ISC representative (or the WRC) but I would be prepared for the response that the monitor is not intended to be a complete solution. That is not to say that a change to help alleviate the behavior are seeing would not be considered, so if this is really tripping you up it would be worth reporting - maybe others have the same pain and there's enough momentum to get this addressed. You may find the following article useful in terms of building your own monitoring solution. https://community.intersystems.com/post/monitoring-intersystems-iris-using-built-rest-api Hope that helps.
go to post Vic Sun · Apr 27, 2020 Hello Julian, The default behavior in your version would be for the activity monitor page to not auto-refresh, but I saw in one of your posts that you have enabled SMP auto-refresh. https://community.intersystems.com/post/queues-refresh-iris-20191 The activity monitor dashboard is really just a starting point - once you start collecting data using the activity monitor you can easily access the monitor tables such as ens_activity_data.days with SQL.
go to post Vic Sun · Apr 21, 2020 Hello Allan, Caché downloads are available from the WRC downloads page.
go to post Vic Sun · Apr 17, 2020 Hi Julian, You're using curly brackets rather than parentheses at the outermost level. If that still presents an issue I'd recommend adding some traces to see what's actually getting referenced.
go to post Vic Sun · Apr 17, 2020 Hi Julian, You could do this with a custom Ensemble utility function but from your description I think parenthesis syntax should work just fine. Defining Custom Utility Functions Parenthesis () Syntax HL7.(PIDgrpgrp(1).ORCgrp().OBR:UniversalServiceIdentifier.identifier) should return a concatenated string from looping through the ORCgrps - you could then search that string to find the value you are looking for. Hope that helps!
go to post Vic Sun · Apr 17, 2020 I second Robert's recommendation to check the lock table. It is probably best to understand what else is holding the lock than to just try and release the lock - the lock might be there for a reason, and if not you should look into what is taking it out and why. Oliver's suggestion to verify that the lock table isn't full is also a good one.
go to post Vic Sun · Apr 15, 2020 Hi Jordan, Check out the docs on private/public variables here: Callable User-defined Code Modules Variables You can pass the variable to the subroutine as a parameter or declare it a public variable - my guess it passing it as a parameter would be the "safer" option.
go to post Vic Sun · Apr 14, 2020 Hello Eric, This message indicates that an Ensemble job had unexpectedly terminated. I would recommend checking OS logs or looking for other events that could have triggered a process termination outside of Ensemble.
go to post Vic Sun · Apr 7, 2020 Cristiano has a good suggestion but this issue could also depend on the various settings. You've censored pretty much everything so it's difficult to troubleshoot.
go to post Vic Sun · Apr 6, 2020 FileList was likely found in the EnsLib.FTP.Common class reference. This is the class extended by EnsLib.FTP.OutboundAdapter. I suspect that could work also - see above documented syntax for running the query. Hope that helps!
go to post Vic Sun · Apr 6, 2020 Hi Michael, I assume you were looking at the %Library.File documentation for FileListFetch. FileListFetch is not meant to be used directly, but is a part of a class query which can be used as documented here: Defining and Using Class Queries https://cedocs.intersystems.com/csp/documatic/%25CSP.Documatic.cls?PAGE=CLASS&LIBRARY=%25SYS&CLASSNAME=%25Library.File If you can navigate to the directory then you could use ##class(%Library.File).GetFileSize(), however for a remote FTP server this probably wouldn't work. You would want to use %Net.SSH.SFTP as documented here: Using SSH https://cedocs.intersystems.com/latest/csp/documatic/%25CSP.Documatic.cls?APP=1&CLASSNAME=%25Net.SSH.SFTP edit: the FileList query is not in %Library.File - I am not sure where that query comes from but the rest of my post remains revelant
go to post Vic Sun · Apr 4, 2020 Is there any reason you need to run these scripts from a shell script? That would definitely be possible and there are plenty of examples you can find on the community with a bit of searching, but I think it would be quite simple to do this in Object Script.
go to post Vic Sun · Apr 3, 2020 Hi Bharath, I don't really have any sample code for you but I'm not sure I (or other readers) have a good idea of what exactly you are trying to do. Have you already reviewed the class reference? I think the Create(), Get(), and Modify() documentation together describe quite well how you could use Security.Users. https://cedocs.intersystems.com/csp/documatic/%25CSP.Documatic.cls?PAGE=CLASS&LIBRARY=%25SYS&CLASSNAME=Security.Users
go to post Vic Sun · Apr 2, 2020 Hi Augusto, The role that handles backups is %Admin_Operate as documented here: Assets and Resources I don't believe there is a resource that specifically governs the external freeze/thaw capability, you would probably need to design something custom for that particular restriction. For example, you might assign your user a startup namespace or routine as documented here: Users Startup Namespace The namespace in which to begin execution following login from a terminal-type service or the Portal. This property overrides any namespace value provided via the command invoking Caché. Startup Tag^Routine The routine to execute automatically following login from a terminal-type service. This property overrides any routine value provided via the command invoking Caché.
go to post Vic Sun · Apr 1, 2020 Hi Kevin, Thanks for pointing the documentation issue out. The documentation has been modified to specify that the <NETWORK DATA UPDATE FAILED - MAXSTRING> error relates to network activity - "An asynchronous network error occurred and updates sent over the network were lost because InterSystems IRIS/Caché on the server has encountered an attempt to specify or create a data string longer than the implementation allows (32,767 characters)." What were your instances doing at the time you received this error and where did you find this error? I put a little time into trying to throw this error myself by manipulating some large strings from an ECP app server but wasn't able to reproduce it.
