Define "set up". Is it an authority issue, or does your trigger "assume"
that it is always running in a particular library list setup? If the
former, consider program adoption. If the latter then you'll have to set
up the library list otherwise. A common technique is to use the trigger
data structure to determine what the library is that contains the file.
Then, if your application is set up this way, either retrieve a job
description or a known data area that stores the library list in that same
library and set the library list to that. Or, if it is only the one
program, you could use the F spec keyword to open the other files in the
same library as the file's library. EXTNAME & USROPN.
I'd avoid hardcoding the library. Soon as you do someone will try a
CRTDUPOBJ to make a test case and just hose you all up.
Rob Berendt
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.