Multiple DataStage Versions on Same Server
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
Multiple DataStage Versions on Same Server
We have DataStage 8.1 and DataStage 9.1 installed on the same server. All jobs were migrated from 8.1 to 9.1. When I try to execute a job from CLI using dsjob, the job in 8.1 repository runs and not the one in 9.1.
Am I missing something?
Am I missing something?
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
I renamed the /.dshome to /.8.1dshome and /.9.1dshome for the respective versions. Checked the $DSHOME variable. Was as expected.
I'm not sure I understand what should go into the -domain and -server arguments since both installations are on the same server
I'm not sure I understand what should go into the -domain and -server arguments since both installations are on the same server
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
Nope. I ran
Code: Select all
`cat /.9.1dshome`/bin/dsjob
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
That just means you ran the executable from the 9.1 directory and I doubt there's anything different between it and the one under the 8.1 directory. I would be curious what environment you have loaded. Did you source the 9.1 dsenv before you executed that command?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
I'm sorry Craig. I am yet to renew my membership.
If you're asking me what environment I've loaded then I'm not sure how that needs to be done. Which probably means we are still on 8.1.
If you're asking me what environment I've loaded then I'm not sure how that needs to be done. Which probably means we are still on 8.1.
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
Thank you, Craig.
I sourced the 9.1 dsenv file using
I also checked the $DSHOME and it points correctly to the DS9 home.
I sourced the 9.1 dsenv file using
Code: Select all
. `cat /.9.1dshome`/dsenv
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Try
-domain 9.x_server:port
and
-server 9.x_engine:port
Ex.
-domain abc9.def.ghi.com:9080
(or port 9443, etc. - port of services tier)
and
-server ABC9:31539
(or if default engine port 31538 is used, leave port number off)
-domain 9.x_server:port
and
-server 9.x_engine:port
Ex.
-domain abc9.def.ghi.com:9080
(or port 9443, etc. - port of services tier)
and
-server ABC9:31539
(or if default engine port 31538 is used, leave port number off)
Choose a job you love, and you will never have to work a day in your life. - Confucius
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
Awesome! Used the auth file to store all domain/server/user/pass details and managed to get it running. Thank you all
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
Just have one final follow-up question.
We actually managed to execute using the below command. We did this so that there wouldn't be a need to use the auth file.
My question is - what needs to be done to run the dsjob without even the server parameter just like the 8.1 installation on 31538 runs?
We actually managed to execute using the below command. We did this so that there wouldn't be a need to use the auth file.
Code: Select all
dsjob -server :31539 -run -mode ......
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.