RE: Trigger programme without a trigger.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Joe Pluta
Sent: Friday, June 06, 2008 11:00 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: Trigger programme without a trigger.


I'm sorry, but I don't believe that. Any time DFU is required on
production data, red flags ought to be gonig up all over the place - if
you were a SOX shop, it would take longer to do the paperwork than the
change!

You right on the paperwork, however even with SOX, you can temporary grant higher authority, make the
change, and then fill out the appropriate paperwork.

I agree about the routine use of DFU / SQL. But the way I've always seen it work is:

1) Somebody notices a problem
2) The problem may require an immediate data fix
3) Problem cause is determined and appropriate changes made to prevent reoccurrence.

However, at least here the person getting the elevated authority to fix the data is usually if not
always a developer. Such person should be familiar with the data and implications. So they'd know
about an I/O module. On the other hand, immediate means immediate, compiling a new fix program that
uses the I/O module and getting it transferred from the development box to production takes more time.
With triggers, I can quickly use SQL, and know that I haven't broken any other rules.


Charles



This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.