RE: Insert using ODBC/system DSN

> From: rob@xxxxxxxxx
>
> Chill buddy.

"Chill buddy"?

Did you get the idea I was offended?  All I did was answer your question
"why not use an API?"  In so doing, I expressed the idea that APIs are not
the universal panacaea, and that a call to a CL program is perfectly
acceptable, especially to people who don't want to deal with binary numbers.

No need to chill.  The climate is like, totally awesome here, dude.


> I brought that up because some people raised the concern
> that simply calling a CL to do the CHGLIBL causes overhead, just because
> CL does.  That's why I suggested the api.  Then in this case, if that is
> all the CL does, then I would think that disposing of it properly
> would be the right solution.

The problem was calling the CL every time, which adds the overhead.  Calling
the CL via an RPG program in a first-time routine removes the CL call
overhead as well as an API does, provided that the trigger is relatively
persistent.

I understand your point, and thank you for taking the time to make it
clearly in this message.  The complexity of an API may make sense in the
specific case where the library list change is called over and over again.
Hopefully, though, that's not the situation here.  If the trigger is called
repeatedly within the same job, the sheer simplicity of a CL program might
well outweigh any gains in overhead.

Joe