[Steve MacDonald]

We actually change them to the word ‘AND’.

regsub -all {&} [inbound msg] “and” [outbound msg]

[Steve MacDonald]

If you have the 5.5 Host Server running as well – You may need to run $ unset DISPLAY in the 5.8 Environment before running $ hciss -s h

We had this issue with 2 Host Servers running simultaneously as well.

Hope this helps.

[Steve MacDonald]

There is no way to tell how much disk you will end up using.  It depends on the number of saved message files in your 5.8 sites and the volume of messages they ‘save’.  The file system will simply continue to grow until the process that created the ‘open’ file is bounced.  

ON AIX 5.3.0.0

---

>

if you do a ps -ef | grep [hci_process] and retrieve the pid – you can then check all of the open files associated with that process.  

on AIX – lsof -p [pid]

those with the exclusive write lock ‘wW’ are the active .idx and .msg files.  those where the write lock is released, but the allocated memory is not have the lowercase ‘w’ only.

These are files ‘taking up disk’ but do not have a ‘file name’ when searched for:

COMMAND    PID    USER   FD   TYPE             DEVICE  SIZE/OFF  NODE  NAME                                                                                

hciengine 893054  hci   82w  VREG              103,2  1359387 16804 /sites8 (/dev/ie8_fs01)

hciengine 893054  hci   83w  VREG              103,2  1154241 16772 /sites8 (/dev/ie8_fs01)

hciengine 893054  hci   84w  VREG              103,2  3322464 16774 /sites8 (/dev/ie8_fs01)

hciengine 893054  hci   85w  VREG              103,2  5349123 16783 /sites8 (/dev/ie8_fs01)

[Steve MacDonald]

We are migrating from 5.5r1 to 5.8.  No major issues (knock on wood).

We did change all of our Reply Handling from the Recover_38.tcl procs to the default ‘Resend OB message’ within Timeout Handling.  We did find out that the Trx id on the Inbound replies does have to be set to HL7.  It didn’t seem to matter on 5.5.

We also had some Xlates to an FRL where we were using a temp variable as part of the OB name.  5.8 process would error on messages through this Xlate.  We had to Iterate using %f1 and use that instead.

On Global Monitor – The thread notes aren’t displaying yet.  That has a fix coming out in Rev 1 I am told…

I’ll be watching for other issues in 5.8.  We are migrating one engine at a time starting in November.

Thanks!

Steve MacDonald

Senior Technical Analyst

Trinity Health

[Steve MacDonald]

We are upgrading from 5.5r1 to 5.8 on AIX 5.3 Tech Level 9.  Some of the issues we have found so far……..

1)  When Bulk Copy or Path Copy is not used the outbound message will differ from 5.5 to 5.8.  In 5.5, the EVN is not optional so the first field is populated with Variant Message Type (eg. A01).  In 5.8 you will just receive the segment ID of EVN with no fields populated.

2) Using a temp variable in the outbound field pathname will not work in 5.8 as it did in 5.5.  The Temp variable will need to be changed to $%f#.

3) When running version 5.5 and 5.8 on the same AIX server, bouncing the 5.8 host server requires an ‘unset DISPLAY’ command before starting it back up.  Still checking on this one   😕

4) Outbound threads left with the default Auto-Reconnect setting of Reopen the connection every 10 seconds were filling up the logs fast (even with EO set to DISABLE_ALL).  I changed these to 7200 on our test connections.

5)  Global Monitor 4.0 ‘Notes’ do not show what was placed in the NetConfig Notes Tab.  I think the fix on this is coming out in the first rev patch though…

[Steve MacDonald]

We also plan to upgrade to 5.8…from 5.5 rev 1.

Those that have Beta Tested.  What did you notice with Variant differences?  Added fields?  Segments?  Other?

Thanks for your help!

Steve MacDonald

Systems Analyst

Trinity Health – TIS

[Author]

Replies