Hi All
I can open the job sccessfully.
But When i am trying to create the copy of job its telling
that job is locked. I wondering about this scenario.
thanks
Prashant
job is locked while creating the copy
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 108
- Joined: Wed Jul 28, 2004 7:15 am
job is locked while creating the copy
Last edited by Prashantoncyber on Thu Oct 12, 2006 10:33 pm, edited 1 time in total.
Re: job is locked while creating the copy
Try this command from Administrator
UPDATE DS_JOBOBJECTS SET READONLY = 'NRO' WHERE NAME = '<Job Name>';
Regards
Hexa
UPDATE DS_JOBOBJECTS SET READONLY = 'NRO' WHERE NAME = '<Job Name>';
Regards
Hexa
-
- Participant
- Posts: 108
- Joined: Wed Jul 28, 2004 7:15 am
Try this command from Administrator
UPDATE DS_JOBOBJECTS SET READONLY = 'NRO' WHERE NAME = '<Job Name>';
Regards
Hexa
Hi Hexa,
when i executed this command from Administrator,
It says that 1 reacord is updated.
Subsequently , my problem is resolved.
Can you give some insight how what this command does?
and where to refer & how to learn more about this type commands to
resolve our problems in future.
Many thanks
Prashant
UPDATE DS_JOBOBJECTS SET READONLY = 'NRO' WHERE NAME = '<Job Name>';
Regards
Hexa
Hi Hexa,
when i executed this command from Administrator,
It says that 1 reacord is updated.
Subsequently , my problem is resolved.
Can you give some insight how what this command does?
and where to refer & how to learn more about this type commands to
resolve our problems in future.
Many thanks
Prashant
Last edited by Prashantoncyber on Thu Oct 12, 2006 10:34 pm, edited 2 times in total.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It does something completely unnecessary to recover from a locked job; it sets a "read only" flag to 'NRO' when it was already 'NRO'!
The long and short of your original problem is that you tried to take a copy of a job that was already open - whether in Designer, Manager or Director (Monitor) - or currently running. The DataStage Repository is a database; it uses row level locking to protect objects from inadvertent updates. This is what you encountered.
Chances are that you closed the open connection when you opened the Administrator client, which is why you believe that the update command solved your problem.
The long and short of your original problem is that you tried to take a copy of a job that was already open - whether in Designer, Manager or Director (Monitor) - or currently running. The DataStage Repository is a database; it uses row level locking to protect objects from inadvertent updates. This is what you encountered.
Chances are that you closed the open connection when you opened the Administrator client, which is why you believe that the update command solved your problem.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.