Hi Larry -
These programs could be useful, particularly as they do not require every 
possible target job to create a message queue and assign a break-handling 
program to it, which is another method of doing the same kind of thing.
BUT ... this method means that you have to have authority to use commands 
that generally are going to be *PUBLIC *EXCLUDE.  And to use the STRSRVJOB 
command:
   To use this command, you must be signed on as QPGMR, QSYSOPR,
   QSRV, or QSRVBAS, or have use (*USE) authority to the user
   profile of the job being serviced.
I could run this on our development system but not on our production system.
And a traceable event has to occur to trigger the exit program, which the 
break-handling program method does not require.
My other comment ... when you said that you could easily access another 
job's QTEMP, that wasn't really true.  Like the break-handling program 
method, you are getting that job to access its own QTEMP on your behalf, 
which isn't quite the same thing.
--
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 mailing list archive is Copyright 1997-2025 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.