Re: QTEMP cleanup

Buck,

As you know, each job has its own QTEMP. So the only way that the first DSPOBJD file could be in the QTEMP library is if the two processes were run from the same job.

That was just for clarity, not nitpicking. From a design standpoint (mine) objects should only be put into QTEMP that the job needs - temporarily. Any object that is going to be needed by a later process should not be put into QTEMP. I use the same process that you outlined (DLTF, CPF2105) before one of our processes creates a file in QTEMP. Once the process (not necessarily the job) ends, one should care less what happens to the object(s) left lingering in QTEMP.

* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



Buck wrote:

rob wrote:

So, what you are saying is that you have no responsibility to clean up objects you created in QTEMP after you are done with them and it is the sole responsibility of whomever decides to add other programs to that job stream to decide whether or not to delete your objects based on their need?

I think I understand the question. Someone writes a CL program that uses DSPOBJD *OUTFILE OUTFILE(QTEMP/DSPOBJD) to process data areas in a production library. That CL leaves QTEMP/DSPOBJD in place when it's done.

PGMA /* load QTEMP file */
PGMB /* loop through QTEMP file */

Now I come along and write a new CL program that uses DSPOBJD in the same way, but this time for user spaces. When I stick my program into the job stream, I'll overwrite the other guy's DSPOBJD. How do I know he's really done with it, and didn't leave it there for some reason?

PGMA /* load QTEMP file */
PGMOOPS /* overwrite QTEMP file and process it */
PGMB /* loop through QTEMP file */

The answer is that I probably don't. And my CL will probably be written with a prophylactic DLTF/MONMSG CPF2105 so I won't even know I've deleted his file and put user spaces in there instead of data queues.

Which is why it's Really Important to look at the whole job before making changes to that job.

Very best regards,
--buck