I tend to submit daily, and handle the weekday processing with some logic in DCL. Having the procedure resubmit itself daily means you don't have to worry about job or system restarts. So long as there's always at most one job in the queue and the first thing it does is requeue itself for tomorrow at 7am, it (generally) does the right thing.
I use this daily batch job because I find I tend to have a mixture of daily maintenance and staggered BACKUPs and other such; some daily and staggered weekly stuff. I'll have GOTO or GOSUB or CALL for some processing, based on the weekday. Even if all the job does is re-queue itself for tomorrow and exit, it's not a load on the system.
DECscheduler (now a CA product of some other name, IIRC) and other packages can provide this scheduling more directly, and there's a Freeware Kronos package around IIRC. DECscheduler (now ScheduleIT?) can handle recovery and restart and error reporting, too. Haven't looked in detail at Kronos.
