gerd_renz3
VIP Member
Alexander,
I studied the PID question for some different reasons lately and found this:
when a job is put in the queue (F986110 table) and is still in status 'W',
it already has a PID assinged to it. This does not make very much sense, at
least on a Unix box, because it is not executing yet at this moment. This
PID is the Unix process-ID for the Queue mother process (daemon).
When it starts executing, status 'P', the PID is changed to the Unix
process-ID for the actual runbatch process, as we would expect.
What you are taking is the PID from the runube process. To my understanding
runube only puts a job in the queue and goes off.
What you need is the PID for the runbatch process and you can get it only
from the F986110 table and you have to make sure that the process is in
status 'P' already. I have a client who monitors UBE's through the Unix-PID
ever since B732. I do not know exactly what they do, but it seems to work
well for them.
Good luck, Gerd
-----Mensagem original-----
De: [email protected] [mailto
[email protected]]Em nome
de ammoraes
Enviada em: quarta-feira, 19 de dezembro de 2001 15:30
Para: [email protected]
Assunto: Runube
Hi everybody !!
We're schedulling the execution of some batch jobs using TWS. We wanted to
know if the job ended with errors or if it is processing for a long time, so
I thought of getting the runbatch's pid on the Unix and query the F986110
table for the job status.
But when runube starts the ube, it dies leaving no way to get the runbatchs
pid.
Does anybody had a problem like this before ? Is there another way of
getting the jobs pid on the Unix ?
Thank you very much ...
Alexander
Alexander Moraes
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=2
5546
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list / forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com
JDEList is not affiliated with JDEdwards®
+ - - - - - - - - - - - - - - - - - - - - - - - -+
I studied the PID question for some different reasons lately and found this:
when a job is put in the queue (F986110 table) and is still in status 'W',
it already has a PID assinged to it. This does not make very much sense, at
least on a Unix box, because it is not executing yet at this moment. This
PID is the Unix process-ID for the Queue mother process (daemon).
When it starts executing, status 'P', the PID is changed to the Unix
process-ID for the actual runbatch process, as we would expect.
What you are taking is the PID from the runube process. To my understanding
runube only puts a job in the queue and goes off.
What you need is the PID for the runbatch process and you can get it only
from the F986110 table and you have to make sure that the process is in
status 'P' already. I have a client who monitors UBE's through the Unix-PID
ever since B732. I do not know exactly what they do, but it seems to work
well for them.
Good luck, Gerd
-----Mensagem original-----
De: [email protected] [mailto
[email protected]]Em nomede ammoraes
Enviada em: quarta-feira, 19 de dezembro de 2001 15:30
Para: [email protected]
Assunto: Runube
Hi everybody !!
We're schedulling the execution of some batch jobs using TWS. We wanted to
know if the job ended with errors or if it is processing for a long time, so
I thought of getting the runbatch's pid on the Unix and query the F986110
table for the job status.
But when runube starts the ube, it dies leaving no way to get the runbatchs
pid.
Does anybody had a problem like this before ? Is there another way of
getting the jobs pid on the Unix ?
Thank you very much ...
Alexander
Alexander Moraes
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=&Board=OW&Number=2
5546
+ - - - - - - - - - - - - - - - - - - - - - - - -+
This is the JDEList One World® / XE mailing list / forum.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found on the JDEList Forum at
http://www.JDEList.com
JDEList is not affiliated with JDEdwards®
+ - - - - - - - - - - - - - - - - - - - - - - - -+
