[Graham Hartley]

I have also recently started to see the same error repeatedly throughout the day….

[icl :icl :ERR /0:        DEBUG:01/10/2013 02:26:34] imhVerify failed at free 0x0489F6E8

[icl :icl :ERR /0:        DEBUG:01/10/2013 02:26:34] 0x0489F6E8 type is 5

Thankfully it isn’t crashing the engine but I would like to know what it means.

Any ideas?

Regards,

Graham

[Graham Hartley]

Thanks both,

Jim – I was hoping to use the same connection handle in both the IB and Xlate Pre Proc to save having to connect to the database again.  Currently we connect to the database in the IB startup so we can store the messages and execute various stored procedures.  I then hoped to use this same connection handle to access the database in the Pre Xlate.

As this dosen’t seem possible I think I will shelve the idea and maybe look at moving the code from the pre Xlate into the IB tps instead.  

Regards,

Graham

[Graham Hartley]

Hi,

I have been experimenting with namespaces to try and resolve this problem without success however I have learnt alot about namespaces!

The ultimate aim is to be able to store the database connection handle generated in the inbound TPS and reuse it in the Pre Xlate proc.

As I now know that the IB and Xlate thread run in different interpreters I thought I could share this handle using a namespace variable but I can

[Graham Hartley]

OK Thanks both.  I will look into using a separate namespace for the odbc variables and see how I get on.

Thanks again,

Graham

[Graham Hartley]

Thanks James for your comments however the thread used to process the message already has its encoding set to windows-1252 therefore I don

[Graham Hartley]

Thanks for the response.  Given it a try and it still dosen’t work I am afraid

[Graham Hartley]

Thanks for all your help on this.  In the end changing the thread so that it uses windows-1252 encoding seems to resolve the problems I have been experiencing.  

David

[Graham Hartley]

Thanks Boris,  I will give that a try and let you know how I get on.

[Graham Hartley]

Thanks for your suggestion. I have tried changing the encoding on the thread to various types including windows-1252 and this has no effect.  I note that in version 5.3 there is no encoding dropdown.  

Unfortunatly I think the issue may be quite a complex one to solve!

[Graham Hartley]

Thank you all for your help on this.

Jim – I have checked the Xlate and in 5.3 @gg1 was being used to address other repetitions apart from zero.

I have thankfully now managed to get it to work.  In the end I replaced @gg1 with $%g99 in all places apart from in the address path where I replaced it with %g99.  If anyone knows why I have to reference it differently then please let me know.

For example:

Code:

{ { OP ADD }
                                   { ERR 0 }
                                   { IN {$%g99 =1} }
                                   { OUT $%g99 }
                                   { FUNCTION ADD }
                               }

but in the address path I have to use %g99

Code:

{ { OP COPY }
                           { ERR 0 }
                           { IN =| }
                           { OUT {{SEG3(%g99).Record_Seperator.[0]}} }
                       }

Regards,

Graham

[Graham Hartley]

Thanks everybody for your help on this.  I will try out some of your suggestions and let you know how I get on.

Your help is much appreciated,

Regards,

Graham

[Graham Hartley]

Thanks Russ.  The files you suggested are re-created when the process is restarted.  The strange thing is that the logfile still gets cycled even though this error is returned.  I guess I can just carry on using the same command but just ignore the error.  However I would still like to know what causes it.

Regards,

Graham

[Graham Hartley]

Thanks for your suggestions thus far.  I havent tried the Automatic Log cycling yet.  However I would still like to know why the approach I am taking dosent always work.  The reason for taking this approach is that I would like to create a script to cycle the logs on a daily basis.

[Graham Hartley]

Thanks Tom.  That worked a treat.

[Graham Hartley]

Hi Tom,

Thanks for your quick reply.  I can add 1 to this variable but if I do this it skips over the 1st secondary procedure.  This is because the variable is used in the following..

{ IN SEG5(%s1).OPCS_Secondary_Intended_Procedure_Code }

{ OUT 0(0).PR1(%s1).00393 }

I think what I need is a different variable that I can reference in the OUTPUT so that %s1 iterates through SEG5 and another variable (which will be %s1 +1) populates the HL7 say PR1(newVariable).  However I am not sure if/how you can use multiple variables in an iterate.

Any more suggestions please?

[Author]

Replies