How Trigger the job without CA-7

Pons · Posted: Tue Aug 14, 2007 8:36 am

Hi,

I just want to set the Test Cycle like my production cycle.
In prodction they schiduled by CA-7, But i just want to submit in my own. So how to trigger the another job from my main job with out CA-7.

Any thing like Internel Reader.... Please explain clearly...

stodolas · Posted: Tue Aug 14, 2007 8:43 am

Why not have them schedule a full test cycle as well?

Devzee · Posted: Tue Aug 14, 2007 9:05 am

yes you can use internal reader - for this you got to change JCL's

There should be CA 7 for test environment also - Check

Pons · Posted: Tue Aug 14, 2007 10:57 am

Hi Stodolas,

I dont want to schedule the whole cycle. i just want the important jobs for my testing purpose. Please let me know how we submit the job from another job?

Hi Devzee,

We dont have an access to schdule the job form CA-7. That what i want to make it using JCL, I have an JCL with Changes. but i dont know how to code the Internal Reader for another job...

Please Explain...

Devzee · Posted: Tue Aug 14, 2007 11:01 am

use IEBGENER
//SYSUT1 DD DSN=2ndJCL
//SYSUT2 DD SYSOUT=(A,INTRDR)

Pons · Posted: Tue Aug 14, 2007 11:26 am

Thanks Devzee,

This what i needed. Ok. One more thing, how can i check the previous 2nd job return code. If i just check the step.rc=, then it will take the IEBGENER return code only right. Please advice....

expat · Posted: Tue Aug 14, 2007 3:44 pm

Pons · Posted: Tue Aug 21, 2007 11:05 pm

Hi expat,

I didn't get you. if give the cond==(0,NE,STEP1)
then it will check the return code of IEBGENER only right.

I just want to check the return code of INTRDR.
Using SYSUT1 i submit the job. Then how can i check the internal
reader job return code....

dick scherrer · Posted: Wed Aug 22, 2007 12:17 am

Hello,

I'd suggest you define what jobs you want to run and their dependencies and use the ca-7 or hand-hold your test and submit what you want run as each process successfully completes.

It seems a waste of time to "roll your own" scheduler for this.

There is no "internal reader" return code. Once the gener copies the jcl from the dataset to the system, it becomes a job by itself - there is no backward communication to the job containing the gener that submitted it.

Craq Giegerich · Posted: Wed Aug 22, 2007 12:18 am

dick scherrer · Posted: Wed Aug 22, 2007 3:12 am

Hello,

Each of your jobs would have a new step added at the end (GENER to the internal reader) that would submit the "next" job. There would be no backward communication or testing. As each job successfully completed, the "next" one would be submitted.

This means that if your jobs all ran successfully, the entire set of jobs would be run one behind the other as a result of submitting only the first job. Before turning this new set of jobs over to production, the "last" step would need to be removed.

jasorn · Active User Joined: 12 Jul 2006 Posts: 191 Location: USA

There are a couple ways I know to 'roll your own' scheduler. Apparently lots of shops let you use ca7 for test environments. None I've worked in have

Ways I know?

1. Call one job from the last as suggested in this thread.
2. Create a schedule from an app on another platform. This app could be on unix or windows or anything that can submit the job via ftp. Using something like access(eegads!) you can set up a pretty easy and powerful test scheduling system.
3. Baby sit the jobs(i.e. run them manually)

Pons · Posted: Fri Aug 24, 2007 10:20 pm

Thanks for your suggestings.

Thanks dick, Now i understood clearly. I try with my test cycle in different way...

dick scherrer · Posted: Sat Aug 25, 2007 12:58 am

You're welcome.

Let us know if there are new questions.