|
View previous topic :: View next topic
|
| Author |
Message |
ankit917350
New User
Joined: 22 Aug 2021
Posts: 1
Location: United States
|
|
|
|
I want to connect to teradata table for Select query as well as Google bigquery environment in same job.
There is a parameter in Job-card SCHENV which is TESWC for teradata and GCXS for bigquery.
Is there a way I can connect to different environment in same job based on some condition |
|
| Back to top |
|
 |
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1255
Location: Bamberg, Germany
|
|
|
|
Purpose
For JES2 jobs only, use the SCHENV parameter to specify the name of the WLM scheduling environment that is to be associated with this job. A scheduling environment is a list of required resource state settings. By associating a scheduling environment name with a job, you ensure that the job will be scheduled only on a system that satisfies those resource state settings. Note, however, that the job will go through JCL conversion prior to being held. If the JCL of the job refers to a subsystem (DD SUBSYS=), then TYPRUN=JCLHOLD is the only way to ensure that the required subsystem is actually up and functioning at JCL conversion-time. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA
|
|
|
|
| ankit917350 wrote: |
I want to connect to teradata table for Select query as well as Google bigquery environment in same job.
There is a parameter in Job-card SCHENV which is TESWC for teradata and GCXS for bigquery.
Is there a way I can connect to different environment in same job based on some condition |
Welcome!
You will need to send this question to right support group at your site. Usually it depends how your environments are configured , i have some like this for some of the environments but we have different jobs set up accordingly. So that’s why forum can’t answer these type of questions except to give an idea about what is what. |
|
| Back to top |
|
|
|
|
