|
At 23:20 27/10/99 -0400, you wrote: > >Booth >You can qualify the trigger program to a particular library. However this >is not your problem, Your problem is the resources(FileMaudit) that the >trigger program uses. How does the Trigger program find all the >resources it needs. > >A. The Library List - Best choice over all for flexibliity. >B. Run Qcmdexec or call a CL program from the Trigger program to add the >"Libraries" Needed. > >Using solution B. you are Hardcoding the libraries. What happens if you >have a "Test or Development" version of the files and programs ? >Now you physically have to change the Trigger program to add the "Test" >library names. Not Good. > >Solution A. is the Best. You know the Golden Rule, "Get Thy Library >List In Order ! " . > If you use a command somewhere in there you could use the product library option on the command to get that sucker in and out of your library list without the ugly SETLIBL code that normally happens with manipulating library lists. Regards Evan Harris +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.