>> MCL J13484.112 is required whether or not data spaces are used, though >the >> problem is indeed exposed by DB2's use of data spaces (which actually >uses >> the base space of the DB2 server virtual machine quite heavily). > >To put a finer point on it, please oh please put all of the previously >referenced MCLs on the box before you run z/VM 5.2. > >Hardware problems often manifest themselves in ways that make it difficult >for us to quickly say "Oh, THAT. That's caused by lack of MCL xyz." So >we end up spinning our wheels on problem determination. We'd much rather >work on *new* problems rather than ones we already solved. :-) > >We're serious enough about this that we're discussing how to put checks >for pre-req MCLs into system initialization so the system won't run if a >required MCL isn't applied! >
A further spin on this, we cannot predict the characteristics of workloads which will cause outages without MCL J13484.112 (or any of the other listed MCLs) applied. Just because DB2 is not being used, or the fact 5.2 IPLs cleanly and runs without problems, doesn't mean you will not take an outage without the MCL applied. Please, just apply them. They do apply concurrently. Best Regards, Les Geer IBM z/VM and Linux Development
