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: