I have a job (JMAINJOB)
that is streamed every weekday night AT =23:00.

This brings down the network to log everyone off
Then does a STORE @[log in to unmask]@

Brings up the network services JINETD, FTP, ODBC.
Then runs a separate job (JWEEKDAY)
to run several other jobs (say JOB1, JOB2 etc.)

and sets itself to run again AT=23:00.
That works fine.

Without going into too much detail ...
I would like to specify in the JWEEKDAY job that
JOB1 should terminate before JOB2 be allowed to start
and son on for JOB3 and JOB4 etc.

These are the options I have considered:
1. Figure out how long JOB1 takes to run and put an AT on
on JOB2 making it not start till the JOB1 has finished.
I don't like this option because the duration of any job is not really fixed
and will vary with the size of my database.

2. Daisy-chain all the jobs from one to another so that
JOB1 would finish by streaming JOB2.
JOB2 would finish by streamingJOB3  etc ...
Don't like that either because
a) I would like to be able to add or delete jobs to the JWEEKDAY
job without having to care about which order they are in and
b) if any job in the chain flushed for any reason,
the remaining jobs in the chain would be lost.

3. Last option was to set the JOBLIMIT to 4 so as to allow
    1. Network services (JINETD)
    2. FTP  - and -
    3. ODBC
to run with just one other job.
Thus JOB2 could not start unless JOB1 had finished etc.
Sounds OK but I can't get the LIMIT command to work inside a job.
I get error messages telling me to use the ALLOW command.
When I modify the JOB card to MANAGER.SYS and
insert the ALLOW command I get more messages
saying I will need to ALLOW the ALLOW command.


So my questions are :
1. Which is the best option?
2. If it is the LIMIT option then how do I allow it in a job?
3. Does anyone have any other suggestions?

Thanks in advance.
Seamus BROWNE
[log in to unmask]