On Wed, 16 Apr 2014 13:37:22 +0000, DASDBILL2 wrote: > IBM made RECORD=NO the default and RECORD=YES an option for very good > reasons.
Thanks for the reference Bill - and yes, I know IBM needs to allow for "unforeseen circumstances". However, out in the real world, people need to get work done. When something screws up, I want to be able to find out why/when. As the DB2 issue clearly illustrated, knowing when something is amiss is crucial. The DBAs had no idea (at the time) - we found out when LOGREC dump jobs kept firing one after another. But at least we knew to look, and saw DB2 chewing the machine - and ignoring everyone. We got out out it by bouncing one subsystem, not a potentially long incident followed by poring over a SADump for days. Personally, I reckon any software released for public consumption shouldn't have the option to specify RECORD=NO. Simple as that. Shane ... ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
