|
Interesting scenario here I thought I would throw out for some ideas.
An application uses QTEMP for temporary files. It builds files as part of
a process. For normal batch or interactive jobs it works fine. QTEMP is
unique to that Job.
The process looks like this:
1. Delete any existing QTEMP files
2. Create new QTEMP files
3. Put data in them to process
4. Done.
Now throw this into a web server situation. The jobs change the User ID
for the process from QTMHHTTP to a real user ID.
A file in QTEMP is created, process completes, all is good. Files in QTEMP
are left there.
A new user comes along and changes the User of the job. Now the process
errors out because the new user doesn't have the right authorities to the
object in QTEMP to clear it or remove it and start over.
Any ideas on how to make this work without having to change authorities to
the QTEMP objects or delete them each time? Or give users *ALLOBJ
authority?
I guess I'm looking for some sort of flag that we can say "when you create
an object in QTEMP, make it so any User ID can work with it.". I'm
guessing there isn't such an animal, but I am curious.
Brad
www.bvstools.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.