RE: work files in qtemp

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.

Now the paragraph on the concerns with STRSRVJOB is a good heads up.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Ken Sims <mdrg5003@xxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
05/18/2005 03:37 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
rpg400-l@xxxxxxxxxxxx
cc

Subject
RE: work files in qtemp






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.

-- 
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.