MVSFORUMS.com

[misi01]

I do realize that you would normally use something like OPC, but where I'm working, they only seem to use that in production.
So, this is what I would like to do.
I have some JCL that is generally imbedded in a long stream of jobs. This JCL stops all the online CICS databases so that a batch job can be run. The JCL starts by stopping all the databases like this

[Nic Clouston]

You want to imbed 3 steps into your existing jobstram? Or you want your jobstream to submit another job to execute those 3 steps? I am not quite following you. INCLUDE can be coditional in the ense that if you have one setting then you could include those 3 steps but with another setting you could include a simple IEFBR14. But I am not clear on the before and after.

You could also, as you mentioned OPC, write a simple scheduling system in rexx. I did that and it allows for mulitple predecessors and multiple successors. One control data set, one 'plan' data set and a simple rexx program executed at the end of each job.
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.

[kolusu]

misi01,

It is not clear as to what you want to do.

Do you plan to run your stop/start/ JCL from your private library every time that long stream job ran?

You can add a step to submit your JCL using IKJEFT01

[misi01]

I want the three steps to run in sequence. I get the impression with your IKJEFT01 suggestion that I would simply be submitting a job to stop the databases. Would that mean that the step AFTER isn't started until the STODBJCL steps have completed, in which case that might well do the trick.

HOWEVER if it meant that the stop of the DB's was run as a separate job which gets started "whenever", but in the meantime the next step starts running immediately, it wouldn't. I want to be able to ensure the stop DB's is run, 5 seconds elapse, and then the second step starts running.
(I reread my first append, and obviously the first line should have read

[Nic Clouston]

No, your job will execute the next step immediately after submitting your stop step as a separate job. That job may not even starft until the submitting job finishes if the resources are not available. This scenario would not be helped by a scheduler.

What you need to do is split your long job stream into at least two parts. The first would submit the stop and terminate. The stop job would submit the second part which would eventually submit the start job. If you are going to run the job stream without the stop/start then you can use separate include members or even simple have 2 procedures, one does the stop/start and the other simply runs the whole lot (sans stop/start).
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.

[kolusu]

misi01,

Ideally I will have 1 JCL which does the following

1. Accepts parms to sysin ( Look up EXPORT feature in JCL ) so that you can have dynamic STOP/START databases that you are interested. ex https://www.mvsforums.com/helpboards/viewtopic.php?t=12874&highlight=export

2. STEP 1 will STOP the databases you are interested

3. Step 2 will have the WAIT step

3. Step 3 will have your program that modifies/load the database

4. Step 4 will START the databases that you stopped from step 1

It is that simple. I am not sure why you want to make it so complicated.
_________________
Kolusu
www.linkedin.com/in/kolusu

[Nic Clouston]

I am thinking that he wants to insert it in the middle of some existing process - stuff that has to happen before the database work and stuff that has to happen after the database work, Also, perhaps sometimes the database work is not required, otherwise why the kerfuffle?
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.

[misi01]

Thanks for the comments/suggestions. Here's what I put together. First the generalized part that I needed