RE: Insert using ODBC/system DSN

["Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>]

I'd have static (global) file pointer (C terminology here) and check if
it's NULL.  If it is CHGLIBL (or use api; doesn't matter, as it is
processed only once per job), open the file etc.
If not, you can 'safely' assume that you are running in the job that has
gone through the init already.
You might need an exception handler around this code that would reset
the pointer back to NULL in case of an exception in the trigger call
(_CTLA_INVOKE).  This way the 'safely' comment would apply.

This scheme would work with C compiler as it initializes global storage
to zeroes (NULL).  I don't know about RPG etc.

Elvis

-----Original Message-----
 
The problem with a trigger from an odbc job is it might be any one of
the 
various server jobs associated with serving odbc and probably not even 
staying with the same odbc server job even though it is serving the same

odbc client.  Anyone who has had to debug an exit point knows what I am 
talking about.  :-).  So you probably do have to open the file every
time. 
 But maybe odbc and exit points work differently.

Rob Berendt