On 09 mai 2011, you 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.

Do you mean that you run RCLSTG through a BRMS exit point ?

If you do so, we were used to perform the following operations in this
case:

Backup
Seq Items Exit command
10 *EXIT RCLACTGRP ACTGRP(Q1ABRMS)
20 *EXIT RCLSTG
30 *EXIT RCLDLO DLO(*ALL)

Look at http://www-912.ibm.com/s_dir/slkbase.NSF/DocNumber/455703151


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?

Rob Berendt




This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].