Cloverleaf 6.1 hcixltconvert

[Keith McLeod]

If I am upgrading from Cloverleaf 5.7 and have run hcixltconvert, what do I need to restore to get back to before the hcixltconvert command ran?

formats?

xlates?

Anything else?

Topic

[Keith McLeod]

Receiving many of these messages in a route test.  Any ideas?

[tcl :out :INFO/0:  UNNAMED_TID:08/16/2014 11:10:38]

[Charlie Bursell]

Keith:

When you ran hcixltconvert it should have created a .bak file for each one converted.  Simply remove the .xlt files and rename the .bak files and you should get back to where you were

The error says it is trying to route to an un-named thread ID.  You usually get messages like that when there is something weird with the files, NetConfig, etc.

Have you checked your files and made sure you don’t have a bunch of embedded CR characters?

[Keith McLeod]

Charlie,

Thanks for the quick reply.  So only the Xlate files are impacted by hcixltconvert.  That would be a quick fix.

The UNNAMED_TID only shows on the route test in Cloverleaf 6.1 and not in the route test on Cloverelaf 5.7.  The output files appear to be identical when written to disk.  The NetConfigs survive hcinetcheck, etc….  The xlates run fine and point out warning such as formats are from the master site.  Could this just be extra noise from the 6.1 testing tool?

[Charlie Bursell]

I am not aware with hciroutetest problems with 6.1.  You may want to contact Support

[Keith McLeod]

The tcl callout apears to happen in route test whenever there is an echo or puts statement being used.  I am going to check to see if any eo_aliases are in use on these routes as a possibility….  I would have expected the same result in 5.7 vs 6.1 though…  After this I may put in a ticket.

[Troy Morton]

I noticed the same thing after upgrading from 5.6 to 6.0.2 and did not notice any affect on the output of messages either.  I think that UNNAMED_TID is simply Cloverleaf saying that the thread name in the message METADATA is empty.

[Max Drown (Infor)]

Troy Morton wrote:

I noticed the same thing after upgrading from 5.6 to 6.0.2 and did not notice any affect on the output of messages either.

-- Max Drown (Infor)

[Author]

Replies