Failed to open project - Status code 81015

shin0066 · Post by **shin0066** » Tue Jul 24, 2007 9:30 pm

we are experiencing "Failed to Open Project and job is aborting with Status code 81015" - we are trying to execute the DS job thru Autosys.

when i did netstat -a | grep for dsrpc
i can see 2 tcp4 instances

Code: Select all

tcp4       0      0  *.dsrpc                *.*                    LISTEN
tcp4       0      0  loopback.dsrpc         *.*                    LISTEN

what is this loopback.dsrpc?

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.

Any info is appreciated!

ArndW · Post by **ArndW** » Tue Jul 24, 2007 9:49 pm

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?

shin0066 · Post by **shin0066** » Tue Jul 24, 2007 10:15 pm

Hi ArndW,

the same jobs and same autosys is been working from last 4 months and why suddenly these issues.. that is what i could not understand.

we can log into director and run the jobs.... successfully!!

ArndW · Post by **ArndW** » Tue Jul 24, 2007 10:26 pm

And the 2nd part of the question?

shin0066 · Post by **shin0066** » Tue Jul 24, 2007 10:33 pm

when i type
"dsjob -ljobs {projectname} "
it is throwing ksh: dsjob: not found.

is something wrong?[/code]

ArndW · Post by **ArndW** » Tue Jul 24, 2007 10:35 pm

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

shin0066 · Post by **shin0066** » Tue Jul 24, 2007 10:58 pm

hmm

here is what i got... same error 81015

$ $DSHOME/bin/dsjob -ljobs {projectname}

Status code = 81015

so what is causing this and what is the solution.

Thanks

ArndW · Post by **ArndW** » Tue Jul 24, 2007 11:06 pm

That is quite strange. And can you start jobs from the director as well? Is the system very slow and have you tried stopping and starting DataStage?

shin0066 · Post by **shin0066** » Tue Jul 24, 2007 11:16 pm

Yes we can run the jobs from Director, jobs are running at normal runtimes. but not thru job scheduler or via command line using wrapper shell.

No i did not bounce the DS Server.....

ArndW · Post by **ArndW** » Tue Jul 24, 2007 11:24 pm

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.

shin0066 · Post by **shin0066** » Tue Jul 24, 2007 11:36 pm

Yes it is same user ids which we are using via director and scheduler.

I tried the same command to see the status of other projects - it is same issue.

ArndW · Post by **ArndW** » Wed Jul 25, 2007 12:13 am

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)?

shin0066 · Post by **shin0066** » Wed Jul 25, 2007 6:42 am

Nope, we do not have multiple engines....
let me try bounce DS Engine....

shin0066 · Post by **shin0066** » Wed Jan 09, 2008 10:20 am

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.

Thanks