Vic Sun · Mar 31, 2020 go to post

Hi Laura,

There are some tables covering schemas that might be of use to you as documented here:

Exporting a Production

"Export the underlying Caché global that contains the schema and then import this on the target system. To export a global, select System Explorer > Globals, select the desired globals and then select Export. The X12 schemas are stored in the EnsEDI.Description, EnsEDI.Schema, EnsEDI.X12.Description, and EnsEDI.X12.Schema globals. The XML schemas are stored in the EnsEDI.XML.Schema global. See “Exporting Globals” in the Using Caché Globals guide for details on exporting globals."

Vic Sun · Mar 31, 2020 go to post

Hello Dan,

I am struggling to understand the scenario that you are testing/planning for. Do you have an arbiter? I would read through the mirroring docs which discuss the various options available to you and the various automatic responses that mirroring can take (including some diagrams).

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

https://cedocs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=GHA_mirror#GHA_mirror_set_autofail_outages

If you want to simulate network isolation, I think you'd need to actually network isolate. If you force the backup to become primary, Caché will try to force down the original primary to prevent split brain.

Vic Sun · Mar 30, 2020 go to post

If you can't identify a permissions issue I would recommend opening a WRC case to investigate as it will probably take some looking around at your system to resolve, and that isn't easily done via a forum.

Worth considering is if this works in other environments and if so what the difference in permissions might be, and if you can try the freeze or journal switch directly in Caché terminal (taking the OS terminal out of the equation).

Vic Sun · Mar 30, 2020 go to post

Hello Augusto,

If you're on Unix error 13 is permission denied so I would definitely suspect that this is a permissions issue. Do you have any other journaling issues (maybe other messages in cconsole.log)? Can you try running your commands straight in the Caché terminal and see if they work?

Vic Sun · Mar 24, 2020 go to post

Hi Daniel,

The audit log would probably be a good place to look.

Vic Sun · Mar 2, 2020 go to post

Hi Joe,

If you haven't seen it already, our Printers documentation could be useful for you. You could try printing some things from terminal just to test and then see if you can implement it into your production. Eduard's question is relevant as well to see what you can actually do.

Vic Sun · Feb 18, 2020 go to post

Hi Hansel,

For a mirroring issue usually the full context of all mirror members is usually important to understand a problem, whereas a singular message may not paint the whole picture.

This error in particular (you included an excerpt, but I have seen it before) indicates that this instance is unable to take over the VIP, so you may want to check if the VIP is available or if it may be assigned to a different machine as the rest of the error message would indicate.

Vic Sun · Feb 17, 2020 go to post

Are you using an Archive Path or Work Path?

When you look at the Visual Trace does it give you any more ideas for where issues could be cropping up?

Can you elaborate on this: "It appears like the same file gets picked up by a later session but we have no way of knowing if it is the same doc or not."

Do you mean that the file is sometimes picked up but with a reported filesize of 0kb? What business process is attempting to move the file to a working directory?

What were the errors that you had previously? If Ensemble is having trouble picking up the file it may be a fileshare availability issue.

This is likely not going to be easy to troubleshoot through this forum, I'd recommend reaching out to the WRC to investigate.

Vic Sun · Feb 5, 2020 go to post

Wish I could be of more help, but I think there is no longer a freely available trial version of Caché, and if you are looking for a download you would need to go through your company. You may want to reach out to your ISC sales team to see if something can be arranged.

Vic Sun · Feb 4, 2020 go to post

Hi Christopher,

I'm not sure where you're seeing Download Caché Evaluation, all links show IRIS instead for me. IRIS is the product of the future for InterSystems so it's what is being presented for evaluation. Is there a particular reason that you need Caché? If you are a supported customer you can still get access to Caché through the WRC but if you are looking to try an InterSystems product then IRIS has Caché's capabilities and then some.

https://www.intersystems.com/try-intersystems-iris-for-free/

Vic Sun · Feb 4, 2020 go to post

The $job documentation put me on the path to look deeper into %SYS.ProcessQuery. The class documentation recommends using SQL to avoid the overhead of opening the object. It also recommends looking for a property that doesn't require sending a mailbox message to the process.

%SYS.ProcessQuery

For example:

SELECT CommandsExecuted FROM %SYS.ProcessQuery where pid=5812

If the pid exists the query will return a row, otherwise it will return nothing. Hope that helps.

Vic Sun · Feb 4, 2020 go to post

I'd have to think a bit on what the "best" way to do this would be, but the following seems to work:

%SYSTEM.Process.JobType()

In my admittedly quick testing, it will return 0 for a process that doesn't exist.

Vic Sun · Jan 9, 2020 go to post

Your user may have permissions to write a file to the output directory, but that doesn't mean you will have access to all the utilities that pButtons will try to run, including Windows Perfmon. There should definitely be more than 1 log file is a pButtons is running normally.

I wonder if the Buttons report was able to collect its cstats as that also requires elevated permissions. You can check that section within the html report to see if it exists.

I would definitely recommend opening an Administrator Windows command prompt and then navigating to \cacheinstalldir\bin, where you can use "ccontrol console <instancename>" to access the terminal. From there try to run a test pButtons.

Vic Sun · Jan 9, 2020 go to post

What's in the log file? Prior to collection in the html there should be multiple log files containing various pieces of information, so tracking down what is/isn't collecting could be useful.

I suspect OS permissions, can you open a terminal making sure you have administrator privileges so that you can run the proper performance monitoring utilities?

You can just run a test 5 minute run to check if things are running properly.

Vic Sun · Dec 2, 2019 go to post

You can find Studio-only installations in the Components section of the WRC distributions page, which includes versions compatible with IRIS 2019.2.

Vic Sun · Nov 26, 2019 go to post

Hello Duncan,

Please see the following documentation. Defining and Calling Methods.

Some examples:

 do ##class(Package.Class).Method(Args)
 set myval= ##class(Package.Class).Method(Args)
 write ##class(Package.Class).Method(Args) 

You may find some of the courses on learning.intersystems.com (linked in the top bar of the developer community as well) useful such as the Caché Objects Introduction.

Vic Sun · Nov 22, 2019 go to post

16384 was the default a long time ago back in Caché 2011, and upgrades would not automatically change this value.

It is a good idea to review your memory settings periodically to make sure they still make sense for your application and usage. This value having never been tweaked from its default may be a sign that other memory values were never thoughtfully adjusted, so the following article may be of use to you (or your team):

https://community.intersystems.com/post/intersystems-data-platforms-and-performance-part-4-looking-memory

Vic Sun · Nov 22, 2019 go to post

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?

Vic Sun · Nov 19, 2019 go to post

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.

Vic Sun · Nov 18, 2019 go to post

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.

Vic Sun · Nov 5, 2019 go to post

Cancelling compaction in IRIS is supported and there is no risk of a data integrity issue.

Vic Sun · Nov 4, 2019 go to post

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.)"

Vic Sun · Oct 18, 2019 go to post

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.Journal
FreezeOnError


Security.System
DBEncJournal
 

Config.Miscellaneous
IEEEError

Vic Sun · Oct 18, 2019 go to post

Hello Pandian,

This should be a larger discussion with your InterSystems sales rep. I would highly recommend reaching out to them.

Vic Sun · Oct 4, 2019 go to post

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.