Re: Turning off the requirement to have *allobj to look at the joblog of a currently running *ALLOBJ job.

Good example.  And that should be enough.

But if the person running that job does a SIGNOFF *LIST do they then get a 
printed spool file that they could look at?  That attribute only blocks 
the joblog of a running job, not the spool file created.

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





"Henrik Krebs" <hkrebs@xxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/29/2004 04:13 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
<midrange-l@xxxxxxxxxxxx>
cc

Subject
Re: Turning off the requirement to have *allobj to look at the  joblog of 
a currently running *ALLOBJ job.






Say you have *SAVRST but not *ALLOBJ. Guess that it's then possible to 
copy an object to tape (and bring it to a system where you have *ALLOBJ) 
to sneek. The complete joblog will make it much easier to find the objects 
that you want to save.

k

> date: Mon, 29 Mar 2004 15:17:25 -0500
> from: rob@xxxxxxxxx
> subject: Re: Turning off the requirement to have *allobj to look at
> the joblog of a currently running *ALLOBJ job.
> 
> Can you give an example of what you might see in the joblog that you 
> wouldn't be able to see via something else in the job like call stack or 

> open files; that would be determined to be a potential security breach?
> 
> Rob Berendt



_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.