RE: triggers and clrpfm and such

Is this really an issue? How often does one CLRPFM a file with triggers on it? I can't imagine just whilly-nilly performing a CLRPFM on our item master table.
I suppose if you had a batch header table and a batch detail table and the trigger on the detail updated the summary in the batch header table might be an issue. Is this the case?

I would not delete the triggers. Just turn them off/on as needed. This is what replication H/A solutions do on the target systems. See below for sample.

create table rob.oktrig (mycol char(5));

create table rob.oktrigcnt (nbrtrig int);

insert into rob.oktrigcnt (nbrtrig) values(0);

create trigger rob.addem
after insert on rob.oktrig
FOR EACH ROW MODE DB2SQL
update rob.oktrigcnt set nbrtrig = nbrtrig + 1;

create trigger rob.dropem
after delete on rob.oktrig
FOR EACH ROW MODE DB2SQL
BEGIN ATOMIC
update rob.oktrigcnt set nbrtrig = nbrtrig - 1;
end;

insert into rob.oktrig values('hi');

call qcmdexc('clrpfm rob/oktrig');
Trigger program or external routine detected an error.

alter trigger rob.dropem disable;

call qcmdexc('clrpfm rob/oktrig');
CALL statement complete.

alter trigger rob.dropem enable;

Of course, at this time the value in rob.oktrigcnt is inaccurate, as you disabled the 'nbrtrig - 1' logic.

Rob Berendt