Re: Need generic routine to invoke trigger program, using C language _Rread perhaps?

Scott,

As you can see, the 'UPDATE sometable SET somefield = somefield' does
noting except to cause the update trigger on sometable to be fired.

Since sometable might have 3+ million records and is journaled,
performing the dummy update has considerable overhead.

Thus, my desire for a program that gets passed a tablename,
'sometable' in this case, and a trigger program name, say 'MYTRGPGM',
which will then read each record in sometable, build an approprite
pseudo-trigger buffer and call MYTRGPGM.

Make sense?
Charles


On Fri, Sep 19, 2008 at 10:35 AM, Scott Klement
<rpg400-l@xxxxxxxxxxxxxxxx> wrote:

I'm not sure that I understand. How would a program doing _Rread() --
which reads a record -- replace a routine that does 'UPDATE SET
somefield=somefield'

Surely an update and a read are two very different things? And invoke
different triggers with different trigger buffer parameters?

Did you mean to say that you want to use _Rupdate()?

Or are you planning to only test read triggers?


Charles Wilt wrote:

All,

I'm considering putting together a generic routine that can
generically call a specified trigger program instead of having the DB
call the trigger program.

Basically, the program I want will read through a DB table containing
table names and their corresponding triggers. For each table listed,
the program will read each record in the specified table and invoke
the specified trigger program.

This generic routine will replace programs specific to each table that
simply do a 'UPDATE sometable SET somefield = somefield'.

I'm thinking the C language _Rread function will allow me to do want I want.

Anybody (Scott perhaps ;) have experience using _Rread?

Thanks!
Charles Wilt

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.