× 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.



"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 02/23/2018 01:00:02
PM:
----- Message from Craig Richards <craig@xxxxxxxxxxxxxxxx> on Fri,
23 Feb 2018 17:33:59 +0000 -----

To:

"RPG programming on the IBM i (AS/400 and iSeries)"
<rpg400-l@xxxxxxxxxxxx>

Subject:

Re: On Triggers and library lists.

Hi Charles,

Yes I usually prefer that method too but not all files are RPG access.
In particular there is one with a CLOB on.
I don't believe you can open files with CLOBs in native RPG.

Also the program is building JSON objects using the DB2 JSON_OBJECT
publishing function from data on the trigger after image for insert into
the CLOB so that all needs to be SQL.

But I agree, I have a particular preference for ExtFile when I can get
away
with it.

best regards,
Craig

On 23 February 2018 at 17:24, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

I wouldn't use an override....

Instead, use the EXTFILE() keyword on the f-spec..

Charles

Sorry, but I'm really behind on my e-mail and I'm just getting caught up
on this thread.

Doesn't the library on the EXTFILE keyword have to be hard coded at
compile time? And wouldn't that mean it's useless for the point of this
thread--i.e., if the trigger can handle the same file in multiple
libraries, using EXTFILE would force it to update the file in the
specified library and not necessarily one in the same library as the file
causing the trigger to fire?

Thanks in advance for clarifying my understanding (or misunderstanding),
Michael Quigley
Computer Services
The Way International

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.