Error using dsjob on windows based DS

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
tine_bi
Participant
Posts: 18
Joined: Mon Nov 24, 2014 6:02 am

Error using dsjob on windows based DS

Post by tine_bi »

Hi
We want to schedule some solutions we have made.
Trying to use cmd line optons and powershell or Splinterware to do so.
First I am trying to get this to work:
DSJOB -domain NONE -server APP10032.tine.no:9080 -user isadmin -password ispwd -run TINE TI_DT_Lagersted_SEQ

This reports: Failed to open project. Status code = 81005

I can run dsjob -lprojects and dsjob -ljobs TINE.
So I know the project and job exist.

Using:
dsjob -run TINE TI_DT_Lagersted_SEQ
returns: error running job. Status code = 99 DSJE_REPERROR

Any ideas what I am doing wrong?
BR
Dan
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

Your current -server value appears to be what you would normally expect to see after the -domain option for the services tier.

Try a -server value of the engine short name by itself instead (i.e. -server APP10032).

If your engine is not running on the default port, then append the engine short name with :port_number, with no spaces before or after the colon.

See also: viewtopic.php?t=145294
Choose a job you love, and you will never have to work a day in your life. - Confucius
tine_bi
Participant
Posts: 18
Joined: Mon Nov 24, 2014 6:02 am

Post by tine_bi »

Thanks, now at least I get staus code = 0
One step forward

BR
Dan
BR
Dan
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Don't use port number with -server option. Indeed, if you're using default port numbers, don't bother with them at all. But it's the domain that's listening on port number 9080, not the engine server.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply