and i noticed when i submitted the job using shell script (executed from command line) it is producing lot of loopback tcp4 connections.... is it normal?
What is going on --- we are not able to run the jobs using autosys or command line scripts to execute DS jobs.
Let's take a step back and deal with the rpc questions later. If you can login to the project using the graphical tools (Designer, Director, Manager and Administrator) then your connectivity is set up correctly and you don't need to delve into the internals of how DS communicates between client and server.
If you login as your DataStage user and ensure that your environment is set up correctly by executing the $DSHOME/dsenv script, then execute the command "dsjob -ljobs {YourProjectName}" what is your output?
Referring to my original post - have you set your user environment correctly? go to $DSHOME and issue a '. ./dsenv' and if you haven't included the dsjob in your path it can be executed in $DSHOME/bin/dsjob
Are you running jobs using the same user id from the Director and from the command line? Also, do you have several projects and if so, please try to see if you can use the dsjob command to list the jobs in another project on the same machine.
I would recommend stopping and starting DataStage.
Do you have multiple engines running on the same machine (i.e. connecting to client via a port number)?
sorry for the late post -
we found out the cause to having two LISTEN ports for dsrpc. some how the connection is not turning from LISTEN to ESTABLISH from a work station who logged into datastage designer. We traced the work station and did perform few test to find the cause... and asked fix the workstation to have proper Unix GUI.