|
It may well be that this is totally inapplicable in your case, . . . .
It is indeed. The program in question is a trigger applied to files IN the very libraries it would add to the *LIBL. Triggers, by their nature, have to be fast, and this one, containing a recursive-descent parser for a scripting language, already has more than enough overhead as it is. If it were constantly adjusting the library list, response times would become intolerable.
But at any rate, not only am I adding libraries the job in question is already accessing, one way or another, but I ended up explicitly adding the libraries to the TAIL end of the library list, in order to avoid having them preempt anything else.
Besides which, if I actually did need to know whether the ADDLIBLE failed, the C "system()" call, along with a few other things from the C runtime, would tell me that.
-- JHHL
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
