Where do temp files go?

[Guest.Visitor]

When a job runs and creates temporary files, where do they go? I've tried looking in QTEMP, but it's always empty. I've even tried purposely aborting a job in the middle of a run, but I can't find anything. Any ideas?

[Guest.Visitor]

In case of Batch Jobs I heard that there is a QTEMP created for that Batch job and that cannot accessed by our interactive job.

[Guest.Visitor]

Each job on the system gets its own qtemp library, when the job ends the qtemp library is deleted along with all it's contents. Someone correct me if I am wrong about this, but I believe that the qtemp library of job A cannot be accessed by job B

[Guest.Visitor]

Jim: It sounds like you are running a batch job and, if, that is the case then QTEMP (which is a separate object tied to the batch job) is deleted after your job finishes. The QTEMP lib you a looking at in your interactive session is another object tied to your interactive job. Try this. At your interactive session, create a physical file in QTEMP. DSPLIB on QTEMP and you will see that the file is there. You can do an UPDDTA to it and add records to it and they will also be there. Sign off and sign back on and QTEMP will be empty again.

[Guest.Visitor]

While a job is running and from that job do dspobjd *all/qtemp and you will see the objects; put the list in an outfile and read the outfile and do whatever with the objects in qtemp library for that job... You maybe can search this site for QTEMP and find some stuff. bobh

[cwscholbe@dstsystems.com]

Jim, What are you looking for in QTEMP? Why do you want to see/save these objects?

[Guest.Visitor]

Job B can manipulate objects in job A's QTEMP library via various devious MI utilities. We use PeekPlus from Bytware for that; I think the Tango/04 product lets you do it, as may OpCenter from ASC. And job B can view what's in job A's QTEMP (but not manipulate the objects) if job B does WRKJOB JOB(999999/Job_A_User/A) OPTION(*LIBL) or WRKACTJOB and use option 5 then 13 on job A and if QTEMP is in job A's library list, then you can do option 5 on QTEMP. Otherwise, no.

[Guest.Visitor]

Ken, Thanks for pointing out that it is possible for one job to access another jobs qtemp library. Do you have any examples of when & why this would be valuable? Steve

[Guest.Visitor]

A client asked me if temp files hang around after a job crashes.

[Guest.Visitor]

Nope!