[Mark Brown]

This is happening in production. About the time this started happening we had gone live with a system called Ignite. it creates a huge alias in PID:3 that exceeds the HL7 spec for length . They provided a script to truncate this field.  We hadn’t installed it. But now we did and it has no impact.  Infor support has no idea what could cause it

[Mark Brown]

Color me embarrassed.  A TCL proc was failing.  It’s fixed now. Thanks for pointing out what to look for.

[Mark Brown]

This just got strange. I know I probably committed some kind of sin for doing this, but I wrote the XLATE on our test engine which is 6.2. I decided to create the XLATE on our production system which is still 6.0. It didn’t work either. I found an error in the variant I created.  I fixed that. Still didn’t work.  I then spent time deleting, re-adding, changing the XLATE around until I got it back to how it was originally.  And now it works.  The XLATE is identical to what is on 6.2 and it originally didn’t work, but  now it does.  I used the same file for test input in both cases.

I’m more worried than happy it’s working now.

[Mark Brown]

Thanks for the help.  That worked concatenating the iteration variable with the control id.  Sadly, it didn’t fix the problem. At least I know how to do this now.  🙂

[Mark Brown]

Making EVN optional did the trick.

Thanks!

[Mark Brown]

Thanks for the replies.  I need to digest that.  But I have a related question. I’ve looked in the documentation, but I don’t see anything.

On our current production system (Windows, CL 6.0) we use vbscripts to do a lot of maintenance chores. Some of these things, like cycle saving no longer work with CL6.2.  I also tried clicking on “cycle save” (right click on thread, click on control, click on full, click on cycle save) and nothing seemed to happen.

Is there still such a thing as cycle save?

[Mark Brown]

What’s odd is that on some procs, I’ve had to change the proc name (inside the proc) to all lower case to not get an error.

[Mark Brown]

Thanks!

[Mark Brown]

The errors are occurring with an outbound thread.

[Mark Brown]

I agree that fixing it at the source would be the best solution, but that doesn’t seem to be happening.

I think I’ll go with the option of the intermediate local host thread. That seems to be least amount of headache.

Thanks for all your replies.

[Mark Brown]

That did the trick!

Thanks!

[Mark Brown]

Thanks…

I’m snow blind now…

Seriously, I really don’t much care for that either.  I don’t care for the flat, colorless GUI’s that every software company thinks is hot at the moment anyway.

[Mark Brown]

Can someone post a screen shot of the GUI?

[Mark Brown]

Here it is.  Is “curdetail” the severity?

xpmerror $xlateId curdetail “Patient was not assigned to a bed. Cancelling Translation!”

[Mark Brown]

I don’t see a severity being set anywhere.

[Author]

Replies