You can enter the arguments to pass into a Run/Debug Configuration here:

I'm not sure what you mean by the "select class file" that you are trying to pass in. Here is the method signature for %UnitTest.Manager/DebugRunTestCase:

ClassMethod DebugRunTestCase(testsuite As %String = "", testcase As %String = "", qspec As %String = "", testmethod As %String = "", ByRef userparam) As %Status

Which parameter are you trying to pass in?

Hi John,

To answer your first question - I just looked over the development change that implemented the compare with server option. The developer commented that this has only been implemented in the Atelier Explorer context menu so far and that this feature will be coming up in the Editor context menu. I don't have a timeline for you on that.

I'll have to let someone from the development team speak to your second question. I'm not sure why the replace with server option appears and is disabled.

As a member of the Support team, I also wanted to let you know that you can absolutely file a WRC case with Atelier questions! The product options we provide are intended to find out which of our server products you are using. Feel free to ask any Atelier questions you'd prefer to keep separate from the Developer Community in the WRC (for example, if you have a question that you expect will require a lot of back-and-forth to reach a conclusion).


Thanks for reporting this Peter. It looks like Atelier is not properly recognizing the end of a class' Query member. I found a couple other ways that this issue presents itself - a syntax error on the closing bracket of the class before you compile, and any class members following the Query are not listed in the Outline.

I logged this bug for the Atelier development team (internal reference ATL-4372).

Hi Fred, I was not able to reproduce this behavior on my system. What version of Atelier are you using (Help > About Atelier)? What Caché/Ensemble/HealthShare server version (enter "write $zv" in a Caché Terminal)?

I work in the Support department, can you open a WRC case to investigate this further (email or call 617-621-0700)? Once we determine exactly what is necessary to reproduce we can post the results here in the Developer Community so this is public knowledge.

The Studio Inspector will not be implemented as-is in Atelier. However you can still view the same information in Atelier:

To see a class' properties, methods, parameters, etc. you can use the Atelier Outline view. That is shown in the answer to the DC post that Vitaliy linked to: Currently this shows only the members in the current class, not those that come from superclasses. A "Show Inherited" option is planned for an Atelier 1.1 release.

Hi Shobha, here is the relevant documentation about using Ensemble with SOAP:

This should give you some background about using Ensemble to send and receive SOAP messages. I would suggest reviewing this and letting us know if you have any specific questions, configuration problems, errors, etc. You can also reach out to Support or your InterSystems Sales team with more involved questions that might be easier to discuss on the phone rather than in the Developer Community.

Hi Jean,

I tried out the Eclipse SQL Explorer and was able to connect to my local instance just fine. I installed the plug-in using the update site from the link you provided,

Then I opened the associated perspective by going to Window > Perspective > Open Perspective Other > SQL Explorer. I right-clicked in the Connections view and hit New Connection Profile. I had to select Add/Edit Drivers to add the Caché JDBC driver with these settings:

The keys were to 1) select the Extra Class Path tab and Add JARs to pick the JDBC driver from my Caché install directory and 2) to add the correct Driver Class Name, com.intersys.jdbc.CacheDriver.

Once I had that configured I selected it in the Connection Profile Wizard, entered my JDBC connection URL, jdbc:Cache://localhost:56773/SAMPLES, and selected the authentication information:

This also worked for me when I unselected "Username is not required", checked "Auto Logon" and entered my Caché credentials.

I right-clicked the connection and hit Connect. Then double-clicking the connection (listed as "Connected since <timestamp>") opened the connection in the Editor where I could enter my SQL statement:

Where are you running into problems?

That was true in older versions of InterSystems products, when cached query code was stored in routines rather than classes. A problem could occur if a query executing in one process required round trips from the client to server and a separate process purged cached queries while the client application was still using it. Development resolved this by moving the cached query code into classes - the class definition and OREF are now stored in memory until the client process is done executing the query. This makes purging cached queries safe on a live system in more recent versions.

The change was implemented starting with Caché 2010.2.0 for dynamic SQL and Caché 2012.2 for xDBC queries.

1. You can create a new legacy task (allows you to run COS code) in your application namespace from the System Management Portal:

The command to purge all cached queries in the current namespace is "do $SYSTEM.SQL.Purge()". That is described in our class reference here:

2. I am checking in with development on which Caché version resolved this bug.

Development did a code review and determined that this is a bug with the cached query generation code in Caché 2014.1. As far as I know we've only seen this for queries executed via xDBC.

There is a place in the cached query generation code where an error may not be properly trapped. In this case the cached query routines are not created properly, but no error is reported back. Then when Caché tries to use that cached query code to execute the query the expected methods do not exist.

The possible solutions we've come up with:

1. Create a task to purge cached queries in your application namespace - Pick a task frequency that means it will run more often than you have seen errors occur. This way you aren't stuck manually purging cached queries whenever an error pops up.

2. Get a development patch containing some fixes for your version of Caché - For this you will need to contact either your InterSystems Sales team or Support to file a WRC case. Note that our development patches do not go through our standard QD testing process. If you apply this patch you will be working with a version of our code that has not gone into any released product.

3. Upgrade your instance - This is the only long-term solution. Our cached query generation code has been rewritten in later versions of the product and this is no longer a problem.

You can use the Outline view in Atelier for information about the current class' properties, parameters, class methods, etc:

There is an enhancement request to show inherited members in the Outline view which is currently planned for Atelier 1.1.

Atelier's code completion, which can be accessed by hitting ctrl+space, is also a good tool here. For example you can use code completion to quickly check the possible options for an index's keywords (with documentation):