|
View previous topic :: View next topic
|
| Author |
Message |
Sree Sandhya Kota
New User
Joined: 14 Aug 2021
Posts: 1
Location: India
|
|
|
|
Hi ..I have a scenario to place a negative dependency between 2 jobs.
it means if one job A executes , other job B should not execute.
This should be done without a scheduler.Can any one pls suggest on this. |
|
| Back to top |
|
 |
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3076
Location: NYC,USA
|
|
|
|
| Not possible as per me. Why not use scheduler? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA
|
|
|
|
| Without a scheduler, the only way to do this is to determine which job to execute manually and submit it. |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1337
Location: Bamberg, Germany
|
|
|
|
| Consider using Jobgroups or, very simple, same jobnames. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3076
Location: NYC,USA
|
|
|
|
| Joerg.Findeisen wrote: |
| Consider using Jobgroups or, very simple, same jobnames. |
how could same job name can be placed in one prod jcl Lib? Usually the member name is same as job name. |
|
| Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008
Posts: 2141
Location: USA
|
|
|
|
| Rohit Umarjikar wrote: |
| Joerg.Findeisen wrote: |
| Consider using Jobgroups or, very simple, same jobnames. |
how could same job name can be placed in one prod jcl Lib? Usually the member name is same as job name. |
1) “Usually” doesn’t mean “must be”.
2) One member can include as many JOB statements as needed.
3) There is no need to use a PDS to store a JCL stream. Any PS dataset is acceptable. Even a deck of punchcards was being successfully used for this purpose in ancient times. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3076
Location: NYC,USA
|
|
|
|
| sergeyken wrote: |
| Rohit Umarjikar wrote: |
| Joerg.Findeisen wrote: |
| Consider using Jobgroups or, very simple, same jobnames. |
how could same job name can be placed in one prod jcl Lib? Usually the member name is same as job name. |
1) “Usually” doesn’t mean “must be”.
2) One member can include as many JOB statements as needed.
3) There is no need to use a PDS to store a JCL stream. Any PS dataset is acceptable. Even a deck of punchcards was being successfully used for this purpose in ancient times. |
It’s unrealistic and I have never seen this is true when I worked for big firms so far. So you might have worked where that is possible as lack of missing scheduling or version control tools e.t.c. If one is using scheduling and version control tool it is not possible to have two jobs with same member name. One member having multiple jobs cards is possible but that’s not the ask here. |
|
| Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008
Posts: 2141
Location: USA
|
|
|
|
| Rohit Umarjikar wrote: |
| sergeyken wrote: |
| Rohit Umarjikar wrote: |
| Joerg.Findeisen wrote: |
| Consider using Jobgroups or, very simple, same jobnames. |
how could same job name can be placed in one prod jcl Lib? Usually the member name is same as job name. |
1) “Usually” doesn’t mean “must be”.
2) One member can include as many JOB statements as needed.
3) There is no need to use a PDS to store a JCL stream. Any PS dataset is acceptable. Even a deck of punchcards was being successfully used for this purpose in ancient times. |
It’s unrealistic and I have never seen this is true when I worked for big firms so far. So you might have worked where that is possible as lack of missing scheduling or version control tools e.t.c. If one is using scheduling and version control tool it is not possible to have two jobs with same member name. One member having multiple jobs cards is possible but that’s not the ask here. |
It is absolutely realistic.
I participated in a project for one of the largest US organizations, where hundreds to thousands of daily jobs, later scheduled and controlled by CONTROL-M facility, are initially generated and customized by means of FTS as several huge job streams, with hundreds of related jobs in each of them. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3076
Location: NYC,USA
|
|
|
|
Exactly , in today world almost everyone uses scheduling and version control tools , what’s done in past or ancient is not something I want to argue on.
So let it get clarity why not scheduling an option here first else as said by Robert submit them manually one after another. |
|
| Back to top |
|
|
sergeyken
Senior Member
Joined: 29 Apr 2008
Posts: 2141
Location: USA
|
|
|
|
| Rohit Umarjikar wrote: |
| what’s done in past or ancient is not something I want to argue on. |
About 80-90% of the total permanently running software nowadays is the “ancient one”, created between 1960-1980; it doesn’t require daily patches, and fixes, unlike the “modern” development which will need every-hour, and every-minute fixes very soon. |
|
| Back to top |
|
|
Phrzby Phil
Senior Member
Joined: 31 Oct 2006
Posts: 1050
Location: Richmond, Virginia
|
|
|
|
| Quote: |
| Even a deck of punchcards was being successfully used for this purpose in ancient times. |
One danger here: In one of the original Mission Impossible TV episodes (1966-73), the Peter Graves character is to disrupt a computer center operation.
He gets on a tour of the computer room, and as the tour group passes a card reader with about a foot or two of cards on the input stack, he slips a punchcard into the pile.
As the group continues around the room, the camera periodically shows the card stack getting lower and lower, and when the fatal card is read in, all of a sudden the tape drives go berserk, and the card punch starts spewing cards out all over the floor.
Never mind there are brackets on the cardpunch that prevent this and which cannot be moved by a program, and never mind about a dozen other things.
Pretty funny. |
|
| Back to top |
|
|
jasorn
Warnings : 1
Active User
Joined: 12 Jul 2006
Posts: 191
Location: USA
|
|
|
|
We do this all of the time and there are various ways to do this. I'd need to know more about your use case but things to know/investigate that might help you are that jobs can be submitted from job, you can make use of datasets to indicate if jobs have run, and you can build your own schedule making uses of files or tables to keep track of what has already run and what to run next.
I've worked in various shops where for whatever reason we would not allowed to use the 'proper' schedule to schedule test jobs. Or, if we were allowed, the process to update the test schedule using the proper scheduler was too onerous.
So I've used the above techniques in various combinations to run test schedules many times. |
|
| Back to top |
|
|
jasorn
Warnings : 1
Active User
Joined: 12 Jul 2006
Posts: 191
Location: USA
|
|
|
|
We do this all of the time and there are various ways to do this. I'd need to know more about your use case but things to know/investigate that might help you are that jobs can be submitted from job, you can make use of datasets to indicate if jobs have run, and you can build your own schedule making uses of files or tables to keep track of what has already run and what to run next.
I've worked in various shops where for whatever reason we would not allowed to use the 'proper' schedule to schedule test jobs. Or, if we were allowed, the process to update the test schedule using the proper scheduler was too onerous.
So I've used the above techniques in various combinations to run test schedules many times. |
|
| Back to top |
|
|
|
|
