The error you are encountering, SSL23_GET_SERVER_HELLO:unsupported protocol, often indicates that the SSL/TLS configuration being used is attempting to negotiate an unsupported SSL/TLS version for the connection. This can occur if a server supports a newer protocol like TLS 1.3 and your implementation is limited to older versions like SSL 3.0 or TLS 1.2.

Here are some troubleshooting steps and points of consideration based on the documents:

1. Update SSL/TLS Configuration:

   • Ensure your SSLConfiguration in the %Net.HttpRequest object is correctly configured to use the protocols supported by the server. For example:
     objectscript
Set request = ##class(%Net.HttpRequest).%New()
Set request.SSLConfiguration = "groundca"
Set request.Server = "osrd.atlassian.net"
Set request.Https = 1
Set tSc = request.Get("/rest/api/2/issue/<issue-name>")
     You may need to verify that the SSL/TLS configuration named groundca supports the correct set of protocols (e.g., TLS 1.2 or TLS 1.3) [1][2].

2. Enable Supported TLS Versions:

   • If the error is due to protocol mismatch, check whether your Caché system supports the required protocols. Older versions of Caché may not support TLS 1.3, as indicated in some discussions around outdated versions [3][4]. If upgrading to a newer version is not currently an option, you could use an external tool like Stunnel in client mode to handle the TLS encryption [3].

3. Verify Server Certificate and SNI:

   • If the server uses Server Name Indication (SNI), your configuration might need to explicitly include the SNI name. Some versions of Caché do not support SNI, and you may need a workaround for older setups [5]. For instance:
     objectscript
Set request = ##class(%Net.HttpRequest).%New()
Set request.SSLCheckServerIdentity = 0

4. Troubleshoot Using curl:

   • Since Curl successfully connects using TLS 1.3, it confirms that the server and API key are working as expected. Compare Curl's configurations (e.g., certificates, protocols used) with your Caché setup to identify discrepancies [1].

5. Certificate Matching:

   • Ensure the server name matches the values in its SSL certificate. Sometimes mismatches arise from redirects or incorrect configuration, which can result in an SSL handshake failure [1][5].

If these steps do not resolve the issue, further analysis of the environment and possibly server-side requirements may be needed. It's also advisable to consider upgrading Caché or alternative methods to establish newer protocol support. [1][5][3][4]

Sources:

Here is a programmatic solution to list all defined namespaces and their databases using both ObjectScript and Python:

ObjectScript Code

ClassMethod ListNamespacesAndDatabases()
{
    // List all defined namespaces
    Set namespaces = ##class(%SYS.Namespace).ListAll(.result)
    zwrite result

    // For each namespace, get its associated databases
    For i = 1:1:result.Count() {
        Set nsName = result.GetAt(i)
        Write "Namespace: ", nsName, !
        Set dbs = ##class(%SYS.Namespace).Databases(nsName, .dbInfo)
        zwrite dbInfo
    }
}

This code lists namespaces and retrieves their database configurations using the appropriate methods provided by the %SYS.Namespace class [1][2].

Python Code

To do this in Python, you need to work within the context of an InterSystems IRIS Python environment.

import iris

def list_namespaces_and_databases():
    result = []
    # List all namespaces
    namespaces = iris.cls('%SYS.Namespace').ListAll()
    for ns in namespaces:
        databases = iris.cls('%SYS.Namespace').Databases(ns)
        db_info = {key: value for key, value in databases.items()}
        result.append({'namespace': ns, 'databases': db_info})

    return result

# Usage
namespaces_and_databases = list_namespaces_and_databases()
for item in namespaces_and_databases:
    print(f"Namespace: {item['namespace']}")
    for db, info in item['databases'].items():
        print(f" Database: {db}, Info: {info}")

This Python example uses the iris module to interact with the InterSystems IRIS system. It retrieves both the namespaces and their associated databases using the same functionalities as ObjectScript [1][3].

These code snippets allow you to programmatically list namespaces and their databases from InterSystems IRIS. Let me know if you need further clarification or assistance!

Sources:

You may encounter the error Failed to save 'Utils.cls': Unable to write file 'isfs://mip:mz/API/Utils.cls?project=MZ' (Unknown (FileSystemError): Unknown Error) when trying to save or compile a class in Visual Studio Code due to several potential reasons.

Here are some troubleshooting steps based on relevant information:

1. Do Not Alter First Line of New Files: If you are creating a new file in the Explorer tree in VS Code and modify or delete the first automatically generated line after naming the file (e.g., foo.cls), it may cause issues saving the file. Always start coding on the second line and retain the first untouched [1].

2. Namespace and Server Connection Issues: Ensure your connection to the server is functional:

   • Check if you have configured the namespace and server connection properly in VS Code.
   • Use PuTTY or the browser-based management portal to verify connectivity to the server and test your file import or routine executions, as they should work without errors if connectivity is valid [1].

3. Correct Permissions: Make sure that the user configured for your VS Code ObjectScript plugin has the necessary privileges to write to the namespace or specific filesystems in InterSystems IRIS.

4. VS Code Plugin Setup: Ensure the required InterSystems ObjectScript extensions, such as the ObjectScript Extension Pack and Server Manager, are installed and properly configured [1].

If this doesn't resolve the problem, it may be useful to look at the server logs or other error details in the Audit Trail (%SYS.Audit) to get more information.

Sources:

I can’t find the information you’re looking for. If you rephrase your question, I might be able to help. You can also explore the following resources:

• "Extend Your Web Server Configuration with the Web Gateway" [1]
• "Web Gateway Registry in InterSystems IRIS" [2]
• "The Web Gateway: Serve InterSystems Web Applications and REST APIs to a Web Client" [3].
  

Sources:

To pass a string to a routine from PowerShell, you can use a syntax similar to the following example:

call: irissession healthconnect -U user 'Say^ImplUtil("Your String Here")'

In ObjectScript, to call a routine with an argument, you use the caret symbol (^) followed by the routine name, then the method with the argument in parentheses as shown in this syntax:

DO Say^ImplUtil(argument)

Here, argument can be a string such as "hello, I'm the ROUTINE" enclosed in quotation marks. This ensures the argument is passed correctly as a string [1].

Sources:

The syntax issue with your line set gn=$name(..#GlobalName) likely stems from the improper use of # and the .. syntax to reference the Parameter value stored in your class. The $NAME function in ObjectScript returns the canonical name value of a variable or portion of a subscript reference. However, it works correctly only with properly defined references [1].

To resolve your problem:
1. Ensure that GlobalName is correctly defined in your class as a Parameter so it can be referenced.
2. When calling $NAME, use proper syntax for object property or parameter references. If GlobalName is a class parameter, replace ..#GlobalName with the evaluated value or other valid syntax that provides the global name string to $NAME.

The $NAME function returns a canonical name of a variable or subscripted reference, allowing you to subsequently use the @ indirection operator on the resulting string [1][2]. Here's a simplified example:

set gn=$name(^AGlobal)
set @gn@("index")="value"

Make sure ^AGlobal corresponds to the actual global structure you intend to modify or reference [1][2]. If rephrased, or if a specific class definition is missing, additional context might be required.

Sources:

During the installation of InterSystems IRIS 2025.1, the InterSystems IRIS launcher icon typically appears in the system tray dimmed, signifying no active IRIS server. When the launcher yields no response upon right-clicking, it might indicate incomplete installation configurations or server connection issues.

To address the issue:
1. Verify that the installation completed successfully and review the options you selected during setup. Ensure the icon is not dimmed due to the IRIS server not running [1][2].
2. If it remains unresponsive, check whether a preferred server has been specified for the client, as this is mandatory for its functionality [1].
3. Post-installation steps should ensure the IRIS starts automatically and the launcher icon is functional in the system tray. If this didn't happen, continuing with the post-installation guide could resolve the problem [2].

Sources: