Re: Suggestions for replacing WRKQRY -- MIDRANGE-L

On 08-May-2015 10:10 -0500, (WalzCraft) Jerry Forss wrote:


I just did the STRQM command and it throws the message that it
cannot  start because a COMMIT or ROLLBACK must be done.

Presumably that was msg QMR0151 "DB2 UDB for iSeries Query Managercannot start." per the prior logged generic msg QWM1102 "START commandended due to error." per the prior logged specific msg QWM1201 "STARTcommand failed with SQLCODE -752." for which the sqlcode -752 isrevealed in the first level text and the sqlstate revealed in the secondlevel text for which the attempt to activate the SQL environment for QMhad failed due to the prior logged msg SQL0752 rc#.


Someone must have played with this before my time here.

The failure unlikely due to something prior to one's "time" on thethe particular system or in that employ, though possibly in that process[aka job] on the system [but of course nobody shared interactivesessions ;-)]. The failure is likely due to the job on the systemhaving performed some work under commitment control, but for which thatactivity is not at a commit boundary.


What will happen with either option?

That would be revealed by reviewing what is pending commit, from theWork With Commitment Definition (WRKCMTDFN) output; issue WRKCMTDFNJOB(*) STATUS(*ALL) ASPGRP(*ALLAVL) LUWID(*ALL) OUTPUT(*) and review the5=Display Status and then F6=Display Resource Status [probably ajob-level definition for *DFTACTGRP] to track down what resources arePending Changes. IMO reviewing the OUTPUT(*PRINT) is less tedious, soperhaps that is a better option.

If the ROLLBACK is issued then the pending changes are discarded. Ifthe COMMIT is issued then the pending changes are confirmed\committedand thus their completed effect is visible.