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.

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.

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

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.

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

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?

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.

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.