DSXchange

Posted: **Fri Jan 02, 2015 2:54 pm**

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.

Posted: **Fri Jan 02, 2015 6:36 pm**

It sounds like an environment problem.

One script option you could try:

http://www-01.ibm.com/support/docview.w ... wg21507350

Posted: **Sun Jan 04, 2015 4:03 pm**

You need to ensure that the value passed through $DS_PROJECT is correct: correctly spelled, correctly cased.

Posted: **Mon Jan 05, 2015 2:29 pm**

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

Posted: **Mon Jan 05, 2015 2:46 pm**

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.

Posted: **Mon Jan 05, 2015 6:16 pm**

Thanks

I have removed -wait option but still no luck.

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

Thanks.
Man

Posted: **Mon Jan 05, 2015 7:10 pm**

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.

Posted: **Mon Jan 05, 2015 9:03 pm**

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

Posted: **Mon Jan 05, 2015 9:43 pm**

Have you performed the echo commands, particularly for $DS_PORT, in production?

Posted: **Tue Jan 06, 2015 3:50 pm**

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

Posted: **Wed Jan 07, 2015 2:14 am**

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?

Posted: **Wed Jan 07, 2015 1:40 pm**

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

Posted: **Sun Jan 11, 2015 6:50 pm**

Thanks Ray,

we have tested in test server.

Thanks
Man

DSXchange

ERROR:80011:Failed to open project