go to post Vic Sun · Sep 28, 2021 Augusto, I'd check if the port is taken by something else. Perhaps the OS logs or the IRIS ^SYSLOG will have entries of note?Maybe you can try restarting the web server to see if you can throw an error?
go to post Vic Sun · Sep 28, 2021 Lionel, Check out the following article: https://community.intersystems.com/post/handling-date-and-time-operations-cach%C3%A9 You might want to try something like: %SYS>s time=$PIECE($horolog,",",1)-1_","_$PIECE($horolog,",",2) %SYS>zw timetime="66014,35176" %SYS>w $zdatetime(time,3)2021-09-27 09:46:16 When you just do $horolog-1, you're truncating the time off of $horolog. $PIECE lets you modify and combine the date/time segments of $horolog independently.
go to post Vic Sun · Sep 28, 2021 Hello, Additional context on what exactly you need to do would probably be helpful. If this is something critical, I would consider reaching out to the WRC for assistance. Otherwise, the ^JRNRESTO documentation is where I'd start: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GCDI_journal#GCDI_journal_util_JRNRESTO You can restore a backup and then choose what subset of journals to restore.
go to post Vic Sun · Sep 27, 2021 Hello Garin, Differing free vs available memory is a natural occurrence for Linux. The buff/cache is what's being used by the OS for memory and can be relinquished to applications as necessary. I would check underlying items like OS logs and whether the OS version is supported. error 22 is presumably error 22 invalid argument - not sure what exactly that indicates though.
go to post Vic Sun · Sep 27, 2021 Hi Niko, I'm not sure I understand what you mean by "linking that query into a process", but you can run SQL from Object Script code using either dynamic or embedded SQL: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GSQL I hope that helps. If you are looking for other general guidance for this, feel free to reply.
go to post Vic Sun · Sep 24, 2021 Cedric, Take a look at the server migration guide which contains a list of other items you can export. https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=AMIG You can use the Security.Users.Export() method to export programmatically.
go to post Vic Sun · Sep 24, 2021 Ah, great. Thanks for the update. I'm glad you were able to figure this one out!
go to post Vic Sun · Sep 23, 2021 Hello Igor, What steps did you follow exactly? Do you see any potential permissions issues? Does the messages.log include any useful errors? Did you follow the documented temp directory unzip steps? mkdir /tmp/iriskit # chmod og+rx /tmp/iriskit # umask 022 # gunzip -c /download/iris-2019.3.0.710.0-lnxrhx64.tar.gz | ( cd /tmp/iriskit ; tar xf - )
go to post Vic Sun · Sep 23, 2021 Actually, reviewing more closely, it looks like your version string is for Unified Care Record / Patient Index. That has a different set of requirements than the basic IRIS migration. I'd recommend closely reviewing the HealthShare documentation - I'm not personally very familiar with the HealthShare side of things, but I'm fairly certain there is a version plateau for HealthShare to allow for the move to IRIS. edit: this doc page at least is relevant: Unified Care Record Installation and Migration Guide > Preparing for an Upgrade Installation https://docs.intersystems.com/hs20211/csp/docbook/DocBook.UI.Page.cls?KEY=HEINS_prep#HEINS_prep_considerations "If you are upgrading from a Caché-based Unified Care Record or Information Exchange system earlier than version 2019.1, you must first upgrade to the plateau version 2019.1 before upgrading to this release."
go to post Vic Sun · Sep 23, 2021 Now that you mention it, I think you have not followed a supported migration path. You can find details in the IRIS migration guides available in the WRC distributions page's documents section, but the minimum version to migrate in-place from is 2016.2.x, and it can be used to go to IRIS 2019.1.1+ or 2020.1. It does not support migration directly to 2021.1.
go to post Vic Sun · Sep 23, 2021 Augusto, Ens.Director definitely still exists in IRIS. That error means the "%Library.CacheStorage" class doesn't exist. I don't know why that class would be called, however, as it has been replaced by %Library.Persistent by comparing CE / IRIS docs. Are you sure your in-place migration completed successfully? I assume Ens.Director should try to use the corresponding class in IRIS. I think this is a candidate for WRC investigation.
go to post Vic Sun · Sep 22, 2021 Can you identify what is being locked? Is it possible the lock is on something internal, and not the table itself?
go to post Vic Sun · Sep 20, 2021 Sai, By folder, do you mean moving a class to a different package? It's okay if the class name overlaps, because the package will still differentiate the "full name" of the class. ex, the following can coexist. package1.class package2.class You could also use subpackages such as package1.subpackage.class. Some of the built in class divisions might be helpful for you to compare with - for example, on IRIS for Health, the following packages exist: EnsLib.HL7.Operation EnsLib.HL7.Service etc., for each type of business component. I certainly agree that having Git / source control set up is a good practice. You may also find the built-in production deployment functionality useful:https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=EGDV_deploying
go to post Vic Sun · Sep 20, 2021 Vivek, I looked at learning.intersystems.com and it looks like the FHIR tutorials make use of the new SMP features. For 2019.1, it seems the documentation I linked would be the best starting point. https://docs.intersystems.com/irisforhealth20191/csp/docbook/DocBook.UI.Page.cls?KEY=HXIHFHIR_fhir_productionconfigure#HXIHFHIR_fhir_productionconfigure_init
go to post Vic Sun · Sep 16, 2021 Hello Alicia, I would recommend you reach out to your Athena representative for guidance on what version of IRIS to migrate to. I anticipate you will also need them to distribute to you the appropriate kit. It also sounds like you are planning to go live with this change in the very near future. I would suggest testing this upgrade before attempting in your live environment. edit: I may have misinterpreted your org. If you are licensed directly with InterSystems, I'd recommend reaching out to your InterSystems account rep. If you are licensed through somebody else, they can help you with the migration to IRIS.
go to post Vic Sun · Sep 16, 2021 Sai, I'm not sure I understand your question, but it sounds like you are asking about code package conventions? Perhaps you can describe in more detail what you are trying to do, or give an example? Package Options
go to post Vic Sun · Sep 16, 2021 I'm not sure I understand what you want to do exactly. Presumably, there are at least a few namespaces where you want to access this code. You could test a few namespaces (not the %ALL "namespace", real namespaces) to confirm that you can access the code you have %ALL mapped.
go to post Vic Sun · Sep 16, 2021 That makes sense to me. As the docs explain, there is not really a "%ALL" namespace, it's more of an abstraction to represent a system-wide mapping. Once you have set up a %ALL mapping, I would just directly try to verify that the functionality works as you expect. For example, make a AllMapping package and put your test code in there, then make an AllMapping package mapping for %ALL, then confirm that you can access that code in any namespace.
go to post Vic Sun · Sep 16, 2021 Hello Muhammad, Where are you trying to select %ALL? https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=GSA_config#GSA_config_namespace_addmap_all "%ALL is not visible except for the purposes of mapping data; that is, it is not a real namespace, but a mechanism for mapping data to all namespaces."
go to post Vic Sun · Sep 16, 2021 Vivek, Your version of IRIS for Health doesn't have the SMP UI to create a FHIR server. That was added in 2020.2. https://docs.intersystems.com/irisforhealthlatest/csp/docbook/DocBook.UI.Page.cls?KEY=HXIHRN_new#HXIHRN_new_serverui I'd suggest you look at the 2019.1 docs for your version's instructions. That being said, IRIS' FHIR support is being actively developed so it is changing frequently. If you can upgrade to the latest version of IRIS for Health, you will get access to the most functionality (and quality of life improvements like the SMP option!)
