Commitment control and open data paths with triggers

I have been reading documentation and setting up test scenarios all day 
and can't get past this last obstacle.

I have a file called TEST with an RPGLE deletion trigger to write a 
history file TESTH.  In the trigger, TESTH is left open for performance. I 
have a little test program that takes the commitment control flag as an 
entry parm.  It deletes a record and then rolls back.  When I call the 
program with commitment control on, it fires the trigger and rolls back 
just fine.  In the same job, when I then call the program with commitment 
control off, it deletes the record but never fires the trigger.  Keep in 
mind that I have to execute STRCMTCTL before running the program for the 
first time and can not ENDCMTCTL between the calls because TESTH is still 
open.

This is a tough one.  My everlasting gratitude to anyone who can help me 
get past this.

Regards,

Mark