×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Ok, I've got a rollback that's been running for 36 hours or so
(non-production machine luckily) after a QZDASOINIT job was ended
*IMMED...
Apparently IBM as added a 20=Kill Rollback to the WRKCMTDFN, according
to this article...
http://systeminetwork.com/article/journal-insights-getting-out-big-hammer
But it must have been added in 6.1 or 7.1 as my v5r4 system doesn't show it...
The above article has a blurb..
"It was at that point when it dawned on us, as Journal developers,
that folks shouldn’t have to make a phone call to the lab in order to
accomplish this outcome. Instead, there ought to be a tool in their
tool belt which they could use to kill the long running roll-back
phase of a commit transaction. That’s why we introduced the Kill
Rollback option on the Work Commit Definition (WRKCMTDFN) screen. "
So before I start jumping through the hoops required to make that
early morning call myself...does anybody know how kill the rollback at
v5r4?
Thanks!
Charles Wilt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.