Can't delete Job

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
samp
Participant
Posts: 25
Joined: Thu Nov 06, 2003 4:34 am

Can't delete Job

Post by samp »

Hello,

when i would like to delete a job, i have the message :

"Error calling subroutine: DSR_EXECJOB (Action=1); check DataStage is set up correctly in project ETUDES
(Subroutine failed to complete successfully (30107))"

first , i thunk that my job was locked, but i could edit it !, transfom it and save it, but not complie it !

i try to reimport my job, by an older version of it ... but i got the same error message !

I try to use the datastage command DS.REINDEX.ALL, DS.REINDEX but nothing.
I always have the same message !

Could you tell me how i can delete drastically my job?
rameshrr3
Premium Member
Premium Member
Posts: 609
Joined: Mon May 10, 2004 3:32 am
Location: BRENTWOOD, TN

Post by rameshrr3 »

Looks like the executable file for your job is de-linked with design time information?
You best option is to save the job under a different name, compile it and use it.
samp
Participant
Posts: 25
Joined: Thu Nov 06, 2003 4:34 am

Post by samp »

i do that, i have copied and renamed my job in order to use it. it works.
but now i would like to delete the wrong one, and i can't.
it's not clean .

is there a way to re-link the executable file ?
rameshrr3
Premium Member
Premium Member
Posts: 609
Joined: Mon May 10, 2004 3:32 am
Location: BRENTWOOD, TN

Post by rameshrr3 »

You should be able to get more information on search . Especially on strings like '30107', 'JOB LOCKED' 'Design time information' etc.
singhald
Participant
Posts: 180
Joined: Tue Aug 23, 2005 2:50 am
Location: Bangalore
Contact:

Post by singhald »

if it is possible to stop the DS engine..

please stop and restart the DS server.

it will solve the issue

Sid
Regards,
Deepak Singhal
Everything is okay in the end. If it's not okay, then it's not the end.
samp
Participant
Posts: 25
Joined: Thu Nov 06, 2003 4:34 am

Post by samp »

i stop and start the ds server, and the server itseft... it hasn't solve the problem...
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Try executing DS.CHECKER in the project. You must have exclusive access to the project.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
samp
Participant
Posts: 25
Joined: Thu Nov 06, 2003 4:34 am

Post by samp »

i try a DS.CHEKER, but same result.
same error.

if i try to compile the job : i obtain the error :

Error calling subroutine: DSR_EXECJOB (Action=1); check DataStage is set up correctly in project ETUDES
(Subroutine failed to complete successfully (30107))

+

(40503) A call to an OLE server has failed, or a runtime error occured within the ole itself.

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

Post by ray.wurlod »

What output did you get from DS.CHECKER? (The output is preserved in the subdirectory &COMO& in your project directory.)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
samp
Participant
Posts: 25
Joined: Thu Nov 06, 2003 4:34 am

Post by samp »

This is my output.

COMO DSR_CHECKER established 15:52:13 25 JUN 2007
**********************************************************************
Checking job files
**********************************************************************
*** Processing: DS_JOBS...
Number of jobs found: 596
*** Processing job XXXX - Jobname
...
*** Checking for undeleted job files
*** Checking for redundant job files...
*** Checking for orphaned job records...
**********************************************************************
Checking Container files...
**********************************************************************
*** Processing: DS_CONTAINERS...
Number of containers found: 0
*** Checking for orphaned container records...
**********************************************************************
End of check.
COMO completed. 15:52:38 25 JUN 2007
I've heard about my problem that i should drop a line in DS_JOBS and then execute a cleanup on my project. But it seems that the cleanup command no longer exist in v7.5...
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

DS.CHECKER is the Cleanup command. It has not found any undeleted, redundant or orphaned job or shared container files.

You can force-delete your job if it does not contain any shared containers. Can you please identify the records in DS_JOBOBJECTS using the following query? Post the results.

Code: Select all

SELECT DS_JOBOBJECTS.OBJNAME, DS_JOBOBJECTS.OBJTYPE, DS_JOBOBJECTS.OLETYPE FROM DS_JOBOBJECTS, DS_JOBS WHERE DS_JOBOBJECTS.OBJIDNO = DS_JOBS.JOBNO AND DS_JOBS.NAME = '<<Job name>>';
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
samp
Participant
Posts: 25
Joined: Thu Nov 06, 2003 4:34 am

Post by samp »

At least i have found a way to delete my job.

1 - Open datastage Administrator and, in your project, open command window.

2 - execute the following SQL : DELETE FROM DS_JOBS WHERE NAME = 'JobName'

3 - Execute at least the DS.CHECKER command . It will find some files previously attached to yout job :
Files found for old job number 952
(DS_TEMP952,RT_BP952,RT_BP952.O,RT_CONFIG952,RT_LOG952,RT_STATUS952)
OK to delete them(Y)?
and orphaned objects.
Orphaned Job Object records found
(J\952)
OK to delete them(Y)?
Click yes , and your job is "quite" properly deleted
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Adequate, but not rigorous.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply