how to submit a daily job?

[Davor_7]

Hi all
a simple question
how can i submit a job and let it do every 8 am?

i know, this is a simple question, but i'm new here :p

thanks in advance...

[Hein van den Heuvel · Accepted solution]

The basic approach is to start the batch job once, and have it re-submit of itself as a first step.

This would be done with a line like:

$subm/noti/log/noprint/after="tomorrow+8:0:0" 'f$environment("procedure")

- Try it!
- Check the help!
- Think about whether you want the exact version number there.
- realize that batch jobs are submitted by file-id, not by name (so be attentive with edits)
- consider a 'jacket' job to pick up the most recent atch job version.
- consider a 'cron' super batch job to launch weekly/daily/hourly jobs
- Check the help again:
= $help dcl date
= $help lexi [f$parse] [f$searc] [f$env]

Google for more examples

Enjoy,
Hein.

[Peter Quodling]

Of course, help submit, will also give some clues. (ANd don't forget the System Manager's Manual in the documentation set...)

Peter Q

[Davor_7]

thanks both~

i know that SUBMIT is to submit a batch job.and i also looked into the help info on this command.
there is actually a parameter (/after) can identify the time you need to submit it. but i have no idea about how to submit once and let it run each day...

that's my question~

let's discard the document here, due to this is simple question, just some command need be typed here, who can answer it?
thanks!

[Mike Reznak]

Hi,

you have to have inside the procedure the command for resubmit. The best is to put it somewhere near the beginning. But it depends on how your procedure is structured. It's the same as it have been mentioned here.

$subm/noti/log/noprint/after="tomorrow+8:0:0" 'f$environment("procedure")

That will do the job.

Mike

[Willem Grooters]

Looks you want "cron" implememted on VMS ;-)
The others have given the VSM solution: Let the job resubmit itself.
Otherwise, there are solutions in the market that do the type of thing you want. Eventually, there might even be "cron for VMS"

Willem

[Peter Quodling]

There was a Cron for VMS (albeit sometime back...) DECscheduler, as I recall. But it was sold to CA, who have probably filed it. There was a thing called Kronos on the Freeware distribution - probably back around version 4 or so. (of the freeware distribution).

q
Leave the money on the Fridge...

[Wim Van den Wyngaert]

I have a script that is used at boot time to get a job in a queue at a certain hour.
See enclosure.

Wim

[Hein van den Heuvel]

>> let's discard the document here, due to this is simple question, just some command need be typed here, who can answer it?

99% if the people READING this forum can.
I can, and I did answer the question.

Read more. Write less.

Best regards,
Hein.

[Jim Geier_1]

The product formerly known as DECscheduler is still available from and supported by CA. Now called Unicenter Job Management for OpenVMS, the product is fully supported and even runs on OpenVMS 8.2 on Alpha and I64.

This is a piece of good software that, in my opinion, should not have been sold, and probably should have been integrated into the OpenVMS operating system.

I agree with the other replies, having a job resubmit itself is a reasonable solution is a small number of such jobs are to be managed. I typically break down the command to two or three commands, partly because I want the move recent version submitted, not necessarily the version currently running:

$ procedure_file = f$environment("procedure")
$ procedure = f$element(0,";",procedure_file)
$ submit/after="tomorrow+0-08:00:00" 'procedure'