Questions about CL6.1

[Mark Brown]

I’m trying to deal with several issues with testing CL6.1

First, which are the correct procs to use for generating a reply and for validing a reply?

I’m also getting a “tcl callout error (302)” on proc that worked just fine in CL6.0.  it works just fine in the testing tool.  But I get this error when I’m trying to route a message through it.  It’s the only proc on that particular route.  The error just says:

Tcl error:

  msgId = message0

  proc    = ‘checkMPVORU’…’ error in ‘RAW’ under ‘ORU_R01’ to ‘obmpv’;

Previous recovery db state is 5.

Topic

[James Cobane]

Mark,

Regarding “which are the correct procs to use”, I would think that you would use whichever procs you are currently using under 6.0

As for the “call out error”, when you are running the testing tool are you running a ‘route test’ or simply running a ‘tps test’?  To truly test how it may behave when the message is run through the engine, you should run a ‘route test’.  It is possible that the proc is calling some additional procs/routines, et al, that didn’t get migrated to the 6.1 version from 6.0.

Hope this helps.

Jim Cobane

Henry Ford Health

[Lawney Lovell]

I am not sure if this is the same issue but we are in the process of testing 6.1.1 and ran into a problem with some of our old tclprocs that went missing from the tclindex.

The root cause was found to be the missing curly braces surrounding the args keyword on the proc declaration line.

i.e. proc testing123 args {

needs to be

    proc testing123 { args } {

This was not an issue with 6.1 but with 6.1.1 and the introduction of the new auto_mkindex command provided by Tcl with tcl8.5

I hope this helps.

[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.

[Author]

Replies