[Mike Campbell]

A brief follow-up.  This is mainly to those new to utilizing the jdbc process to query external databases.  I won’t go through setting up the jdbc ‘tables’ used but rather on how to handle errors.

Cloverleaf – 19.1.2.2

We discovered that if there was a connection error, information would be written to the .err and/or .log.  Nothing real-time was sent stating an error occurred.  The message would still be sent, however the information might be missing or incorrect if based on the query result.

To remedy that we created an email tcl proc to check the built-in jdbc error flag of @tbl_errno.  0 [zero] is successful.  -1 is an error condition.  Greater than 0 means multiple rows were returned.  So, if -1, we generate an email stating the error, with information needed for research, etc.  We also created a tclproc to send the mesasge to the error database, and suppress it from being sent out.

The error database tcl uses:  xpmerror xpmId severity message – to do the work.  Fairly easy to work with.

 

[Mike Campbell]

With some expert help and guidance from Jim Kosloskey, I was able to get the xpmerror to work and send the message to the error database.

Thanks all!

[Mike Campbell]

Thanks Debbie.  That would be great.

mike.campbell@nmhs.org

[Mike Campbell]

Linux to Unix transfer.  So Windows is out of the picture.

[Mike Campbell]

Well, here is the answer from Infor support:

   We changed how we handled subcomponents in 6.0, then rolled it back in 6.0.1.

   

   So that’s why you did not see it in 6.0 but you did in 6.0.2…

   

What the details or inner reasons why I do not know…but it seems it was by design.

Also I checked the 6.0.2 release notes and noticed that it’s stated in there as well.

“Rollback changes causes copying HL7 subcomponents behavior change (9548)”

Must have missed that comment in the release notes.

[Mike Campbell]

I would agree with the comment Jim, except I applied the patch several months earlier and encountered the same problem, and backed it out until I could research what needed to change in the Xlates.  

We also had an instance where information in the OBX-5 was passing okay in the 6.0 version, but the embedded ‘&’ started causing issues with the patch.  Luckily we know a quick workaround for the ampersand mapping.

[Mike Campbell]

Thanks Rob.  Appreciate the examples.

[Mike Campbell]

Thanks Justin.  Really was trying to discover the best practices and the easiest way to get it set up.  Good information in you replay.  I’ll bookmark it and ask away as I get things going.  

Mike C.

[Mike Campbell]

What I did to make this work:

I added this to the script prior to the site specific processing needed:

setroot -clear

setroot /quovadx/cis6.0/integrator your_site_here

Then after processing, I reset to the site needed:

setroot -clear

setroot /quovadx/cis6.0/integrator your_primary_site

Seems to be working just fine.

[Mike Campbell]

Turned out James C. was correct after all.

I looked in one place that had the HL7 defined, but not the correct one.

So…limping for a while after the self-inflected shot-to-the-foot.   😳

[Mike Campbell]

Thanks for the replies all.  I’ve checked and double checked all those things mentioned.  I finally bit the bullet and opened a point with Infor support. So far, they are at a loss as to what the issue is.  I’ll post when we get it figured out.

[Mike Campbell]

I’ve checked that, re-copying and re-entering it.

It’s the same as production.  And yes, the wild card box is checked.   🙂

[Mike Campbell]

I do like the TCP/IP thread pair idea.  

So, on the SOURCE side, I am getting messages into the thread, and wanting to send those to the DESTINATION side.  

My guess is I would use a RAW static_route configuration.

If correct, how do I get the DESTINATION [in a different site] to show up to connect to?

[Mike Campbell]

Might have to give you a call early next week.

Unless you can briefly explain what “OVER” looks like.

[Mike Campbell]

Thanks Jim.  I AM using the Cloverleaf inter-site routing, or at least I’m trying to.

[Author]

Replies