Hello Augusto,

I think you're at the right part of the documentation. I'm not sure what specifically you are asking about. The actual "upgrade" on Unix involves running cinstall as if you were installing a fresh instance, and you can target the existing instance. The docs cover what else needs to be done before/after that.

I hope that helps? I would definitely recommend testing the procedure to familiarize yourself.

I agree with Pravin that <STORE> errors generally indicate a lack of process private memory which you can try to address by raising that limit. Documentation on <STORE> errors here: https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=RCOS_vstorage#RCOS_C132257

The other practical side of things though - can you use smaller subfolders rather than one that needs to host so many files? Do you really want your process to have to scan through that many files?

Hello Muhammad,

I would recommend reading this section of the documentation on Assets and Resources.

"Users and applications interact with InterSystems IRIS databases through namespaces. While there are no privileges associated with namespaces, access to a namespace is granted or denied based on the privileges associated with the underlying databases. More specifically, to access a namespace, you must hold the Read privilege on the default globals database associated with that namespace."

Gary - as far as I know, the IRIS for Health docs should only be additional pages on top of the base IRIS documentation. Is there anything missing that you were looking for?

I would second Julian's suggestion (and also his note that having a password in plaintext would probably not be great), as OS auth is the most common solution I've seen for people looking to run scripts without needing to explicitly log in to terminal.

You mention authenticating by other means; delegated authentication is generally how you would implement custom authentication by writing a ZAUTHENTICATE routine. If you're not already familiar, see the docs:

https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls?KEY=TSQS_DelAuth

That might be overkill for what you describe as a small tool though...

Depending on what this automation is, does it need to log in in the first place? Could you set it up as a task to run within IRIS? Perhaps a bit more detail on exactly what you want to do could point to other workarounds.

I look forward to seeing if other people have other solutions though.

Ah, I see, I've misinterpreted your query, apologies for that. I'm not sure about this behavior! If somebody doesn't have an answer for you, this sounds like something you could raise with the WRC.

Hello Eduard,

The following isn't a answer to your literal question, as that would probably take specific testing to see what the behavior would be. However, the best practice would be to stop a component while you're updating it. That applies to a business process and any other situation where you're updating an active component, to prevent any sort of compatibility or timing issues that could cause unexpected behavior in your production.

Jay,

I recognize your frustration. I'm not an expert on this topic but I think different antiviruses have different patterns that they check for and it might not be possible to avoid all false alarms.

Kaspersky have this to say on the subject:

https://support.kaspersky.com/viruses/answers/1870

"A false detection, or a false positive, is a case of incorrect detection of a clean file or website as infected.

Unfortunately, manufacturers of security solutions cannot avoid false detection. At Kaspersky, we continuously improve the product testing system and strive to decrease the number of false positives. However, it is impossible to completely avoid such cases, as new threats arise every moment."

Hello Evgeny,

The ^%SYS.NOJRN tags are actually not system-wide, and just at the process level. That being said, for changing the actual database journaling status, perhaps Lucas' solution makes sense.

For more info on disabling journaling, I think Tani's article series is great. Here's his chapter on some methods to disable journaling. Perhaps you'll find something useful to you now or later:

https://community.intersystems.com/post/preventing-globals-getting-journaled-continued-how-do-i-minimize-my-journals

FYI, just a plug to avoid $zu commands whenever possible, as they're internal/deprecated and subject to change. $zu(12) can be replaced by %Library.File.NormalizeDirectory().

Here are the docs with almost all the $zu functions' modern replacements.

https://docs.intersystems.com/latest/csp/docbook/Doc.View.cls?KEY=RCOS_replacements

I also did not see an overwrite server option, but when I saved the catalog.cls/inventory.cls files (I used command+s) and checked the ObjectScript explorer, I saw my classes had been updated and compiled. You could mention this to the online training team as well, as the "overwrite server" item might be a detail from a previous version of the tutorial.

I'm not sure if some particular sequence could cause you to need to manually check an "overwrite server" box.

Crys,

I'd recommend reaching out to onlinetraining@intersystems.com so they can look at your sandbox specifically, I don't think I can help with that.

Agreed with Dmitry.

You can read more about community edition, including its limitations (there's also a 10gb and 5 connection limit) below. This also gives a sample of restricting cores using docker:

Deploy and Explore InterSystems IRIS

If this is for personal use, community edition and containers could be a good option. If you're working with an org, you might want to discuss with them (or your InterSystems rep) whether it would make more sense to get a full kit and license.

Hello Muhammad,

What problem exactly are you having? Enslib is a database, not a namespace, and I've tested that the database should definitely be installed on your version.

https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=GORIENT_ch_enviro#GORIENT_enviro_database_system

"ENSLIB — This is a read-only database contains additional code needed for InterSystems IRIS Interoperability features, specifically the ability to create productions, which integrate separate software systems.

If you create a namespace that is interoperability-enabled, that namespace has access to the code in this database."