RT_SCTEMP/job_INSERT_INVOICE_SECTION_STATUS_CABS.100556.fifo
Moderators: chulett, rschirm, roy
RT_SCTEMP/job_INSERT_INVOICE_SECTION_STATUS_CABS.100556.fifo
Im running a sequencer where a single job is called in mulitple invocations. The job name is job_INSERT_INVOICE_SECTION_STATUS_CABS. For around 10 invocations the following error is encountered.
RT_SCTEMP/job_INSERT_INVOICE_SECTION_STATUS_CABS.100556.fifo
LOCKED STATUS () -1); file is locked
Please advice.
Thanks.
RT_SCTEMP/job_INSERT_INVOICE_SECTION_STATUS_CABS.100556.fifo
LOCKED STATUS () -1); file is locked
Please advice.
Thanks.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It would appear that two jobs have generated the same pipe filename. This is odd, as the numeric component should be the process ID. But, if you are using an O/S with large pids and the name only uses the rightmost six characters, I guess there's a chance of this happening. Involve your support provider; if my analysis is correct you've uncovered a bug.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Dear Ray/Kumar,kumar_s wrote:Yeah, first task for tomorrow. The job is locked as well. I cant even delete and reimport.
I am running around 100 jobs in parallel of which 50 jobs are getting locked due to the above fifo file locked error. What could now be the possible solution for the above issue.
Thanks.
RK Raju
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Still awaiting response from kumar_s...
Is yours precisely the same error, with precisely the same number in the name of the file?
If not, are the numbers in your file names corresponding to process IDs or, perhaps, invocation IDs of multi-instance jobs?
Is yours precisely the same error, with precisely the same number in the name of the file?
If not, are the numbers in your file names corresponding to process IDs or, perhaps, invocation IDs of multi-instance jobs?
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.
There are around 200 jobs which are being called with invocations. 80 jobs are being aborted with the fifo file locked error.ray.wurlod wrote:Still awaiting response from kumar_s...
Is yours precisely the same error, with precisely the same number in the name of the file?
If not, are the numbers in your file names corresponding ...
eg: RT_SCTEMP/JobName.100556.fifo
LOCKED STATUS () -1); file is locked
The number in the file name is invocation id.eg 100556. I have checked code and concluded that there are no jobs which are being called with the same invocation id.
Please advice on how to solve this issue.
Thanks.
Still stuck with fifo
Hi Ray,
I searchd thru the posts nd found some advce regarding rights on the RT_SCTEMP dir. As suggested in this posts, I gave all the read,write,execute rights to this directory. In fact, I emptied this dir (by takin a backup) & ran the sequencer again. Bt the error is still coming for a new set of jobs. I also noticed that all those fifo files which are present in this RT_SCTEMP dir, corresponding jobs to these files are aborting. I am totally clueless abt this. Plz help, thr is a large no. of jobs failing due to this err.
I searchd thru the posts nd found some advce regarding rights on the RT_SCTEMP dir. As suggested in this posts, I gave all the read,write,execute rights to this directory. In fact, I emptied this dir (by takin a backup) & ran the sequencer again. Bt the error is still coming for a new set of jobs. I also noticed that all those fifo files which are present in this RT_SCTEMP dir, corresponding jobs to these files are aborting. I am totally clueless abt this. Plz help, thr is a large no. of jobs failing due to this err.
RK Raju
Issue in my site got sorted out. And it turned out to be a dump issue.
The first time when I asked to release the lock for the jobs, they have killed the PIDs from Unix. I think that could left the lock of that job over the RT_SCTEMP folder.
Yes that fifo were present, if the job gets aborted.
Next time, they used Admin window to release the lock of that job. And not its running fine.
I wanted you to check, if you run the job in less number of instance, does it get aborted? Start with 10s and gradually increase with multiples of 10.
The first time when I asked to release the lock for the jobs, they have killed the PIDs from Unix. I think that could left the lock of that job over the RT_SCTEMP folder.
Yes that fifo were present, if the job gets aborted.
Next time, they used Admin window to release the lock of that job. And not its running fine.
I wanted you to check, if you run the job in less number of instance, does it get aborted? Start with 10s and gradually increase with multiples of 10.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'