Does anybody use generated routes? If so do you have an idiots guide to using them? The examples in the documentation are a bit contrived and don’t actually explain how to actually use them (or not to me:-))
I’ve used it in one place within our environment. Although, I will soon be changing it. It works OK with relatively low volumes of data. Once the volume increases, the generate route will SLOW you down. In my opinion, there is almost always a better way to do it.
If you’re still interested in it, I’ll let you take a look at some snippets of code that I’ve done.
I have a potential need/desire to utilize the ‘generate route’ functionality witin Cloverleaf. My scenario is that I have an inbound thread that needs to route to any one my multiple outbounds, but I do not want to define all of the routes and further clutter-up the spider-web of routes that exist currently. I’ve coded the proc and it works, but my questions are:
1) What is the performance hit of doing this versus defining the routes within NetConfig?
2) I used the standard ‘tps’ template to code the ‘generate route’ proc, but is there a different template to use? The documentation on coding a ‘generate route’ procs is very light.
You didn’t mention whether or not you need to xlate the messages between threads. If not, here’s what I would do:
Set the destination thread in the metadata of the message (DESTCONN) and also setting SKIPXLT to 1. This accomplishes 2 things.
1. You don’t have to define any routes. The messages are simply placed on the outbound side of the destination thread.
2. You can skip the xlate portion of the routing, which is the slowest part.
Unless things have changed with the generate routed function, I would steer clear of it. It’s fine for low volumes, but it really starts to drag as the volume increases.
I concur with Jim. After my post I did get involved in trying to support an interface that was built using generate routes and when asking Quovadx support for advise there first response was why use generated routes? Anything that can be built using generated routes you should be able to build using the ‘normal’ routing’ of Cloverleaf with some Tcl.
We had route generate procs in several high volume interfaces and there was considerable drag on processing throughput. They are high maintenance as you must build the equivalent of DATAXLATE keys perfectly and then put braces around those suckers. A pain in the backside! We have retired them all now.
I would suggest looking at doing a Tcl Trxid procedure where you can interpret data and set routes. These are easier to build and maintain and provide optimum routing flexibility.
If you need some route generate code we still have our old suckers.
Thanks for your feedback. Our initial approach was going to be using a trx_id determination, but thought we would see what the ‘generate route’ could provide. Our intial testing seemed to indicate that the ‘generate route’ was slower, but I thought maybe it was just an anomaly. Based on the feedback, we will go with our original approach.
Thanks again for your feed back.
Jim Cobane
Henry Ford Health
Author
Replies
Viewing 8 reply threads
The forum ‘Cloverleaf’ is closed to new topics and replies.
.
.