We bring down our DB2s weekly to put them into "maintenance mode" to run an image copy. It's an old, old habit of our DBAs and its due to poor application design. The DBAs want a "point in time" backup, which would be do-able without bringing them down; however the application designers designed a multi-step job that updates tables - but they want that treated as thought it were one unit of work, i.e. back out the whole job if something fails. Because of multi-step update jobs that can't be "split", the only way to ensure a point-in-time backup, they tell me, is to make sure no application can use DB2 while the copy is being taken! We therefore have to drain all initiators, wait for the jobs to finish running, put DB2 in maintenance mode, take the IC, and then go back to normal mode and start the initiators. It was a pain in the HASP to automate that, too! Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209
---------------------------------------------------------------------- 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
