ammoraes
Member
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
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