#Caché

I am connecting to an intersystems cache database via C# and I need to obtain a list of all available namespaces.

I am using code like this:

// Source - https://stackoverflow.com/q/79393836
// Posted by Tony Valenti, modified by community. See post 'Timeline' for change history
// Retrieved 2026-04-21, License - CC BY-SA 4.0
namespace ConsoleApp13
{
   internal class Program
   {
       static void Main(string[] args)
       {
           var CS = "Server=XXXXX;User=system;Password=sys;";
           
           var C = new InterSystems.Data.CacheClient.

Hello, community.

I've been working with Intersystem Caché for two years, and right away I was excited about the rich ecosystem that Caché provides. However, I was disappointed with calls using #call, and I understand that it was a limitation of the time. Well, the frustration is that #call returns null by default, meaning an AJAX request is executed, but there's no hook to retrieve the return from that request. The only way to retrieve the data from that request is by building a callback on the server side using &js<>.

Hi Team,

We are currently running InterSystems Caché 2018 on an IBM AIX server and would like to configure the Cache instance to start automatically when the server boots or is rebooted.

Could you please provide the recommended steps or any official scripts/guidelines to enable auto-start for the Cache instance (QA2018) on AIX?

Additionally, if there are any best practices or prerequisites (such as filesystem mount options, service dependencies, or startup order) that we should consider, please share those as well.

Thanks,
Ganesh

We didn't start with a big AI strategy.

We had a legacy InterSystems Caché 2018 application, a lot of old business logic, and a practical need: build a new UI and improve code that had been running for years. At first, I thought an AI coding agent would help only with a small part of the work. Maybe some boilerplate, some REST work around the system, and a bit of help reading old ObjectScript.

In practice, it became much more than that.

Motivation

Why do we need this?

1. Lack of Compiled Context: AI tools only see source code; they don't know what the final compiled routine looks like.

2. Macro Hallucination: Because AI doesn't see our #include files or system macros, it often makes them up, wasting time during debugging.

3. The Documentation Gap: Deep logic optimization often requires understanding internal macros that aren't fully covered in public documentation.

4. Manual Overhead: Currently, the only way to fix this is to manually use the IRIS VS Code extension to find the "truth" in the routine.

For software engineers and data architects evaluating data platforms for risk and compliance consolidation in financial services.

Overview

Financial institutions typically run separate applications for risk management and regulatory compliance, creating fragmented data landscapes that are difficult to query and expensive to maintain. InterSystems IRIS is a distributed HTAP data platform that allows organizations to consolidate these systems onto a single, unified data layer.

Working with files often starts off simple. open the file, read, and process. That approach works perfectly well, until the file happens to be an Excel file.

A Common Assumption

At first, an Excel file (.xlsx) looks like just another data file, rows, columns and values. nothing unusual. So it's natural to assume it can be read the same way as a .txt ot .csv file. But that's where things start to break.

Why Excel files behave differently

The key difference is how the data is stored:

-> .txt / .csv - plain text, line-by-line.

-> .

My team is trying to decide on the best Git strategy for a group of related but separate projects/environments.

One side prefers one repo per project/environment/namespace for cleaner separation. The other side prefers one repo with multiple project folders so shared code and releases are easier to manage in one place.

The challenge is that these projects are separate enough that boundaries matter but related enough that some utilities and common logic may need to be reused. We also want the setup to be easy for developers to understand and not become a deployment nightmare later.

I have created the following Task to kick off a Ens.BusinessService to execute a SQL query and process the results

Class OSU.Workday.TerminationsTask Extends %SYS.Task.Definition
{

Parameter TaskName As STRING = "OSU - Workday Termination Update";

Method OnTask() As %Status
{
    #Dim sc as %Status
    #Dim ex as %Exception.AbstractException
    
    set sc = $$$OK

    try{
        // create the service
        #Dim tService As OSU.DataSource.Workday.TermService
        Set tServiceConfigName = "OSU.DataSource.Workday.