http://itknowledgeexchange.techtarget.com/itanswers/qdbsrv0405-reorg-running-for-31-hours-and-still-going/ Tue, 21 May 2013 06:03:52 +0000 hourly 1 http://itknowledgeexchange.techtarget.com/itanswers/qdbsrv0405-reorg-running-for-31-hours-and-still-going/#comment-110337 CharlieBrowne Wed, 22 Aug 2012 18:37:48 +0000 http://itknowledgeexchange.techtarget.com/itanswers/qdbsrv0405-reorg-running-for-31-hours-and-still-going/#comment-110337 Let us know how it turns out for you

]]> http://itknowledgeexchange.techtarget.com/itanswers/qdbsrv0405-reorg-running-for-31-hours-and-still-going/#comment-110325 philpl1jb Wed, 22 Aug 2012 11:59:13 +0000 http://itknowledgeexchange.techtarget.com/itanswers/qdbsrv0405-reorg-running-for-31-hours-and-still-going/#comment-110325 You said the logicals are locked.  Is there any activity on the physical?  How busy is your system.  You might need to end the interactive subsystems.Call IBM.

]]> http://itknowledgeexchange.techtarget.com/itanswers/qdbsrv0405-reorg-running-for-31-hours-and-still-going/#comment-110314 TomLiotta Wed, 22 Aug 2012 04:06:17 +0000 http://itknowledgeexchange.techtarget.com/itanswers/qdbsrv0405-reorg-running-for-31-hours-and-still-going/#comment-110314 It’s hard to say this, but there isn’t much you can do now. I would make a call to IBM to ask if any useful action is possible. And I don’t think this is the right time to discuss how it might be done “next time”. Tom

]]>