|
Ah... good idea! I can try that if it's the only option. I guess I'dpart
rather have the object created automatically with *PUBLIC authority
somehow.
Brad
www.bvstools.com
On Fri, Mar 18, 2016 at 8:50 AM, Glenn Gundermann <
glenn.gundermann@xxxxxxxxx> wrote:
Hi Brad,group
Can you place the users in a group profile and have authority as the
profile?
Yours truly,
Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144
On 18 March 2016 at 09:48, Bradley Stone <bvstone@xxxxxxxxx> wrote:
Interesting scenario here I thought I would throw out for some ideas.
An application uses QTEMP for temporary files. It builds files as
authoritiesofis
a process. For normal batch or interactive jobs it works fine. QTEMP
IDunique 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
processfor the process from QTMHHTTP to a real user ID.QTEMP
A file in QTEMP is created, process completes, all is good. Files in
are left there.
A new user comes along and changes the User of the job. Now the
theerrors out because the new user doesn't have the right authorities to
object in QTEMP to clear it or remove it and start over.
Any ideas on how to make this work without having to change
listtolist
the QTEMP objects or delete them each time? Or give users *ALLOBJcreate
authority?
I guess I'm looking for some sort of flag that we can say "when you
an object in QTEMP, make it so any User ID can work with it.". I'mlist
guessing there isn't such an animal, but I am curious.
Brad
www.bvstools.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
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.