Default port is not being used for dsjob command

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
dohertys
Participant
Posts: 39
Joined: Thu Oct 11, 2007 3:26 am
Location: Sheffield

Default port is not being used for dsjob command

Post by dohertys »

I'm running the command
bin/dsjob -server -lprojects
and I get the error
Status code = 81016
If I run
bin/dsjob -server :31538-lprojects
it works fine

Any ideas whyI need to specify this port number ? - its the default port for the engine so shouldn't really be needed ( I think)

thanks
Cranie
Premium Member
Premium Member
Posts: 19
Joined: Fri Mar 03, 2006 6:02 pm
Location: Sheffield

Post by Cranie »

I would check /etc/services as this is where the dsjob command is looking for the ports (handy truss command).

If you are running multiple engines, upgrading etc and have switched the ports I would check for an old entry of dsrpc (even if it is now on a differing port). dsjob seems to have a check if you are running on the default engine, it will check for dsprc in the /etc/services (on tag installs this can be incorrect). Thus giving you your error of connection refused (81016).
- - - - -

Cranie

Doing the needful.
Post Reply