Re: Accessing objects in another job's QTEMP

> I guess what I'm asking is, would it enable a command like ADPQTEMP
> (Adopt QTEMP) that's called as:
> 
> ADPQTEMP JOB(123456/QUSER/JOBNAME)
> 
> It may allow programatic changes, but sometimes it's nice to just have a
> command like and qtemp access. Then things like wrkobjpdm and CHGDTAARA
> and CLRPFM etc all work.
> 
> ADPQTEMP is a command I'd like to see, it's not one I've made (yet <G>)
> But it would depend on changing the current job's pointer to QTEMP to
> point to a different QTEMP. Is this one of those things that will be
> locked up w/the MI changes in V5R4 and beyond?
> 
> -Walden

I would never mess with that pointer. Too risky if your programs fail, or you
simply forget to restore the pointer to your own QTEMP before you sign off.

You could however use that API to duplicate one or more objects to a
non-QTEMP library, let the job wait for a signal while you use any commands 
to change those objects and copy them back in to the other job's QTEMP again.

--
Njal