@jeff-dawson
Forum Replies Created
-
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.
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:
- Tcl proc created from script editor, after saving proc NetConfig would have be closed and reopened.
- 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.”
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.
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.
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.
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 helpThen updated the backup command and ran it successfully:
rc 0
errorAnother way would be to wrap the catch with an If statement and forgo the set rc (return code) command.
Hi Jim,
I’ve done something like this in the past to issue the sqlite dot commands via tcl. There may be an easier way but I know this does work.
#!/usr/bin/env tcl
global hciRoot
global hciSite
global siteDirset hciRoot $env(HCIROOT)
set hciSite $env(HCISITE)
set siteDir $env(HCISITEDIR)set dbFile “$hciRoot/sqlLiteDbs/ADT/EpicADT.db”
# create batch file of commands to backup sqlite db
set batchFileName “$hciRoot/sqlLiteDbs/ADT/EpicADTbatch.txt”
set batchFile [open $batchFileName w]
#puts $batchFile “.backup TEST.db”
#puts $batchFile “.help”
puts $batchFile “.backup TEST.db”
close $batchFile
set backupCmd [exec sqlite $dbFile < $batchFileName]
