go to post Vic Sun · Jun 2, 2020 Hello Yone, While you can probably figure out a way to code this in a transform, I think it would me more straightforward and legible to write a custom utility function and put your looping logic there. Ensemble Utility Functions
go to post Vic Sun · May 27, 2020 %ALL should cover everything from the Caché side so I suspect an OS permissions difference. Is the task doing anything that requires OS permissions (this could include writing to an output file)? Do the Caché OS user and the OS user corresponding to your account differ? What other differences could you think of between the two users? Without looking around your system I think it will be tough to troubleshoot this, so I'd recommend reaching out to the WRC. Also, you probably already know this, but 2012 is quite an old version - I'd definitely recommend upgrading if possible.
go to post Vic Sun · May 27, 2020 Hello István, You can find in the docs the following: Using the Task Manager "If the chosen user is disabled, the task is suspended until the user is enabled and the task is resumed manually. This does not apply to built-in System tasks, which run even when the chosen user is disabled." While the system tasks will still work while assigned to run as the disabled _SYSTEM user, it might be a good idea to set them to another user with similar permissions for clarity's sake. The necessary resources for a task are totally dependent on what the task needs to do.
go to post Vic Sun · May 26, 2020 Unfortunately, I'm not aware of anything built-in that can enforce the schema - I think it would be difficult to have this as a preset option because it wouldn't be able to match all use cases. Of course, the ideal would be for the upstream to conform, but that isn't always an option. I think this will have to be a custom solution, though maybe somebody else can weigh in with some option I've missed. Perhaps somebody has come up with something clever to leverage the schema.
go to post Vic Sun · May 26, 2020 DefCharEncoding is a setting for HL7 services that you would add the ! to in order to enforce a particular encoding. If MSH:18 is blank then whatever encoding is in DefCharEncoding will be used, whether or not you use ! for the setting. ! in the message in MSH:18 would probably trigger an error as ! doesn't represent a valid encoding.
go to post Vic Sun · May 26, 2020 Hi Cedric, It sounds like you are adjusting the messages to have ! in the MSH:18 field. Unless I'm misunderstanding, that seems like a misinterpretation of the DefCharEncoding documentation, which I will include here: Default Char Encoding Normally the encoding found in MSH:18 is used, but an "!" at the start of the DefCharEncoding setting will forcibly use whatever encoding you specify. Hope that helps.
go to post Vic Sun · May 26, 2020 Hi Elisha, The general method for handling incoming too-long fields would be the validation setting, which can send a message to the bad message handler to be treated as needed: Validation Validating Fields "Test that field sizes in the message conform to the schema." In your case if you know what fields need to be truncated it should be really easy to use a DTL to truncate those fields. Hope that helps!
go to post Vic Sun · May 13, 2020 Hey Murillo, I'm not sure how the SOAP stuff you describe works into the standard Ensemble machinery, and understanding what globals/data are not being purged might be useful to provide further guidance. However, the purge you mention is intended for the activity monitor, and is not the main purge task which is just Ens.Util.Tasks.Purge. See the following docs: Purging Production Data Monitoring Activity Volume
go to post Vic Sun · May 11, 2020 Hi Laura, I don't really have an answer but maybe you can include some pseudo-code or sample code for people to try to reproduce the behavior you're describing. I have an idea of what you're doing from your description but the specifics could be important.
go to post Vic Sun · May 7, 2020 I think the WRC should be able to help out with this - definitely seems like an odd issue worth investigating.
go to post Vic Sun · May 7, 2020 Hi Russell, Can you share more of how you're trying to use %Net.SSH.Session and where exactly the error is coming up? Your version information may be useful as well.
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.
