dsjob or client instal on UNIX machine

ukyrvd · Post by **ukyrvd** » Thu May 08, 2008 10:45 am

I was wondering if we can install datastage client or atleast the ds command line interface on a unix machine.
From the documentation it looks like complete client can only be installed on Windows machines .. But just wanted to make sure that.

Our requirement is we have some java scripts on unix-A machine and our datastage is installed on unix-B machine. we would like to run datastage jobs through the java scripts on A.

Any Ideas/suggestions?

We are looking at possibility of ability to run dsjob command from unix-A or opening up shell connections to Unix-B and run job on B and return to A.

ArndW · Post by **ArndW** » Thu May 08, 2008 10:48 am

The DataStage clients cannot be installed on unix. You can start jobs on UNIX using the "dsjob" command - even remotely.

ukyrvd · Post by **ukyrvd** » Thu May 08, 2008 11:04 am

On A we dont have any datastage components server/client.

ArndW wrote:You can start jobs on UNIX using the "dsjob" command - even remotely.

is that by opening ssh connection from A to B and then issuing the command on B??

Or any other method?

ArndW · Post by **ArndW** » Thu May 08, 2008 11:34 am

You can call dsjob on server A and tell it to start a job on DataStage Server B. If you can "ping" it and it has DS installed and you have a valid userid/password combination you can issue dsjob commands to your heart's content.

ukyrvd · Post by **ukyrvd** » Thu May 08, 2008 12:53 pm

ArndW wrote:You can call dsjob on server A and tell it to start a job on DataStage Server B. If you can "ping" it and it has DS installed and you have a valid userid/password combination you can issue dsjob commands to your heart's content.

I am able to ping B from A.
On A we dont have any datastage software . so when I issue dsjob it is just saying "-ksh: dsjob: not found [No such file or directory]"

ray.wurlod · Post by **ray.wurlod** » Thu May 08, 2008 3:22 pm

You can install dsjob and its associated liraries wherever you like. However, you can only execute dsjob from somewhere where it is installed (and may need to adjust PATH and LD_LIBRARY_PATH environment variables). Details may be found in the manuals.

ukyrvd · Post by **ukyrvd** » Fri May 09, 2008 10:45 am

ray.wurlod wrote:You can install dsjob and its associated liraries wherever you like.

Thanks Ray. This is what I want to make sure if I can install just dsjob & corresponding binaries on unix machine. I couldnt find anything specific in this regard in install/upgrade guide.
I will ask our datastage admin to give it a try using installation code.

just4geeks · Post by **just4geeks** » Fri May 09, 2008 3:16 pm

Datastage server is installed on Unix Machine B. Unix Machine A does not have Datastage installed but can connect to Machine B through telnet sesssion.

Lets say we are connecting to Machine B from Machine A through telnet and issuing dsjob command from telnet session.

In that case also do we need to install dsjob libraries in Machine A?[/b]

chulett · Post by **chulett** » Fri May 09, 2008 3:24 pm

just4geeks · Post by **just4geeks** » Fri May 09, 2008 3:47 pm

Thanks Craig!!

Thats what I thought.

However if answer is no then I don't understand why we are having long discussion about installing dsjob libraries on another machine. am I missing something here?
Even java script on machine A will also connect to Machine B remotely and issue the dsjob command. Please excuse me if I am not able to understand the question properly.

chulett · Post by **chulett** » Fri May 09, 2008 3:53 pm

I was almost going to get into a long discussion on the same topic, but decided not to. I've never needed to worry about getting dsjob components installed elsewhere, but I guess it could be a consideration in a situation where there's no way someone will be allowed remote access to the DataStage server.

jdmiceli · Post by **jdmiceli** » Mon May 12, 2008 10:05 am

To fire off a DSJOB run statement, I believe you also have to have your 'dsenv' set, which can be set in a script. What I would do is to create a script that runs the job correctly on machine B and once it works from there, then you can use a remote connection to just fire off that script as an isolated instance.

Just a thought.