[Henry Bauer]

We are attempting Multi-Server with a connection from EPIC to Cloverleaf, the current hl7Raw_ack.tcl contains:

# For multiserver

           msgmetaset $obMsg DRIVERCTL [msgmetaget $mh DRIVERCTL]

           if {[string equal $ackSubs::ackType “AA”]} {

               return “{CONTINUE $mh} {OVER $obMsg}”

           }

I have seen posts referring to needing to have this code:

set ackmsgDriverCtl [msgmetaget $mh DRIVERCTL]

 msgmetaset $ackmh DRIVERCTL $ackmsgDriverCtl

Is this additional code that needs to be added to the native hl7Raw_ack.tcl or an updated version of the hl7Raw_ack.tcl

[Henry Bauer]

Worked like a charm

[Henry Bauer]

I found an old example I had of a regexp that worked, not what I wanted, I will work on your example.

Thank you!

Been searching online too.

[Henry Bauer]

Thanks for the response Robert, I have read all the posts on this issue including yours and going forward we have resolved the problem using this setup.

[Henry Bauer]

Found the script.

[Henry Bauer]

set v1 “\”

           set path1 “thpftransagt1”

           set path2 “bdi_epiphany”

           set path3 “filedrop”

           

           #Get fields for amending or validation

           #This will replace a field in one segment of several OBX segments if

           #the proper context is found

            foreach obx [ lsearch -all -regexp $segmentList {^OBX} ] {

                 set obxFlds [split [lindex $segmentList $obx] $fs]

                 set obx2 [lindex $obxFlds 2]

                 set obx5 [lindex $obxFlds 5]

                 if {[string eq $obx2 “TX”]} {

                      append v1 $v1 $path1 $v1 $path2 $v1 $path3 $v1 $obx5      

            ;#This allows you to build a relative path to a file and insert it into the HL7                                                            

            ;#message. ie \thpftransagt1bdi_epiphanyfiledrop$obx5

                      lset obxFlds 5 $v1                                    

            ;#Replace the existing OBX field 5 with the new value.

                      lset segmentList $obx [join $obxFlds $fs]                                            

            ;#Replace the existing OBX segment with the amended OBX segment.

                     }          

             }

[Henry Bauer]

Thanks for the response Jim I did not consider that. I appreciate the input.

[Henry Bauer]

the user is just TEST

[Henry Bauer]

Found this information hope it helps:

UNIX

lmclear -u TEST -mp

On Unix it is easier to recover from this command.  No need to stop or shut down anything.

WINDOWS

This error is less forgiving on Windows systems.  To clear you must shut down all sites and stop the QDX 5.x service in the control panel.  Once the service is down you should perform a site cleanup.

[Henry Bauer]

if you are trying to fix the error database use

keybuild elog

dchain elog

Sorry this was my mistake in not defining the commands for recovery and error databases.

[Henry Bauer]

When this occurs running the command hcidbdump -e/-r produces the following error response from the Cloverleaf command line:

    Database error -920, system error 944

When this occurs the database must be reindexed.

The following steps must be performed

  1. All processes must be stopped. If the gui is non responsive to the stop process command try using the hcienginestop -p adt command for each process.

      If the command is slow in processing and time is essential you can cd to the site process level ie; cd $HCISITEDIR/exec/processes, then run the command

      cat ./*/pid this will produce a listing of all pids associated with the processes of the site in question, you will need to then run the command kill -9 ######### for

      each pid number listed.

  2. Run the command hciprocstatus to insure all process have been stopped.

  3. Run the cd command to take you up one level in the site ie; cd ..(two periods will set you in the $HCISITEDIR/exec directory).

  4. Run the command hcisitectl -K to stop the Lockmanager and Monitord Daemons

  5. Remove the monitorShmemFile ie; rm monitorShmemFile.

  6. cd to the databases directory ie; cd databases, this will place you here $HCISITEDIR/exec/databases.

  7. Run the command hcisitectl -S to start the Lockmanager and Monitord Daemons.

  8. Run the command hcidbinit -i, this will remove the index for the databases.

  9. Run the command keybuild rlog.

  10. Run the command dchain rlog.

When this steps are done the recovery database should be reindexed and accessible, run the hcidbdump -r command to verify success. At this point if there are no errors noted by the system with these commands the processes can then be restarted.

[Henry Bauer]

Found information on the hcidbdump, just being a little fuzzy this morning.

[Henry Bauer]

Also have hcitpstest running:

32702738 hci        0   0   27M   26M  run 45+00:51 85.3/92.3 hcitpstest

As I said I believe these PID’s can be killed, just wondering if there may be any ill affects to the system while site is up and running.

[Henry Bauer]

This reminded me of an issue I have dealt with before where you are sending what appears to be a valid transaction and getting a invalid Trxid response. Since this is sending to a database I wonder if at that moment the record it is trying to access is currently locked and unable to process the transaction at that time and inadvertantly giving the wrong response “Invalid Trxid”. Perhaps there could be a way to work around this error.

[Henry Bauer]

Is that the only log file that large? Are there other log files of that size or larger that might be overwhelming the system. Do you have Log file cycling set up, max number of files and max size of files? Is it just this process crashing? Can you deleete the log file or save it off to your pc and analyze it. Just some thoughts.

[Author]

Replies