RE: IBM Job Scheduler and SOX

["Henza, Guy" <GHenza@xxxxxxxxx>]

OK, I've looked for DSPLOGJS and DSPHSTJS on my 520 V5R3 and they aren't
there.  When I GOOGLE them they come up as V5R2 products.  Is there a
special feature code I need or did they go away in V5R3? 
 
Regards, 
 
Guy 

------------------------------

date: Tue, 14 Feb 2006 08:50:26 -0800
from: "Graap, Ken" <keg@xxxxxxxxxxxxx>
subject: RE: IBM Job Scheduler and SOX

The "Display Log for Job Scheduler (DSPLOGJS) " command should provide
the information you require. 

You can run it using the following parameters:

Type . . . . . . . . . . . . . . TYPE           *ALL        
Time period for log output:      PERIOD                     
  Start time and date:                                      
  Beginning time . . . . . . . .                *AVAIL      
  Beginning date . . . . . . . .                *CURRENT    
  End time and date:                                        
  Ending time  . . . . . . . . .                *AVAIL      
  Ending date  . . . . . . . . .                *CURRENT    
Severity . . . . . . . . . . . . SEV            *ALL        
Output . . . . . . . . . . . . . OUTPUT         *           
                                                            
Job entry:                       JOB                              
  Job  . . . . . . . . . . . . .                *ALL              
  Group  . . . . . . . . . . . .                *ALL              
  Group sequence . . . . . . . .                *ALL              
Remote location name . . . . . . RMTLOCNAME     *ALL              
User . . . . . . . . . . . . . . USER           *ALL              
Message identifier . . . . . . . MSGID          *ALL              

------------------------------

date: Tue, 14 Feb 2006 10:57:54 -0600
from: "Goodbar, Loyd (ETS - Water Valley)" <LGoodbar@xxxxxxxxxxxxxx>
subject: RE: IBM Job Scheduler and SOX

We've not been audited on the actual scheduling of jobs, but for
monitoring
for abnormal completions.

We use the Advanced Job Scheduler for all business operations. There is
a
standard report showing job history information.

I schedule a job called JOBMONITOR with this command:
DSPHSTJS STATUS(*ABNORMAL)                          
         PERIOD((*AVAIL &WEEKAGO) (*AVAIL &YESTMDY))
         SEQOPT(*JOB)                               
         OUTPUT(*PRINT)                             

The date parameters:
WEEKAGO        6      *NONE       *QMDY(D-7)
YESTMDY        6      *NONE       *QMDY(D-1)

Our job runs every Monday to review last week's abnormal jobs.

Not sure of the equivalent for the built-in scheduler.

HTH,
Loyd

Loyd Goodbar
Senior programmer/analyst
BorgWarner
E/TS Water Valley
662-473-5713

------------------------------

date: Tue, 14 Feb 2006 11:07:30 -0600
from: "Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxx>
subject: RE: IBM Job Scheduler and SOX

You can see all of the jobs submitted from the (regular) Job Scheduler
using:
DSPLOG PERIOD((*AVAIL *BEGIN)) MSGID(CPC1236)  

OUTPUT(*PRINT) will give you a report with dates and times.

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group


-----Original Message-----
date: Tue, 14 Feb 2006 10:08:14 -0500
from: "Greg Wenzloff" <GWenzloff@xxxxxxxxxxx>
subject: IBM Job Scheduler and SOX

My SOX auditors want me to prove that the jobs on the job scheduler
actually run according to their schedule.  I've never had a problem with
IBM's scheduler so I'm a bit miffed that I have to prove it works.

Is there any neat file that logs when a scheduled job runs and the state
it finishes in?

Has anyone else had to do this?  What did you do?

Greg