MVSFORUMS.com

[computer]

Hi everybody,
We are in the testing phase of an application.Our requirement is the integration tetsing of the application.But we dont have access to the ZEKESET.So we need to do the Scheduling of the jobs manuallly.
Is there any jcl that can serve our purpose.

[CICS Guy]

Sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub, sub?

[computer]

ok thanks,
I got the solution from here itself.

[Nic Clouston]

I have a little thing I use: I have a dataset that describes the job relationship and then each job, before ending, executes a Rexx exec that queries that dataset and submits any jobs that are ready to rock'n'roll. Allows multiple predecessors / sucessors. It is quick and dirty but does the job - so to speak
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.

[jsharon1248]

If you have single successor relationships, you can add an IEBGENER step at the end of each job that references the JCL pds as the SYSUT1 and the INTRDR as the SYSUT2. The following example shows how you'd submit a job to the CLASS B initiator. This works well if you just want to submit a string of jobs to run serially. Not so good for anything other than simple predecessor/successor relationships.