RE: swap QTEMPs

> Or how about storing a pointer to a permanent context (library) as a
> pointer to QTEMP. I've done that before, too. That can be interesting.
> It's handy for testing things done with another job's QTEMP objects. For
> instance, you might have a job that's creating things in QTEMP and
> things aren't going as expected. Create a permanent context, stuff it's
> address in the PCO as if it's QTEMP, and let the job continue. Now from
> another job you can perform all the normal OS/400 commands against the
> job's QTEMP, because it's a permanent context with a normal library name
> you can use in the commands.
> 
        [Leif Svalgaard]  Gary, this is a great idea. Good for debugging,
        snooping, all kinda things. Just wrote a little program to do this
on 
        my V4R3M0 level 50 box. It turns out that you must grab the files
        while the other job is still running, as all objects in the
permanent
        library are deleted when the first job ends. Don't do this with QSYS
        :-)

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---