Re: Rules Engine [OT]

> I'm not even talking about rules consistency: what if we have conflicting rules,
> does the resulting state depend upon the order of execution? Rule priorites? I
> don't have any time to invest into this bu**it.

We're currently using a DLM table against a COBOL interpreter which executes the rules against a given transaction. It works, is "very difficult" to maintain, but competency on the part of the staff has made certain it's not disolved into out and out conflict. It requires on senior developer, full time to keep up with rules changes, implementation and testing which is reported to be a nightmare assignment for our testing department. :)

We're looking into an XML application solution which will do the dirty quite effectively. The proposal thus far is a bit rough, but we were looking to see if there was anything rational out there... apparently not, thus it will be developed in house.

It WILL work, it WILL be easy to maintain, test, develop and along with it we'll be able to upgrade our existing legacy system to somthing a bit more recent than Hard-push Cobol. Currently the only trigger in the entire system is to detect submitted files, everything else is user driven or scheduled... not exactly a maintenance free system. :( So we're improving and improvising, well if everything goes as planed I'll let you know, otherwise expect some more entries / submissions to the Quote of the day on www.dbdebunk.com. ;) Loved that site BTW. :)

G'day! Received on Thu Aug 23 2001 - 18:59:55 CEST