Re: Trigger programme without a trigger.

[Simon Coulter <shc@xxxxxxxxxxxxxxxxx>]

On 11/06/2008, at 4:16 AM, Lim Hock-Chai wrote:

> The problem normally start up with no existing application is updating
> the file under commitment control.  So, at the time of design, the
> programmer is creating the trigger correctly (not need to consider
> commitment control).  Thing then starts to go wrong when a new
> application got created to update the file under commitment control.
> Since we can't predict future, should we say or should IBM recommends
> never create trigger that execute task that cannot run under  
> commitment
> control?

Given that the trigger interface has a field indicating the state of  
commitment control a sensible programmer WOULD write the trigger to  
handle commitment control REGARDLESS of whether it is used by any job  
altering the file.

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 2 6657 8251   Mobile: +61 0411 091 400        /"\
   Fax:   +61 2 6657 8251                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------