Page 1 of 1

doubt in SCHENV

PostPosted: Mon Jun 15, 2009 10:23 pm
by manojlives
I have 2 jobs ...

1st runs in schenv=DB2X
2nd runs in schenv=DB2Y

I have to submit 2 jobs , one after another,
what ever changea i make in 1st job i have to make in 2nd job, So it happens that i maintain 2 jobs and everytime i need to edit both jobs and submit,

Is it possible to maintain these 2 jobs in 1 job so that it will be easy for me to get going on this job. help me out...

Is it possible to run jobs in 2 schenv in a single job?

Re: doubt in SCHENV

PostPosted: Tue Jun 16, 2009 12:01 pm
by expat
Without the slightest idea of what the job does, it may be dangerous for us to guess an answer.

Re: doubt in SCHENV

PostPosted: Wed Jun 17, 2009 5:45 am
by dick scherrer
Hello,

For someone here to be able to help, you need to more clearly post what you need to accomplish. . .

Re: doubt in SCHENV

PostPosted: Wed Jun 17, 2009 8:35 am
by manojlives
Sorry .. let me be clear


1st job ---- Schenv = DB2X ----

unload from DB2 region DB2x , using Ikjeft01 utility

2nd job ---- Schenv = DB2y ----

unload from DB2 region DB2y, using Ikjeft01 utility

i want to run both this job step in a single job...
Is this ok?

Re: doubt in SCHENV

PostPosted: Wed Jun 17, 2009 8:39 am
by dick scherrer
Hello,

Running 2 unloads in the same job should be ok as long as they are run in 2 separate steps.

Re: doubt in SCHENV

PostPosted: Wed Jun 17, 2009 10:51 pm
by manojlives
No i tried it with that way....

With watever SChenv , I run the job the step that runs in that schenv alone is running
wheras the other job fails....
bcoz i am trying to unload across 2 regions.

First job ,Db2 region = db2x , schenv= db2x
I mean: Select * from db2x.dfbp32p.table

second job Db2 region = db2y , schenv = db2y
I mean : select * from db2y.dfbp42p.table

Is This possible?

Re: doubt in SCHENV

PostPosted: Wed Jun 17, 2009 11:44 pm
by dick scherrer
Hello,

Suggest you speak with your dba.

It may be that your "2 regions" are on different lpars and as such cannot be processed in one job on one lpar (unless the other region is defined as a remote). Again, a topic for your dba.