Page 1 of 1

Automatic Job Scheduling in Rex

PostPosted: Thu Jun 05, 2008 6:31 am
by PADDY
Is it possible to schedule a job (without using any schedulers) to run based on time using REXX? Please help us in this regard.

-Paddy

Re: Automatic Job Scheduling in Rex

PostPosted: Thu Jun 05, 2008 7:09 am
by dick scherrer
Hello Paddy and welcome to the forums,

REXX is just another language. It has no built-in "chron"-style function.

If you need to schedule something, why not use the scheduling software already on the system?

Re: Automatic Job Scheduling in Rex

PostPosted: Sat Jun 07, 2008 5:04 pm
by ram23bal
Iam also having the same requirement as Paddy....

I want to take backup on daily basis... Its a bunch of manual work iam doing is it possible to do with Rexx on a daily basis....

Re: Automatic Job Scheduling in Rex

PostPosted: Sat Jun 07, 2008 5:38 pm
by dick scherrer
Hello,

I want to take backup on daily basis...
So, schedule the backup to run daily. . .

Re: Automatic Job Scheduling in Rex

PostPosted: Sun Jun 08, 2008 9:23 am
by ram23bal
I too thought of it... But my problem is getting approval for scheduling is a big task in my concern.... So iam searching for an better alternate....

Re: Automatic Job Scheduling in Rex

PostPosted: Sun Jun 08, 2008 11:03 pm
by dick scherrer
Hello,

If it is worth ensuring it is scheduled, it is worth getting the approval. If it doesn't really matter, run it when you think of it.

There may be an easier alternative, but it will not be better. . .

Keep in mind that if you put toggether some RYO (roll your own) solution, you will still need to check that your process is always working. If you use the scheduler, once it is in, you should not have to be concerned agan.

Re: Automatic Job Scheduling in Rex

PostPosted: Thu Jun 12, 2008 3:41 am
by MrSpock
Paddy and ram,

The two things that neither of you have mentioned yet is:

1. Why REXX and not some other langauge (I would think Assembler or C would be better suited)?

2. Where would this processing take place?

Obviously, you wouldn't run this code from a TSO session, since your session would be constantly locked while a routine constantly checks the TOD clock. So, would you be running this code in the background, either as a batch job or started task? Both of those may be options depending on what your site standards allow. Would they be running in a more real-time transaction-based system (CICS, Netview, some Automated Operator Console product, Connect:Direct)? That seems to me to be the best option, since these systems are always available, are auditable, and are highly reliable.