RE: Commitment control and open data paths with triggers

I'm not understand why you want to condition the commitment control for TESTH 
file in the trigger program.  Wouldn't it be easier to just always have it 
under commitment control.  In the *inzsr, do callp(e) to QCMDEXC to start the 
commitment control and then open the file.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Mark Adkins
Sent: Thursday, September 30, 2004 9:50 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Commitment control and open data paths with triggers

I have one last hic-up to get past now.  I can't execute an ENDCMTCTL even 
with everything committed because TESTH is still open.  I know I can run 
my program in a specific activation group, compile the trigger with 
activation group *CALLER and then end the activation group, but I am 
wondering if there is a better way.