Could these be opt-in Canals (Water-Channels) ?

Ref: Historic community reactions to less-formal posts / articles, where the expectation for work formality was not satisfied.

Ompare - Compare side-by-side multiple disconnected IRIS / Cache systems.
https://openexchange.intersystems.com/package/ompare
This was developed in order to compare environments on different networks. It works by profiling code and configuration, across one or more namespaces, generating a signatures and optional source file to be imported into the reporting service.

The SQL Profile capability is reused to provide comparison of integration production settings across environments.
It ignores non-functional differences in code like blank lines, method / line-label order. Useful for manual integration that has occurred in different order or with different comments.
It provides reporting to show side-by-side differences of the same namespaces across multiple instances.

Has been useful for assurance environment parity, for upgrade sign-off.

Article - Using Ompare to compare CPF configuration and Scheduled Tasks between IRIS instances
https://community.intersystems.com/post/using-ompare-compare-cpf-configuration-and-scheduled-tasks-between-iris-instances

I created a lighter no-install version to compare changes in releases of IRIS versions.
/Ompare-V8 see: https://openexchange.intersystems.com/package/Ompare-V8

Would making a deep clone immediately after first opening the object resolve this?

Class dc.Per Extends %Persistent{Property Color As %String;}

Test:

>s obj=##class(dc.Per).%New()
 
>s obj.Color="Red"
 
>w obj.%Save()
1
>kill obj
 
>s obj=##class(dc.Per).%OpenId(1)
 
>s objcopy=obj.%ConstructClone(1)
 
>w objcopy
2@dc.Per
>w obj
1@dc.Per

One approach that might be suitable is to have a look at overriding method OnFailureTimeout in the sub-class, which seems for this purpose.

Anticipate the ..FailureTimeout value will need to be more than 0 for OnFailureTimeout to be invoked.

Another area to review could be overriding OnGetReplyAction, to extend the retry vocabulary.

Voted

ClassMethod IsValid(s As %String) As %Boolean{    // Floats around them no good characters
    s s=$ZSTRIP(s,"*E","","()")
    // Erupts Combination jabs "(" followed by ")"
    // Relentless follow up until stringy looks unbalanced
    f {q:s'[("()") s s=$Replace(s,"()","")}
    // Swings for the knock out
    q s=""}

Hi Rathinakumar,

One reason may be process contention for same block.

Most application processes work by $Ordering forward from the top of the global down.

When doing table scans, this can results in processes waiting, or running behind another process.

As an alternative for Support and Large Reporting Jobs you can instead "$Order UP" instead.

s sub=$o(^YYY(sub),-1) q:sub=""

Interested if this may mitigate any performance issue caused by contention on a busy system.

Had similar: zn "%SYS" set svc=##class(Security.Services).%OpenId("%service_telnet") set svc.Enabled=1 do svc.%Save()

Note: Class documentation says DO NOT update with SQL. But can see / check settings in %SYS, with for example: SELECT * from Security.Services

set basename="Test.Sub.Base"
set file="c:\temp\subclasses.xml"

// Get list of compiled sub-classes
do $SYSTEM.OBJ.GetDependencies(basename,.out,"/subclasses=1")
// If you didn't want the base class
kill out(basename)

// Write the classes to terminal
zwrite out

// Suffix for export
set next="" for {set next=$Order(out(next)) quit:next=""  set toExport(next_".CLS")=""}
// Fire in the hole !!
do $SYSTEM.OBJ.Export(.toExport,file,"/diffexport")

// to display different qualifier flags and values used by various OBJ methods ( /diffexport ):
do $SYSTEM.OBJ.ShowQualifiers()

Another option have used is stunnel, on Linux variants (SUSE and RedHat).

Where Cache / IRIS connects to local proxy, which then connects via TLS to LDAP service.

Note: If running proxy in process jail, and find it can't get re-lookup of DNS after being started, ie dns lookup is once on start up. An approach is a mini-service script to monitor the DNS to IP resolution periodically, and auto-restart the stunnel proxy when it changes. One advantage being, if the DNS resolution service is temporarily unavailable, the running proxy carries on using the previously resolved IP address.

.

OK. Lets just do this already !!

This example uses Properties and Settings to expose the Request and Response Types so they are viewable from the Management Portal:

This is achieved with the following code:

Class Test.Operation Extends Ens.BusinessOperation{Parameter ADAPTER = "EnsLib.HTTP.OutboundAdapter";Property Adapter As EnsLib.HTTP.OutboundAdapter;Parameter INVOCATION = "Queue";Property RequestTypes As %String(MAXLEN = 4000) [ InitialExpression = {..GetRequestTypes()}, Transient ];Property ResponseTypes As %String(MAXLEN = 4000) [ InitialExpression = {..GetResponseTypes()}, Transient ];Parameter SETTINGS = "RequestTypes:Info,ResponseTypes:Info";ClassMethod GetRequestTypes(){  set ret=""  set messageTypes=..GetMessageList()  quit:messageTypes="" ret  for i=1:1:$LL(messageTypes) {    set ret=ret_$C(13,10)_$LI(messageTypes,i)  }  quit ret}ClassMethod GetResponseTypes(){  set ret=""  set messageTypes=..GetResponseClassList()  quit:messageTypes="" ret  for i=1:1:$LL(messageTypes) {    set ret=ret_$C(13,10)_$LI(messageTypes,i)  }  quit ret}XData MessageMap{<MapItems>  <MapItem MessageType="Ens.StringRequest">     <Method>DoOne</Method>  </MapItem>  <MapItem MessageType="EnsLib.HL7.Message">     <Method>DoTwo</Method>  </MapItem></MapItems>}Method DoOne(request As Ens.StringRequest, response As Ens.StringResponse){}Method DoTwo(request As EnsLib.HL7.Message, response As EnsLib.HL7.Message){}}

How it works.

The Getter methods populate the Properties (RequestTypes, ResponseTypes ) via InitialExpression

These Properties are exposed to the User Interface via the SETTINGS parameter

Note also I have set the MAXLEN of the properties over 2000K characters. This forces the Management Portal to render a TextArea instead of a single line Text input control.

The reuse pattern is to have this code in a class.

Then can add behavior via extends to inherit this behavior.

Class Test.NewOperation2 Extends (Ens.BusinessOperation, Test.Operation){Parameter INVOCATION = "Queue";}

IRIS is so flexible :)

Hi Doug,

Have you considered creating a new Rule FunctionSet.

This would then appear in as a new available function in Rule Editor when compiled.

For example:

Class Test.Fun Extends Ens.Rule.FunctionSet{ClassMethod SegmentFieldContains(pDocument As EnsLib.HL7.Message, segmentName = "", fieldNumber = 0, value As %String = ""){
  // validation
  quit:segmentName'?3AN 0  quit:fieldNumber<1 0  quit:value="" 0  set isFound=0  // get count of segments  set segCount=pDocument.GetValueAt("*")  // loop through all of the segments  for i=1:1:segCount {    set seg=pDocument.GetSegmentAt(i)    continue:'$IsObject(seg)    // skip wrong segment    continue:seg.GetValueAt(0)'=segmentName    // skip if field does not contain value    continue:seg.GetValueAt(fieldNumber)'[value    set isFound=1    quit  }  quit isFound}

}