|
Paul, I think there's something amiss with that. When I do a DSPFD the trigger always has the library in there and not *LIBL. ADDPFTRG FILE(EMPLOYEE) TRGTIME(*AFTER) TRGEVENT(*INSERT) PGM(*LIBL/AA) results in DSPFD Program Name . . . . . . . . . . . . . . : PGM AA Library . . . . . . . . . . . . . . . . : ROB Not *LIBL. What one often does with a trigger in your case is analyze the parms. If the trigger updates another file and it can't find it in the existing library list then often you open the file with the library specified. And you get that library from the trigger parms where it tells you the name of the library containing the file you are updating. Now if your trigger is in a different library, and you need to call other programs from that same library, you could do this same technique. Only instead of using the library from the trigger parms you could retrieve the attribute of the trigger program and use that library to either add it to the library list, or call the necessary programs qualified. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.