RE: SBMJOB Scheduled Date/Time

[Jerry Adams <Jerry@xxxxxxxxxxxxxxx>]

William,

I think Mike was talking about a simple SBMJOB, not the Job Scheduler.  For the Scheduler, you are correct (I set all of mine to *NOSBM).  For the basic SBMJOB there is no 'Recovery Action' (that I could find, anyway), and I've never experienced or tested this.  What I have experienced is a currently running job in QBatch when the system died; that job, just like a QInter job, dies not to be resuscitated until one resubmits it.  My guess (and it's only that) is that a scheduled SBMJOB is similar to a CL program with a DLYJOB; i.e., it would be gone when the system came back.  

But I've been wrong before; sounds like a good subject for a test.  It might not even be necessary to actually take the system down; just ENDSBS QBATCH (or whatever) after a test job was submitted.  Then STRSBS QBATCH (such as most IPL start-up programs do) after the scheduled time.  Or you could go the whole nine yards and re-IPL the system within the necessary time intervals.

I did browse the Info Center, but couldn't find anything that addressed this situation, as I'm sure Mike did, too.

Jerry C. Adams
IBM System i Programmer/Analyst
B&W Wholesale
office: 615-995-7024
email:  jerry@xxxxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Willie J. Moore
Sent: Tuesday, January 27, 2009 10:58 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: SBMJOB Scheduled Date/Time

Mike,
That depends on the recovery action option. If you display the option for the 'Recovery action', it shows you what each means.
William....

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Mike
Sent: Tuesday, January 27, 2009 7:50 AM
To: Midrange Systems Technical Discussion
Subject: SBMJOB Scheduled Date/Time


I have a question, if we used SBMJOB  with a scheduled date. What happens if
the system has been rebooted or goes down during the time it is waiting to
run? Does the job stay out there waiting to run when the system comes back
up?