|
View previous topic :: View next topic
|
| Author |
Message |
shrivatsa
Warnings : 1
Active User
Joined: 17 Mar 2006
Posts: 174
Location: Bangalore
|
|
|
|
Hi,
I have 2 region Prod and Test, Prod is having scheduler where test is not. So how can I run the Job in prod after completion of prod job submits another Job in Test region.
Thanks |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Please clarify this
| Quote: |
So how can I run the Job in prod after completion of prod job submits another Job in Test region.
|
I cannot follow what you are asking. |
|
| Back to top |
|
|
superk
Global Moderator
Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA
|
|
| Back to top |
|
|
murmohk1
Senior Member
.jpg)
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
Shrivatsa,
| Quote: |
| So how can I run the Job in prod after completion of prod job submits another Job in Test region. |
I belive you wanted to execute a job in test region basing on prod job completion.
If this is what you want, schedule test job after prod job in production region itself. But dont forget to include jes2 /*XEQ statement. |
|
| Back to top |
|
|
shrivatsa
Warnings : 1
Active User
Joined: 17 Mar 2006
Posts: 174
Location: Bangalore
|
|
|
|
I am including the below steps after the Prod Job
//INTRDR EXEC PGM=IEBGENER
/*ROUTE XEQ SRVDC
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=XXXX.XXXX.XXXX(ABCDE),DISP=SHR
//SYSUT2 DD SYSOUT=(,INTRDR)
/*
But its saying that XXXX.XXXX.XXXX(ABCDE) is not found
Please suggest |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
But its saying that XXXX.XXXX.XXXX(ABCDE) is not found
Please suggest |
There is little that we can do for You...
review Your dataset and member naming
regards
e.s |
|
| Back to top |
|
|
murmohk1
Senior Member
Joined: 29 Jun 2006
Posts: 1436
Location: Bangalore,India
|
|
|
|
Shrivatsa,
| Quote: |
| But its saying that XXXX.XXXX.XXXX(ABCDE) is not found |
Please ensure that this dsn exists in the test region (i.e., where the job runs). |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| dick scherrer wrote: |
Please clarify this
| Quote: |
So how can I run the Job in prod after completion of prod job submits another Job in Test region.
|
I cannot follow what you are asking. |
Hi Dick,
I think, OP wants to ask "How can He initiate some Job in Test Region after completion of some Job in production. "
Not sure though, OP has to approve it.  |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
I am including the below steps after the Prod Job
//INTRDR EXEC PGM=IEBGENER
/*ROUTE XEQ SRVDC
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT1 DD DSN=XXXX.XXXX.XXXX(ABCDE),DISP=SHR
//SYSUT2 DD SYSOUT=(,INTRDR)
/*
But its saying that XXXX.XXXX.XXXX(ABCDE) is not found |
Keep in mind that this step will run in the production region - it is "sending" the other job thru the internal reader on the production region.
| Quote: |
Shrivatsa,
Quote:
But its saying that XXXX.XXXX.XXXX(ABCDE) is not found
Please ensure that this dsn exists in the test region (i.e., where the job runs). |
This is incorrect - the dataset must exist in the prod region. |
|
| Back to top |
|
|
tchen40
New User
Joined: 12 Sep 2007
Posts: 30
Location: Los Angeles, Ca
|
|
|
|
| Make sure that the two JES subsystems talk to each other. Either through MAS or an NJE connection. |
|
| Back to top |
|
|
diwa_thilak
Active User
.jpg)
Joined: 13 Jul 2006
Posts: 205
Location: At my desk
|
|
|
|
Shrivatsa,
| Quote: |
I run the Job in prod after completion of prod job submits another Job in Test region. |
I think you may need to speak to the scheduling team regarding this. Because any project will already have a schedule in place and if you are trying run the job on only one day, then you may need to set that job as special. if you are planning to run on particular day , you may need to move the code to production.
Many projects will not allow a particular job to be triggered and executed in production from TEST. That is why we maintain two regions.
Also we may not have access to change these triggering schedules for production job.
Cheers,
Diwakar
-------------------------------------
Nobody is Perfect. I am Nobody |
|
| Back to top |
|
|
|
|
