| View previous topic :: View next topic |
| Author |
Message |
BobGilbert
Beginner
Joined: 12 Sep 2006
Posts: 24
Topics: 10
|
 Posted: Thu May 07, 2009 9:41 am Post subject: Technique for before and after execution in non production |
 |
|
Ok, the scheduling packages can handle order of execution. We have had a product DJC which is being removed. It is married to Jes and basicaly is unsupported, plus I believe it has been kicked out of JES by IBM.
My question is what techniq can be given to users in the test enviornment to ensure jobs run in a particular order. With DJC you just use a /*BEFORE JOB or /*AFTER card. I know longtime users are going to scream and not want to make major changes...ideas?
Thanks,
Bob Gilbert  |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12378
Topics: 75
Location: San Jose
|
| Posted: Thu May 07, 2009 10:06 am Post subject: |
|
|
BobGilbert,
Add the following as the last step to all jobs. This will ensure all jobs run in the order you want to run
| Code: |
//STEP0010 EXEC PGM=IKJEFT01
//SYSUDUMP DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SYSTSIN DD *
SUB 'MY.JOB.PDS(nextjob)'
//* |
_________________
Kolusu
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
BobGilbert
Beginner
Joined: 12 Sep 2006
Posts: 24
Topics: 10
|
| Posted: Thu May 07, 2009 10:30 am Post subject: |
|
|
| Interesting....I suppose could could create a proc and users only need pass the dataset name ..one line? |
|
| Back to top |
|
|
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12378
Topics: 75
Location: San Jose
|
| Posted: Thu May 07, 2009 11:20 am Post subject: |
|
|
BobGilbert,
Yes. You can even use symbolics
| Code: |
//LASTSTEP EXEC PGM=IKJEFT01,
// PARM='SUBMIT MY.JOB.PDS(nextjob)'
//SYSTSPRT DD SYSOUT=*
|
_________________
Kolusu
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
