Re: QTEMP objects and Different Users on the Same Job

[Luis Rodriguez <luisro58@xxxxxxxxx>]

Brad,

A couple of (somewhat quick, not really well thought out) ideas:

1) Create a program with the proper (adopted) authorities just for deleting
and/or recreating your files.

2) Use the user's id as part of the table key. Your program can then
process the file's records without the need to delete and create the files
every time.

HTH,

Luis

Sent from my Moto G phone. Please excuse my brevity.
On Mar 18, 2016 9:18 AM, "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 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
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> 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.