Re: RCLSTG vs CPF8204-Commitment control cannot be active during RCLSTG or RCLOBJOWN.

On Mon 05-May-2011 04:35 , rob@xxxxxxxxx wrote:

Pretty much been running the same processes as always when doing our
downtimes but now I am getting CPF8204-"Commitment control cannot be
active during RCLSTG or RCLOBJOWN." when trying to run a RCLSTG.
This is before our save. To get around it I sign off and then back
on. The only recent change was implementing BRMS.

Makes me nervous signing off to resolve this. Makes me wonder if
that will ROLLBACK some change somewhere.

How do I tell what started commitment control for this session? What
is running under such a thing? And, if anything will be rolled
back?

WRKCMTDFN JOB(*) to see what is the origin for the CPF2804. Presumably the QBRM [or is that QBRMS] activation group is just left active in case more BRMS activity is going to occur in the job. Thus signing off is probably fine. Seems familiar anyhow. Nevertheless...

If running with INQMSGRPY(*RQD), then the inquiry CPA8350 should result from ENDCMTCTL when there are outstanding transactions; a choice for how to handle them is offered. SIGNOFF *LIST with the proper logging level would also show the effects of anything rolled back; that or knowing which journal(s) logged the activity, which were then displayed.

Regards, Chuck