[Jeff Dawson]

Hi Robert,

That’s odd, we’ve met  with Infor recently as we still run on prim and one of my first questions was what’s your biggest client running on your cloud solution;

What is their biggest customer, how many messages per day?  4 or 5 customers 10million, 1 in northwest 40million, Texas around 30-40million. 1 message in split out to 10 messages, Infor counts as 10 messages.  Also an ADT message is calculated differently for a CDA or embedded pdf which is weighted differently.  Unlimited threads, messages per day is tracked which does track against hardware/processing that used per what level you are in message volume wise.

[Jeff Dawson]

Jason summed up basically what our team has felt over the 20+ years of running Cloverleaf.  Love the product, extremely powerful, but severely lacking in updated documentation and examples compared to other competitors.  Appreciate the Clovertech community and its a great place for ideas or to ask questions but with the price tag that comes with Cloveleaf there’s been a need for these types of improvements by Infor instead of focusing on tasks like white washing their product.  With the amount we pay yearly for maintenance I’ve started opening tickets with Infor support on some of these questions along with fighting a few bugs on CIS 2022.09.03.   Due to the lack of or out of date documentation in the past I’ve opened up Infor cases sometimes you get helpful individuals other times we’ve gotten you will need Infor’s consulting services which requires a fee to assist.  These requests are not hey Infor do this whole vendor implementation project, that type of reply is extremely frustrating when one of the main competitors support is extremely helpful.  Webservices, CAAWS, and even their  sample sites are something I really hope they will eventually improve on as well.  The CAAWS user manual on CIS 6.2.6.1 was not much help and it looks very similar on CIS 2022.   All I’ve stated here is feed back we have consistently provided our account rep.  Love Cloverleaf and running it on a solid O/S feel like there’s a lot of quality of life improvements they could be making and have been missing the boat the past few years.

[Jeff Dawson]

Thanks Jason for the location where that library is called out in the online help, I made the mistake to search by the actual function name, where it looks like NCI pointed me in the right direction.  Slims pickings regarding the info in the document and even the correct usage if someone new wanted to try and get this working.  Its another item we always bring up with our Infor Site Customer Rep, can Infor invest in providing documentation that is update to date and accurate?  Love the Clovertech community and ideas/questions presented here but the price tag that comes along with Cloverleaf the expectation would be better.  This confirms there’s no write utility and will continue with what I currently do.

[Jeff Dawson]

One other interesting note I was able to to use the export MAXDATA command from my first post and set the process to 1GB.  I was then able to use a tcl proc in the tps inbound stack to check the message size and if greater than 50mB copy OBX-5.1 to OBX-5.5 then set OBX-2 equals to “LARGEPDF”.  In the xlate I added an If clause around the OBX-5.1 to OBX-5.5 to skip the copy command.  The xlate does use a pathcopy on the OBX segment which when deactivating the OBX-5.1 to OBX-5.5 copy statement still allowed the message to cross.  This made me realize how much memory allocation the XPM engine requires when using a copy statement.  Just to reiterate support mentioned since increasing MAXDATA above 3GB still did not allow the xlate OBX-5.1 to OBX-5.5 to work they suggested to offload the pdf locally (local disc storage) before the xlate and then add it back to the message after the xlate in the Outbound tab TPS outbound data stack.

• This reply was modified 2 months ago by Jeff Dawson.
• This reply was modified 2 months ago by Jeff Dawson.

[Jeff Dawson]

We came across this issue again running CIS 2022.09.03 on AIX 7.2 TL 5, 75MB pdf caused an unalloc error.   Support confirmed the engine on version 2025.01.01 will be migrated to 64 bit and hopefully this issue will no longer persist.  Received an update in KB2293813 where the release notes were linked in excel spreadsheet Cloverleaf_Integration_Services_Release_Report_2025.01.02_OP

Migrate AIX engine to 64-bit runtime – Cloverleaf AIX 64-bit support (CISCL-10294)

 

<td width=”525″>1. IBM XL C/C++ Runtime environment package 16.1 for AIX is required to support Cloverleaf AIX 64-bit executables. Please refer to [https://www.ibm.com/support/pages/ibm-xl-cc-runtime-aix-161|https://www.ibm.com/support/pages/ibm-xl-cc-runtime-aix-161] for more details.
2. EXTSHM shall NOT be set in the environment, like in .cshrc file for tcsh or /etc/environment.
3. Disable AIX Large Program Support, remove MAXDATA setting in the environment variable LDR_CNTRL or do not ldedit Cloverleaf executables again. [https://www.ibm.com/docs/en/aix/7.3?topic=concepts-large-program-support|https://www.ibm.com/docs/en/aix/7.3?topic=concepts-large-program-support]

[Jeff Dawson]

Great topic of discussion.  On our side we try to filter using TCL similar to what Rob stated this dates back to hardware performance and Infor’s recommendation and best practices.  It would be nice with the new CIS versions being released if Infor would release a new updated best practices document.   Appreciate Jim’s feed back regarding chaining xlates as it’s another option I’ve never given much thought to regarding filtering but could see it being beneficial for clients with limited experience.

[Jeff Dawson]

Thanks Tim all this information is extremely helpful and very promising to see Cloverleaf is having no throughput issues with that amount of device volume per day you provided.  Also appreciate the NetConfig screen shot, it did come through and is viewable.

[Jeff Dawson]

Extremely helpful information David, greatly appreciate all the feed back!

[Jeff Dawson]

I was told by support there is no options feature to keep this enabled, hopefully this will be added as a feature enhancement.

[Jeff Dawson]

Hi David,

We are on CIS 2022.09.03 and I had opened a ticket with Infor regarding this as well

 

Update from Infor unfortuantely no date of resolution for this so depending on where the tcl proc is created you would need to do the following:

 

1. Tcl proc created from script editor, after saving proc NetConfig would have be closed and reopened.
2. Tcl proc created from Text editor, after saving proc and running mktclindex entire IDE (CIS GUI) would have be closed and reopened for new tcl proc to be available.

 

“CISCL-10409 created for tracking fix for this to be added in a future patch. I have heard back from development. This had been reported to development already and what we call a product Jira to track correcting and will be in a future patch. To see if this specific problem is in a specific patch search for CISCL-10409. I do not have a date for when it will be patched at this time.”

• This reply was modified 1 year, 2 months ago by Jeff Dawson.

[Jeff Dawson]

Pretty frustrating the hoops you have to now jump through just to get release notes and changes for new versions.  It use to be released with the new versions in the download center now it’s placed in some excel spreadsheet with a bunch of other stuff that you have to search for the version CIS version number for any hits as a KB I think.  No clue why Infor would think this is a better way of handling this for their customers.   If anyone has issues finding this information I would suggest opening a ticket with Infor support.

• This reply was modified 1 year, 9 months ago by Jeff Dawson.

[Jeff Dawson]

Enjoy retirement Rob, appreciate all you have done!

[Jeff Dawson]

Hi Jeff,

We came across a similar issue regarding read timeout errors on a few of our inbound threads due to message size of base64 encoded pdf’s, we ended up having to adjust the timeout setting to higher value besides the default of 30.   This might be something to adjust on your side and see if it helps, for some of our systems we upped this to 300.  We also came across another issue where the HL7 message was just to large in general to receive but Infor support confirmed this is an AIX problem only apparently.

• This reply was modified 1 year, 11 months ago by Jeff Dawson.

Attachments:

You must be logged in to view attached files.

[Jeff Dawson]

Hi Tim ,

We are running the same version of AIX, 7.2, talking with our AIX admins they are stating the same thing that AIX appears to be 64bit enabled yet hciengine is only 32bit.  I’ve taken this back to Infor support and they are asking the developers about this.    I’m hoping at some point CIS will be able to run at 64bit however it was explained to me the limitation is on the AIX which doesn’t seem to be the case with the what I’m finding out however there may be other factors involved that Infor’s developers may clarify regarding AIX.  Will post what I find out and I also attached the document that Infor provided regarding this issue.

• This reply was modified 2 years ago by Jeff Dawson.

Attachments:

You must be logged in to view attached files.

[Jeff Dawson]

You could echo variable backupCmd out the contents of the command like the .help but if you wanted to trap an error there’s a few ways this could be accomplished with the tcl catch command.

set rc [catch {set backupCmd [exec sqlite $dbFile < $batchFileName]} error]
echo “rc $rc”
echo “error $error”

I updated the spelling of the dot command so it would fail:

rc 1
error Error: unknown command or invalid arguments: “b”. Enter “.help” for help

Then updated the backup command and ran it successfully:

rc 0
error

Another way would be to wrap the catch with an If statement and forgo the set rc (return code) command.

• This reply was modified 2 years, 1 month ago by Jeff Dawson.

[Author]

Replies