× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Rob -

That last paragraph sounds like nit picking.  From a "users" perspective,
we being the users of Larry's code, we can access some other jobs qtemp.
How it does it is not that important.

I don't think I'm being nit-picky. If Larry could do exactly what he said he could do, that would be a serious security issue. As I see it, there is a significant difference between accessing the QTEMP of another job and persuading that other job to access it on your behalf. The former should not be possible above the MI level. The latter can be done at least two different ways (the TRCJOB way and the break-handling program way) and probably more. But normal security applies to the latter methods.


Another comment, even with Larry's method (and the break-handling program method and any other method of that type) there are limitations. For example, you can't DSPPFM to your screen of a file in another job's QTEMP. If you run that command, the display is going to appear at the target job. You have to copy the file to a regular library or output to a spooled file and look at that spooled file (in the target job's spooled files, not your own job's). If you weren't going through the target job, these limitations wouldn't exist.

--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.