Status code = -10 DSJE_JOBLOCKED

[patonp]

When executing a job from a script, the following message code is reported:

ERROR: Failed to lock job
Status code = -10 DSJE_JOBLOCKED

We've looked in Director, and the log doesn't register the related code having run within the last 7 days. In addition, the Cleanup Resources utility does not list the job. Any ideas?

One other separate question - I've come across a reference to Status code = 0 in the documentation, but I've never seen this in production. What does a status code of 0 represent in DataStage?

Thanks in advance for any help you can provide.

Peter

[ml]

Are you able to compile this job?

Status 0 represents RUNNING status.

[patonp]

What's really strange is that in the cases where this has happened, production support usually attempts to run the job a second time without a problem. Also, the jobs in question are protected.

This has randomly happened to different jobs at the rate of about 1 per week.

When executing a job from a script, the following message code is reported:

ERROR: Failed to lock job
Status code = -10 DSJE_JOBLOCKED

We've looked in Director, and the log doesn't register the related code having run within the last 7 days. In addition, the Cleanup Resources utility does not list the job. Any ideas?

One other separate question - I've come across a reference to Status code = 0 in the documentation, but I've never seen this in production. What does a status code of 0 represent in DataStage?

Thanks in advance for any help you can provide.

Peter

[ray.wurlod]

I think we need to see the script. When this occurs, is the job open in Designer, Manager or Monitor (Director)?

[Ananda]

Hi,

I am facing the same issue with the following error log:

--------------------------------------------------------------------
Status code = 0
ERROR: Failed to lock job

Status code = -10 DSJE_JOBLOCKED
Status code = 0
Error -4 getting log summary

Status code = -4 DSJE_BADVALUE
Error running job

Status code = -2 DSJE_BADSTATE
saving the logfile
End time: Mon Jul 31 09:49:42 CDT 2006
Start time: Mon Jul 31 09:49:40 CDT 2006
dsjob -run -mode NORMAL -warn 500 -wait -jobstatus -param SLX_DSN=SLXT -param
SLX_USER=SBL_RW -param SLX_PASSWORD=n0w4y07t -param SLX_SCHEMA=SYSDBA -param
HASH_DIR=/etl/test/mss/sbl/hash MSS_SBL_TEST
SBL_SMP_Attachment_SLX_Extract_Hash_Lookup
DataStage return code SBL_SMP_Attachment_SLX_Extract_Hash_Lookup: 255

-------------------------------------------------------------
I checked in Designer, Manager and Director and found that this job is not open. I am actually running this job through Tivoli Work Scheduler (a third party tool for scheduling jobs). The strange part is that I found this error log from Tivoli Work Scheduler inbuilt mail notification and the same was missing in DataStage Director.

In Director it shows successful execution of the job. Moreover when I rerun the job the second time the job runs just fine with no error logs in either TWS or Director.

Please let me know if I need to provide more details.

[vardhan354]

This is the process to unlock the locked jobs.

Processes Locked by Another User and release or check for any issues.

For checking and clearing locked processes PC Start DataStage
Administration

Start/Ascential DataStage/DataStage Administration

Login as dsadm

Select Project and click Command

Enter: DS.TOOLS

5

4

7 (and other numbers from menu given by DSADM based on u requirement)

Enter Pid# will display. Select the pid from the ssh session list from the list_readu command. The pid is the first group in the list for the user with the problem lock.

Enter Y to clear the lock.

But need dsadm password,May be this has to be done by prod. support team.Hope this helps out.

Rgds,
VG

[Ananda]

Hi,

I forgot to mention this in my previous mail. The job was not locked and I was able to open this in Designer too after I received the error notification mail.

regards
Anand

[chulett]

As noted - we'd need to see the script.