RE: work files in qtemp

[Ken Sims <mdrg5003@xxxxxxxxx>]

Hi Larry -

> The same holds true here - if I can delete an object in the
> QTEMP library of another job, I think you'll agree that the object is most
> definitely deleted.

The object is definitely deleted, but you didn't delete it.  You sent a 
delete request to the other job and the other job deleted it.  If you could 
delete it directly, that would another matter.

> I could imagine there are much sweeter ways of doing this, and I concede to
> you that it is a simple hack and not an elegant API that truly accesses the
> QTEMP objects in a way we would consider "real" access. But hey, it's free.
> If it's useful to one other programmer then it's worth sharing.

I'm not knocking your method.  For those who have the security to be able 
to use it, it can be extremely useful.  As I mentioned previously, it has a 
major advantage over the break-handling program method in that it does not 
require the target job to have previously done something to establish a 
communications link.

I just think it is important to draw a distinction between directly 
manipulating the QTEMP of another job and indirectly manipulating the QTEMP 
of another job by having that job do it for you.

--
Ken
http://www.ke9nr.net/
Opinions expressed are my own and do not necessarily represent the views of 
my employer or anyone in their right mind.