go to post Vic Sun · Nov 22, 2019 Hello Roberto, I see that my colleague in the WRC has already addressed some of your concerns in the case, but to share some information with the developer community, here are some documentation links that may be useful to understand <STORE> errors: Low Memory and <STORE> Errors $zstorage bbsiz The first thing I notice is that your $zstorage is set to 16384. This is far below our modern default of 262144 (see bbsiz documentation). Is there a particular reason you would want to modify $zstorage on the fly rather than just have your system-wide setting be higher?
go to post Vic Sun · Nov 19, 2019 Hello Tamara, It sounds like you are looking for help getting familiar with Ensemble rather than specifically with the EnsLib.HL7.Operation.FTPOperation. Note that the operation is intended to send out a file from Ensemble to an FTP server, not to ingest a file; if you want to pull in a file from an FTP server to Ensemble you want an FTP Service. You can find some great starter materials on learning.intersystems.com. You can search for "productions" or "integrations" for some useful courses, but I would recommend "Building Your First HL7 Production." Specifically, I think the sub-course "HL7 I/O: Using HealthShare for Message Transmission" would be very useful. Some basic documentation is here also: Adding HL7 Business Operations Hope that helps! If you have more specific questions feel free to ask.
go to post Vic Sun · Nov 18, 2019 Hello Dan, As of Studio 2019.2 IRIS Studio is compatible with Caché and Ensemble as well. Studio is backwards compatible and the latest version is the most stable, so it seems that the only standalone Studio installation available is IRIS Studio. You can get older Studio versions by performing client installs using Caché kits, but there is no advantage to doing so.
go to post Vic Sun · Nov 5, 2019 Cancelling compaction in IRIS is supported and there is no risk of a data integrity issue.
go to post Vic Sun · Nov 4, 2019 Please make sure the version you are on is safe to run compaction. See Pete Greskoff's 3 links in this developer community post: https://community.intersystems.com/post/how-reduce-size-intersystems-cach%C3%A9-database-file-cachedat In InterSystems IRIS as of 2019.1.0, you have the option to monitor and cancel database tasks such as compaction: Using Character-based Security Management Routines ^DATABASE option 15. Show background database tasks"Displays a list of background tasks that are running or that have run since startup. You can also use this option to re-enter the monitor screen, where you can cancel a currently running task as well as purge the history of completed tasks. (Note that the tasks listed here are not the same as those listed as scheduled tasks in the Task Manager.)"
go to post Vic Sun · Nov 4, 2019 Every instance has at least a default local license server installed: LicenseServers I'm not certain I understand the full sequence of events here or the the different keys that you attempted to use. If you want to look deeper into this the WRC can help you review the keys and look into that license message (and cconsole.log context I'm sure).
go to post Vic Sun · Nov 1, 2019 Hello Robert, It looks like this message was informing you that you needed to activate a key, and that once you did so the message disappeared. Did you notice any other licensing related messages? What clarification were you looking for in terms of context/content?
go to post Vic Sun · Oct 31, 2019 Hello Yunier, Have you considered mirroring? A reporting async sounds like what you're looking for. Mirroring Reporting Asyncs
go to post Vic Sun · Oct 22, 2019 Pandiyan, OpenVMS is no longer supported for newer InterSystems releases: https://community.intersystems.com/post/vsi-openvms You can also find our supported platform documentation for IRIS 2019.2 here: https://cedocs.intersystems.com/documentation/ISP/ISP-iris20192/ISP_technologies.html#ISP_platforms_patches Other versions' documentation are available at docs.intersystems.com, but no versions of IRIS support OpenVMS.
go to post Vic Sun · Oct 18, 2019 Hello Paul, I believe that log message comes from your own code and I am not sure how your code determined those calls changed. Note that $zu calls are deprecated, undocumented, and subject to change at any time, so you should replace them with supported APIs. Obsolete And Deprecated Functionality I would recommend reaching out to the WRC or your ISC sales rep to discuss further if you have doubts. Perhaps Eduard's post is sufficient for you to replace the functionality. Edit: upon further inspection of the linked documentation, replacements do seem to be available for the calls you mentioned. Config.JournalFreezeOnError Security.SystemDBEncJournal Config.MiscellaneousIEEEError
go to post Vic Sun · Oct 18, 2019 Hello Pandian, This should be a larger discussion with your InterSystems sales rep. I would highly recommend reaching out to them.
go to post Vic Sun · Oct 8, 2019 Hello James, This documentation should contain the answers you seek: Displaying Free Space Information. You can use the System Management Portal's Databases page, or ^%FREECNT. Hope that helps!
go to post Vic Sun · Oct 4, 2019 Hello Rick, You might need to explain more about your criteria. The Business Service should be checking if filename and time modified match to determine if the file is the same. You may be able to just change the timestamp when you want to recheck. Alternatively, you may be able to code some logic to have the files be moved to an archive path and then brought back over into the file path when you want to retry. Settings for the File Inbound Adapter There might be a way to modify the "already processed" status of a file, but I'm not sure if that's a great idea and you may want to discuss it with your InterSystems representative.
go to post Vic Sun · Oct 3, 2019 Hello Sachin, Can you provide the version of your product from the about page in the management portal or "w $zv" from the terminal? This behavior varies across versions so you can probably find more information in the relevant version of our documentation. Also, please be clear about whether you are referring to namespaces or databases. This documentation may be what you are referring to: Where Ensemble Stores Temporary Data
go to post Vic Sun · Sep 27, 2019 Hello, First of all I wonder what version of Caché you are using as ^MSU has been replaced by ^DATABASE for a long time. That being said, I can't imagine there being any problems with interrupting using ctrl+c. In fact, as you didn't get an <INTERRUPT> error it seems likely that ^MSU/^DATABASE has accounted for a user trying to ctrl+c out and so just returns you to the previous menu.
go to post Vic Sun · Sep 24, 2019 Hello Daniel, As Kenneth mentioned, outside of shadowing/mirroring journaling could still be very important depending on your usage. https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCDI_journal For example, journals are needed in a disaster recovery scenario in order to bring your instance more up to date than the time of the backup itself. If you are not journaling and restore a backup your data will be current as of the time the backup was taken. Replaying journals would be necessary to proceed beyond that. You would only need the journals created after the time of the backup. Also note that I would recommend testing your backup restore procedure and regularly taking integrity checks to confirm the validity of your backups. I would go so far as to say a backup that has not passed an integrity check is not a valid backup. https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GCDI_backup
go to post Vic Sun · Sep 20, 2019 While I suspect this is related to the read-only / mirrored-ness of the backup failover member, I would recommend reaching out to the WRC for a more thorough investigation. Alex and Alexey suggested a nice workaround as well.
go to post Vic Sun · Sep 19, 2019 I'm not sure exactly what your steps were - where did you see that error? I have no problem opening objects without locking in a mirrored database on a backup failover member: MIR>s x= ##class(Sample.Person).%OpenId(1,0) MIR>w x1@Sample.Person
go to post Vic Sun · Sep 19, 2019 Hello Vandrei, Your question is a bit vague but hopefully this helps: https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GOBJ_methods ##class(Package.Class).Method(Args)
go to post Vic Sun · Sep 18, 2019 I didn't do a deep dive but presumably the HL7 message is being opened as an object and therefore automatically taking out a shared lock in order to read it.If you really don't care about locking or concurrency protection, I imagine it wouldn't be that difficult to custom code something to do what you want, though you'd probably want to test:https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GOBJ_persobj#GOBJ_concurrency
