View previous topic :: View next topic |
Author |
Message |
Ranjish Beginner
Joined: 22 Dec 2002 Posts: 64 Topics: 28 Location: Chennai
|
Posted: Thu Jun 16, 2005 11:29 am Post subject: #JI command in job |
|
|
Hi,
We have a scheduled job in CA-7 and from that we are demanding a second job based on some specific condition.
The job step is like this.
JOB1
-------
Code: |
//STEP40 EXEC PGM=U7SVC
//SYSPRINT DD SYSOUT=*
//UCC7DATA DD DSN=login control card,
// DISP=SHR
// DD *
#JI,ID=(002,112,122)
DEMAND,SCHID=002,JOB=JOB2
JEND
//*
//STEP50 EXEC PGM=U7SVC
//SYSPRINT DD SYSOUT=*
//UCC7DATA DD DSN=login control card,
// DISP=SHR
// DD *
#JI,ID=(002,112,122)
DEMAND,SCHID=002,JOB=JOB3
JEND
//*
|
The step STEP50 is getting executed successfully, but the job JOB3 is not getting demanded. We have another step in the same job (STEP40), which is demanding JOB2 in a similar way and it is getting demanded successfully. Only difference is that the JOB2 step was there already and has been running fine for long time.
Is there any specific reason for this? Any changes to be done in CA-7 scheduling part for this?
Thanks for any help you can provide.
Regards
Ranjish |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12372 Topics: 75 Location: San Jose
|
Posted: Thu Jun 16, 2005 11:47 am Post subject: |
|
|
Ranjish,
Is there a schd id 002 for Job3?
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
Bithead Advanced
Joined: 03 Jan 2003 Posts: 550 Topics: 23 Location: Michigan, USA
|
Posted: Thu Jun 16, 2005 11:50 am Post subject: |
|
|
Try changing JEND to #JEND. |
|
Back to top |
|
|
Ranjish Beginner
Joined: 22 Dec 2002 Posts: 64 Topics: 28 Location: Chennai
|
Posted: Thu Jun 16, 2005 11:56 am Post subject: |
|
|
Kolusu,
Yes, all the SCHIDs are available.
Regards
Ranjish |
|
Back to top |
|
|
Ranjish Beginner
Joined: 22 Dec 2002 Posts: 64 Topics: 28 Location: Chennai
|
Posted: Thu Jun 16, 2005 11:58 am Post subject: |
|
|
Bithead,
Sorry, it was a cut paste problem. The job has correct syntax, i.e #JEND.
Regards
Ranjish |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12372 Topics: 75 Location: San Jose
|
Posted: Thu Jun 16, 2005 12:13 pm Post subject: |
|
|
Ranjish,
What were the messages from step050 sysprint ?
Try this . Get rid of step050 alltogether and code the demand card in step040 itself like shown below.
Code: |
#JI,ID=(002,112,122)
DEMAND,SCHID=002,JOB=JOB2
DEMAND,SCHID=002,JOB=JOB3
#JEND
|
Also run a test by just running step050.(i.e delete step040) and see if JOb3 gets demanded.
Hope this helps...
Cheers
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
Ranjish Beginner
Joined: 22 Dec 2002 Posts: 64 Topics: 28 Location: Chennai
|
Posted: Fri Jun 17, 2005 1:10 pm Post subject: |
|
|
Kolusu,
Sorry for the delay. We were not able to test any of the changes. So everytime if we make a minor change, we need to productionize if confirmation.
We were working with scheduling team also. They had made a correction at their end. The UID given for JOB2 and JOB3 were different. They say that it might be the issue. We are yet to check the change in production.
Regards
Ranjish |
|
Back to top |
|
|
|
|