|
We faced this very same problem with file updates coming from the web (via ODBC). Even though we are using a profile with the correct jobd the file updates end up taking place under the profile QUSER with an empty library list. We solved it by adding library list entries at the start of the trigger program (extracting the file's library from the trigger parameters). We had another problem with service programs as these are bound to before the trigger code is run, so these can not be bound as *LIBL, you must specify the library in your binding directory. This caused havoc with our change control system as it does not have this option. Luckily binding directories don't change often. Mark
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.