Unable to save the Job

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
vinodhraj
Participant
Posts: 53
Joined: Mon Sep 12, 2005 6:51 am

Unable to save the Job

Post by vinodhraj »

Hi,

I can't save the job when I am trying to save it and the window getting closed.
It throws the error as mentioned below.

Error calling subroutine: DSR_RECORD (Action=2); check DataStage is set up correctly in project BaseldevLOAD
(Subroutine failed to complete successfully (30107))

Moreover I can't create a job of same name throwing an error that the job already exists.

Is there any way to create a job of same name.

Thanks

Vinod
balajisr
Charter Member
Charter Member
Posts: 785
Joined: Thu Jul 28, 2005 8:58 am

Post by balajisr »

I can't create a job of same name throwing an error that the job already exists.

Is there any way to create a job of same name
Not possible
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

You have some internal corruption in your DataStage project that you need to fix before continuing with this job. Start off with the DS.TOOLS and see if the reindexing option shows any errors on any of the internal files.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Will it allow you to create new job and save in a new name?
Do you have a backup of you project.
Try to do a restart of the server and do a REINDEX as suggested.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Is this happening all the time. Sometimes it happens when you get logged out of the client or someone kills the session. I have encountered this at times when the client just remains open and no activity is performed on it for quite some time. It usually happens even when you are trying to logout a pid from director.
If this is happening every single time then its something to be worried about. If only at times, then its nothing serious. Just make sure you save your job everytime you make a change and not leave the client without any activity for too long.
My 2 cents.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

This one is almost certainly an indexing problem. Get exclusive access to the project then, as the administrator (dsadm or root) execute the DS.REINDEX ALL command from the Administrator client command window.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vinodhraj
Participant
Posts: 53
Joined: Mon Sep 12, 2005 6:51 am

Post by vinodhraj »

I have done Reindexing, but it remains the same. Whenever I am trying to open the project it says the particular job not exists.

Vinod
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Are you able to export the job, or it doesnot even appear in the list.
If you can do that, then import the job back and see what happens.
Sometimes this also helps indexing.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Execute the command DS.CHECKER. Note what its output tells you. Again you will need exclusive access to the project. If the job in question has been partially deleted, it will be completely deleted by this utility, and you will be able to import/restore from backup. Please post results back here.
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