Chapter 6: Route Calls

Routing DFCs

The available routing DFCs are:

route_vprod() – routes data to the SFM through a single production object. See “route_vprod()”.
route_veng() – sends data to the SFM through a specific engine. An engine contains a specific set of production objects listed in a specific order. See “route_veng()”.
route_vrec() – sends data to the SFM through a specific route. This operation bypasses any production objects. The route_vrec() function also allows you to send the transaction to all productions object when the reserved keyword “ENGINE” is used. See “route_vrec()”.
route_recx() – sends data to the SFM through an “ENGINE” (all production objects), or through an engine, production object, or a route. Arguments passed to the function determine which activity is performed. See “route_recx()”.
route_sync() – sends data to a router application through a route or through all production objects when “ENGINE” is specified. The route_sync() function is used by an MQAcq acquisition AIM and propagates out-of-bounds information growing from each message in a queue. See “route_sync()”.

**Table 6-1: Routing function summary**
Routing function	A route	A production objection	An engine	All production objects using “ENGINE”
route_vprod()		X
route_veng()			X	X
route_vrec()	X			X
route_recx()		X	X	X
route_sync()	X	X	X	X