× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.