gerd_renz3
VIP Member
RES: The \'S\' status on the job queue
Justin,
could you please share with us exactly what fix you applied. Any SP, ESU,
SAR available?
I have been seeing this so many times but could never figure it out.
Great question, Sebastian!
Thanks, Gerd
-----Mensagem original-----
De: [email protected] [mailto[email protected]]Em
nome de JEMILLER
Enviada em: sexta-feira, 6 de julho de 2001 14:08
Para: [email protected]
Assunto: Re: The 'S' status on the job queue
Hi Sebastián,
The S or "In Queue" status means that a job has been noticed by a UBE kernel
process but has not yet been passed to a runbatch or runube process for
execution. The UBE kernels basically sit in a loop scanning the F986110
table looking for jobs in W status. When one of these kernels finds a job
and is ready to start it running is updates the record to S. Once the job
has started executing, the status moves to P.
Normally a job should not sit in S status for very long. There is a bug
that was in a recent Breaking News item where certain UBE's can lock a
servers spec files while they run. This will prevent other UBE's from
moving from S to P status. I have applied this fix to a few clients and it
seems to have cleared up the problem.
Regards,
Justin Miller
Justin Miller
[email protected]
working with B7332 and XE on AS/400, NT, Solaris and AIX
--------------------------
Justin,
could you please share with us exactly what fix you applied. Any SP, ESU,
SAR available?
I have been seeing this so many times but could never figure it out.
Great question, Sebastian!
Thanks, Gerd
-----Mensagem original-----
De: [email protected] [mailto[email protected]]Em
nome de JEMILLER
Enviada em: sexta-feira, 6 de julho de 2001 14:08
Para: [email protected]
Assunto: Re: The 'S' status on the job queue
Hi Sebastián,
The S or "In Queue" status means that a job has been noticed by a UBE kernel
process but has not yet been passed to a runbatch or runube process for
execution. The UBE kernels basically sit in a loop scanning the F986110
table looking for jobs in W status. When one of these kernels finds a job
and is ready to start it running is updates the record to S. Once the job
has started executing, the status moves to P.
Normally a job should not sit in S status for very long. There is a bug
that was in a recent Breaking News item where certain UBE's can lock a
servers spec files while they run. This will prevent other UBE's from
moving from S to P status. I have applied this fix to a few clients and it
seems to have cleared up the problem.
Regards,
Justin Miller
Justin Miller
[email protected]
working with B7332 and XE on AS/400, NT, Solaris and AIX
--------------------------