[Kevin Kiplinger]

“ClnMgrToVXU” is required in your eLink if you are going to pull the Immunization messages out of SCM. It takes care of getting most of the extra message info needed for submission to your state. A good reference SCM v5.5 document for this is in Allscripts Client Support Portal    Article 000027201/KA007453  (attachment in the article), but you will want to get the ClnMgrToVXU Translator that is current to your patch level.  You setup a second translator in your eLink to watch the queue from ClnMgrToVXU and send it to Cloverleaf.

[Kevin Kiplinger]

I ran across this( Thread 1 ( adt_xlate ) received signal 11 PC = 0xffffffff PANIC: “0” PANIC: Calling “pti” for thread adt_cmd) error while doing my regression testing for upgrading Cloverleaf 5.6 rev2 on AIX  to 6.0 on RHEL 6.1.   The entire process and all the threads would just go down.  Turns out it was a problem in an XLATE that had an incorrect iteration mapping.  Inbound version was a repeating segment, outbound version was a repeating group with non-repeating segment:

INCORRECT PATHCOPY MAPPING    0(0).PR1(%s1)   ->    1(0).0(0).PR1(%s1)

CORRECT    PATHCOPY MAPPING    0(0).PR1(%s1)   ->    1(0).0(%s1).PR1(0)    

Seems that CL 5.6 rev2 on AIX  was a more fault tolerant of incorrect XLATE iteration mapping in this instance.

[Author]

Replies