%Stream.GlobalCharacter properties in InterSystems IRIS are projected as LONGVARCHAR (-1) for JDBC. This complies with the default mapping, and the JDBC specification applies the maximum length limit for LONGVARCHAR, which may not suit arbitrary stream data requirements.

To utilize CLOBs adequately, the JDBC standard interfaces provide BLOB and CLOB handling. For instance, you can retrieve and set CLOB data within a Java program utilizing the java.sql.Clob interface:

Statement st = conn.createStatement();
ResultSet rs = st.executeQuery("SELECT MyCLOBColumn FROM MyTable");
rs.next(); // Access the Clob data
java.sql.Clob clob = rs.getClob(1);
// Example to print length
System.out.println("Clob length = " + clob.length());
// Perform further operations
clob.free(); // Close explicitly

This demonstrates the correct interaction between Java and CLOB stream data types in IRIS. Ensure that your implementation explicitly opens and manages stream field attributes to prevent constraints like JDBC defaults on LONGVARCHAR types from becoming limiting. [1]

Sources:

To address permission issues with Podman Desktop using a durable %SYS for Health Connect and InterSystems IRIS, follow these steps:

1. Ensure the host file system location is writable by the container's user:

   • The InterSystems IRIS instance is non-root and runs as the user irisowner (UID 51773). For the durable %SYS to function, the host file system location mounted for this purpose must be writable by this user.
   • Run the following command before starting the container:

     podman unshare chown 51773:51773 $INSTANCEDIR
     

     Replace $INSTANCEDIR with the location on the host where the durable %SYS directory is intended to exist.

2. Handle SELinux (if applicable):

   • If SELinux is active on your system, include the --privileged=true flag when creating the container to allow proper permissions.

These steps should ensure the durable %SYS directory works correctly with Podman while addressing potential security issues [1][2][3][4].

Sources:

To configure the system to send an ACK in response to every ENQ when using the ASTM protocol with a TCP service and inbound adapter, the "Get Reply" setting is relevant. By default, the "Get Reply" option is set to true, enabling the system to expect an ACK reply from the external ASTM system. However, if the external system does not provide an ACK reply or when continuous acknowledgment is required, this option can be cleared. Clearing "Get Reply" allows the ASTM TCP business service to not depend on receiving the external ACK reply [1].

Additionally, the "Response Timeout" setting specifies how long the service will wait for a reply before considering a response incomplete. Adjusting this setting may help in avoiding premature disconnection due to timeout, which could influence acknowledgment handling in the communication process. Setting the timeout to -1 ensures the service waits indefinitely for a response [2].

Sources: