Kevin,

That's pretty worrisome. <DIRECTORY> is not a problem with the command - it means the instance can't locate that directory - this case, the CACHESYS directory. I would be surprised if there aren't errors elsewhere in the Caché logs.

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

"There is no such directory on the target system, no Caché database, the Caché database is not mounted, or the database is locked by another configuration. For further details, refer to $ZERROR."

This might be a configuration issue, permissions issue, etc. Definitely would recommend opening a WRC at this point, if you can't identify the problem.

Kevin,

It sounds like your namespace prompt has been replaced with a directory path in the terminal. The /mgr path is for %SYS (or CACHESYS, technically), but the fact that it is displaying that way seems a little unusual. It sounds like you're entering the implied namespace for some reason.

Nothing immediately comes to mind for what could be causing this. You said "at some point", do you recall when that was and if any changes have been made?

I wonder if login auditing would give useful information on this. Does logging in as a different user or looking at the user you are using's security settings show anything?

May be worth opening a WRC, as that might be easier than troubleshooting through this forum.

Hello Michael,

John's suggestion might help. Alternatively, try "iris terminal" as I think that's the best practice.

Interact Using the InterSystems Terminal

Hello Lewis,

In my experience, aborting doesn't retry a message. I wonder if something in your production is resending the message? Do you see anything in the logs that speak to what is happening?

This may be worth opening a WRC about - if you do, I would be interested in hearing what you end up finding out.

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.