RE: IBM Job Scheduler and SOX

Expanding on this, you can use API's to analyze the job scheduler.  It 
records the last time the job started and its job number etc.  Then you 
could use the DSPLOG ... JOB(.../.../...) (using the information gleaned 
from the api) and get the exact job start and end time.

I suppose IBM's Advanced Job Scheduler or Robot's product might be able to 
tell you the same stuff.

Probably plays heck with the people who have every job schedule entry be a 
SBMJOB because they have difficulties getting the library list right on 
the ADDJOBSCDE.

But auditors are morons.  I was just handed a security audit today that I 
have to fill out.  Some good parts, but most of it ignores Client/Server, 
etc.  Questions like display the authority on STRDFU and that genre.  Gee, 
should I tell them about the command WRKDBF?  What about direct links to 
the data from Excel?

Can't wait to slap them after they get the list of system values and we 
get dinged because we allow more than one 5250 session per user.  Why is 
it beneficial to harass 5250 users from being productive but you are not 
to audit the same user id from using two Client/Server based sessions? 
Probably based strictly on the ease of harassing users from being 
productive.  Maybe we need a user profile value, that could default to a 
new system value that would limit a user from connecting from more than 
one IP locations.  To discourage Client/Server users from sharing i5 
passwords.  And maybe the limit session one could be modified to defer to 
this one.  Allow multiple 5250 sessions from the same IP address.  Let me 
guess, this is where the Exit point vendors shine.

Rob Berendt