Failed to open RT_LOG2377 file
Moderators: chulett, rschirm, roy
Failed to open RT_LOG2377 file
Hi,
I tried to compile one job through designer then I got the error "Cannot get exclusive access to executable file for job <job_name> - job may be being monitored" .Then I unlocked all the jobs by command UNLOCK ALL.
Again when I tried to run the job i got the error "Failed to open RT_LOG2377 file"...
One more doubt : I am not able to find the job in director but it is showing in designer.
Could you please help me out here..?
I tried to compile one job through designer then I got the error "Cannot get exclusive access to executable file for job <job_name> - job may be being monitored" .Then I unlocked all the jobs by command UNLOCK ALL.
Again when I tried to run the job i got the error "Failed to open RT_LOG2377 file"...
One more doubt : I am not able to find the job in director but it is showing in designer.
Could you please help me out here..?
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
You just went out and unlocked ALL jobs? Bad Idea.
If you can't see the job listed in the Director then your project has become corrupted, possibly from your overzealous use of the UNLOCK verb. You'll probably as a first effort need to try and REINDEX the project, search the forum for that word or DS.TOOLS for discussions on how that is done.
If you can't see the job listed in the Director then your project has become corrupted, possibly from your overzealous use of the UNLOCK verb. You'll probably as a first effort need to try and REINDEX the project, search the forum for that word or DS.TOOLS for discussions on how that is done.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
2377 is not a pid, it is a job number.
This lock is usually taken if the job is open in Director log view (or has been opened by a now-defunct process).
It is locks that you need to address, not indexes or processes.
This lock is usually taken if the job is open in Director log view (or has been opened by a now-defunct process).
It is locks that you need to address, not indexes or processes.
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.
Re: Failed to open RT_LOG2377 file
I was asking about the Project indexing based on this comment:
Of course, it could just be operator error. [shrug]z035011 wrote:I am not able to find the job in director but it is showing in designer.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
I run the command ps -ef | grep 2377 but there is no any process running......
I am not able to find the job in director so I cannot find the job PID and all the logs ....
Actually I reindex the project itself not the job (my mistake I wrote the job)
How can I move forward to comeup with this error......?
I am not able to find the job in director so I cannot find the job PID and all the logs ....
Actually I reindex the project itself not the job (my mistake I wrote the job)
How can I move forward to comeup with this error......?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
2377 is not a pid, it is a job number.
This lock is usually taken if the job is open in Director log view (or has been opened by a now-defunct process).
It is locks that you need to address, not indexes or processes.
This lock is usually taken if the job is open in Director log view (or has been opened by a now-defunct process).
It is locks that you need to address, not indexes or processes.
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.