It's not whether the DBA is paranoid; it's whether they're paranoid enough. That's your philosophical answer.
I can't give you a technical answer on whether you can get away with your idea. But I'd STOP the member/subsys, then delete/define all the non-actives. Not complying with IBM's instructions is probably a "well, you get to keep the pieces" situation if it doesn't work.
Computer Systems Manager
1. I like the simplicity here.
2. But. If you're copying the old contents to the new, larger contents, then the tracks (CAs?) in the new dataset, which lie "Beyond" the size of the old dataset (Higher RBA than the High-Alloc-RBA of the old dataset) are unformatted, right? Is that a problem for a DB2 Active Log file (particularly in a rollback)?
5 Manhattan West
New York, NY 10001
Thank you :-)
12 blocks per track, innit? Hmm. I wonder if there's anyone out there still using a 3380 track build... Lord knows everything _else_ IBM ever offered for sale is still running _somewhere_.
UPS6756, #1544403 Oleander Drive, Suite CWilmington, NC 28403 Phone: (910) 660-8649Fax: (910) 523-5504