ERROR:80011:Failed to open project

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
PaulVL
Premium Member
Premium Member
Posts: 1315
Joined: Fri Dec 17, 2010 4:36 pm

Post by PaulVL »

I'd echo out your statement before executing, you could at least see if it was a bad project name at the time of failure.

Only other thing I can think of is a bad user id lookup due to an intermitent LDAP lookup. And even that is a stretch.
qt_ky
Premium Member
Premium Member
Posts: 2895
Joined: Wed Aug 03, 2011 6:16 am
Location: USA

Post by qt_ky »

It sounds like an environment problem.

One script option you could try:

http://www-01.ibm.com/support/docview.w ... wg21507350
Choose a job you love, and you will never have to work a day in your life. - Confucius
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You need to ensure that the value passed through $DS_PROJECT is correct: correctly spelled, correctly cased.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Post by mandyli »

Thanks Ray,

Our current design and working now so far even 8.1 and 9.1 .

ex:-
-------
export DS_CONFIG=/tmp/dsjob_file.txt

/tmp/dsjob_file.txt value as follow
tstdsname:9081,tstdsname:31539,dsusr,pwd

export DS_PROJECT=envdev_tst
export DS_PORT="tstdsname:9081 tstdsname:31539"
export DS_JOB="test_job"
echo $DS_JOB
test_job
$ dsjob -file $DS_CONFIG $DS_PORT -run -jobstatus -warn $DS_WARN -wait $DS_PROJECT $DS_JOB

Waiting for job...
Finished waiting for job
Job Status : (2)

Status code = 2

//------------------------------------------------------------

As per above IBM link they mentioned :

instead of using

<DS_HOME>/bin/dsjob -domain server_name:port -user xxxx -password xxxx -server server_name -lprojects

use:

<DS_HOME>/bin/dsjob -domain NONE -user xxxx -password xxxx -server server_name -ljobs

//--------- But I tired following option still no luck.

1) dsjob -file $DS_CONFIG -domain NONE -run -jobstatus -warn $DS_WARN -wait $DS_PROJECT $DS_JOB

2) dsjob -file $DS_CONFIG -run -jobstatus -warn $DS_WARN -wait $DS_PROJECT $DS_JOB

Is this anything missing here?


Thanks
Man
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Just wanted to get anal and point out that with dsjob you use the "-jobstatus" OR the "-wait" option, not both. Pick one based on the type of status information you want returned.
-craig

"You can never have too many knives" -- Logan Nine Fingers
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Post by mandyli »

Thanks

I have removed -wait option but still no luck.

I have doubt with "-file $DS_CONFIG $DS_PORT"

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

Post by ray.wurlod »

Find out what the values of these are.

Code: Select all

echo $DS_PROJECT
echo $DS_CONFIG
echo $DS_PORT
Why are there two references in $DS_PORT ? This will lead to an invalid command line.
Last edited by ray.wurlod on Mon Jan 05, 2015 7:11 pm, edited 1 time in total.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Post by mandyli »

Hi Ray,

Here as follow. I have same concern.

export DS_CONFIG=/tmp/dsjobfile.txt

tstdsname:9081,tstdsname:31539,dssusr,dsspwd

echo $DS_PROJECT
envdev_tst

export DS_PORT

"tstdsname:9081 tstdsname:31539"


But this is running in PROD also.

$ dsjob -file $DS_CONFIG $DS_PORT -run -jobstatus -warn $DS_WARN -wait $DS_PROJECT $DS_JOB

Is this I have to change anything for DS 9.1?


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

Post by ray.wurlod »

Have you performed the echo commands, particularly for $DS_PORT, in production?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Post by mandyli »

Hi Ray,

from PROD value like this.

DS_PORT : tstdsname:9081 tstdsname:31539.

Is this any issue passing like on ds_job?

but this is how it working on production now.

export DS_PROJECT=envdev_tst
export DS_PORT="tstdsname:9081 tstdsname:31539"
export DS_JOB="test_job"
echo $DS_JOB
test_job
$ dsjob -file $DS_CONFIG $DS_PORT -run -jobstatus -warn $DS_WARN -wait $DS_PROJECT $DS_JOB

Waiting for job...
Finished waiting for job
Job Status : (2)

Status code = 2


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

Post by ray.wurlod »

Status 2 is "finished with warnings". So it looks like dsjob is starting the job satisfactorily in production. What's different in the other environment?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Post by mandyli »

Thanks Lot.

we have same kind of OS and AIX level patches with less CPUs.

other then this most of configuration are same on PROD and TEST server.


Thanks

Man
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Post by mandyli »

Thanks Ray,

we have tested in test server.


Thanks
Man
Post Reply