DSJOB Setup

nielsek1 · Post by **nielsek1** » Thu Jun 14, 2007 9:59 am

Hello,

We are in the process of upgrading to version 8.0.1 and are having some issues with updating the dsjob command on our scheduling server(not using director). In version 7.5 we copied dsjob and several dll's into a folder and called it using a VBS script and it ran correctly, did not install the client. When I copy the new DSJOB command and what I think are the correct dll's I get this error. If I install the client the command below runs fine however I am trying to avoid this.

dsjob -domain wafedaetl0 -user nielsek1 -password "password" -server
wafedaetl10 -lprojects
ERROR: ASBHome not found

Status code = 80011

I believe Status Code = 80011 is incorrect username and password however I have verified my password and the command I am running on a pc which has the DS Client installed.

ray.wurlod · Post by **ray.wurlod** » Thu Jun 14, 2007 3:57 pm

The burning question is which user ID and password do you have to give when the -domain option is used? I don't know. Experiment.

nielsek1 · Post by **nielsek1** » Thu Jun 14, 2007 6:51 pm

The user ID and password I am using is an admin in Information Server, WAS and on the server. I can run the command above successfully from a pc which has the client installed however I still cannot figure out why the DSJOB command won't work.

I believe in version 8.0.1 you have to use -domain in the comand.

chulett · Post by **chulett** » Thu Jun 14, 2007 9:02 pm

Perhaps you should double-check with your Support provider? I doubt many people have walked your path yet...

scottdevillers · Post by **scottdevillers** » Mon Oct 22, 2007 10:47 pm

I don't know if you tried this yet, but in the Web Admin console, under the Administration tab => Domain Management => DataStage Credentials, to the right is where you can optionally input "Default DataStage and QualityStage Credentials". If you aren't sharing the user registry for Information Server with DataStage (internal users vs. local OS), then try inputting a local (OS) admin's credentials here. This would apply to version 8 only - as there is no web console in prior versions. I just had this occur to me on a fresh install, and that happened to solve my problem.