|
View previous topic :: View next topic
|
| Author |
Message |
triloknathreddy
New User
Joined: 13 Nov 2007
Posts: 10
Location: hyderabad
|
|
|
|
Hi,
the job card calls to two procs, two procs shouls run on different systems.
//BLTK00WW JOB (45034,2120,00000,1111),'TERA..COBRA',
// CLASS=A,MSGCLASS=J,REGION=6M,NOTIFY=BLTK00
/*JOBPARM SYSAFF=SYSE
// JCLLIB ORDER=(BATCH.LO.M418366.JOBCARDS.TEST.TEST)
//*
//TRILOK EXEC TRILOK
/*OUTPUT CODE SYSAFF=SYSD
//TILLU EXEC TILLU
//
The above one is not working, can any one help me on these.
SYSAFF parameter decides the system. |
|
| Back to top |
|
 |
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
| Why do you think that the procs should run on different systems? |
|
| Back to top |
|
|
triloknathreddy
New User
Joined: 13 Nov 2007
Posts: 10
Location: hyderabad
|
|
|
|
i have existed proc which contains teradata and sas, teradata needs to run on cyst and sas no longer runs on cyst, becoz they expired sas on sysd, hence i have to spilt the proc in to two procs.
Two methods to solve these
1)we can have to job cards , one job runs on sysd for teradata and sas on syse.---> Need to change the dependencies
2). one job card which calls these two procs and runs on two different systems, hence no need of changing the dependecies.
if i have job card which runs these two procs, i no need to change the dependencies.
Let me know ur thoughts on these. |
|
| Back to top |
|
|
Akatsukami
Global Moderator
Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL
|
|
|
|
Let me rephrase the question:
Given that you claim over three years experience in using JCL, what in that experience makes you think that a single job can somehow run programs on different LPARs?
It's been decades since I last worked on a JES2 system, but that OUTPUT card doesn't look as though it has the proper syntax. If you can get assistance from a senpai in your shop, I strongly urge you to do so. |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
| Quote: |
1)we can have to job cards , one job runs on sysd for teradata and sas on syse.---> Need to change the dependencies
|
Lazy huh? |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
So if my understanding is correct here, you want your job to start off on one LPAR, finish the process of PROC1 and then take a stroll over to another LPAR to process PROC2.
You are joking, aren't you
 |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8697
Location: Dubuque, Iowa, USA
|
|
|
|
Oh, my.  |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
| Quote: |
| the job card calls to two procs, two procs shouls run on different systems. |
As the Rolling Stones once told:
"You can't always get what you want. . ."
| Quote: |
if i have job card which runs these two procs, i no need to change the dependencies.
Let me know ur thoughts on these. |
Create 2 jobs and schedule appropriately. . .
d |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| triloknathreddy wrote: |
| the job card calls to two procs, two procs shouls run on different systems. |
To start with, you run (execute) Jobs not the PROCs. (okay...just being picky.).
I believe, if you tell us what is that you want to achieve, possibly there can be alternate solutions instead of telling us what do you think can be a solution in itself. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hi Anuj,
TS explained that there is currently a process that runs on one machine. Due to some changes, the goal is now to run one part of the job on one machine and the other part on a different machine.
TS also explained that one of their alternatives is to split this into 2 jobs and run each job on the appropriate system.
In order to get around documenting/promotinig the second job TS wants this to be "automagic" . . .
As TS already recognized and as has been suggested, 2 jobs should be used/scheduled - one for each system/machine. |
|
| Back to top |
|
|
|
|
