There are more than a few people who would consider using DB2 for metadata as an advantage (operationally and functionally), but leaving that debate aside....
The original poster noted they have DB2 already. Now, of course I don't have the original poster's LPAR configurations, etc., but as a general statement TOM is unlikely to alter the peak DB2 MSUs profile much at all (if at all) in a DB2 shop. (If you're not a DB2 shop already then you might have a slightly longer chat with your "friendly IBM representative.") The original problem cited is that other, non-affiliated workloads (WebSphere Application Server with DB2) are growing, and TOM would seem to be very much on point in addressing that particular problem. Perhaps other products are as well, but I'm doing my best to answer the original poster's question most directly. - - - - - Timothy Sipples Resident Enterprise Architect STG Value Creation & Complex Deals Team IBM Growth Markets (Based in Singapore) E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
