Re: QTEMP cleanup

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