In DataStage I have used the indirect all method to implement "late binding" 
(referred to in the OOP post) to create a "rules engine". The actual rules to 
be applied/tested could not be known until the data actually arrived. So the 
test routine itself was effectively little more than a dispatcher, determining 
which rule routine(s) to call, and calling them via the indirect call mechanism.
 It worked wonderfully well.
U2-Users mailing list

Reply via email to