Is there a way to kill an RC job that is currently running? Through RC console, I can see that the job has a status of RUN. However, the owner of the report believes that the job is hung and wants it killed. I don't see any way to kill the job through the Console. I have gone to Webconsole for the server and I don't see the job there (going to Workspace -> Monitor -> Data Services(Agents)). I don't know where else to look to find this job and stop it. Is it possible to do this? We are on WF 7.6.1 on Windows. Thanks in advance.

If the job is still running, it would show up on the reporting server console. Are you an admin? If not, that may be why you can't see it. It would show up under the execution id.

I am an admin. When I go to the RC console, I see the job but when I choose it - the Delete choice on the title menu is grayed out. It is only active if the job has a status of Queue.

simba,

You could kill the corresponding agent from the server console.

Fernando

I went to Webconsole for the server and looked in Monitor Agents and there was no agent showing for this job. I don't know where else to look to find this job.

If it's not in the list of agents, then it's not running on that server - regardless of what anything else indicates.

I never rely on that status in the RC console anyway. If I have two jobs that execute at the same time, it only shows that one of them is running. Go figure.

Do you have more than one WF server that can process a job? Maybe you're going to the wrong WF server's console.

Also, I don't know where the report's owner would get information to indicate that it is hung. If it is from the DBMS, it IS possible that the job is still running in the DBMS, but as far as WF is concerned, the process is gone. In that case, you would have to use a DBMS tool to kill the job in the database itself.

Thanks for the info. I did wonder what was going on when I didn't see an agent for the job. I was hoping I could kill the job in the RC console.

I am on the correct server - we have 2 servers (prod and dev) and her job is only set up on the prod server. She assumed the job was hung because it didn't complete in a timely manner (take that for what it's worth......). simba

As you indicated, once the job has begun (indicated by RUN status) it cannot be deleted within the RC console - only from the web console. Look at the RC log for that job for further information on problems or errors.

I had checked and there was no log for that job. Then I noticed that the user had disabled the job. I enabled it and then disabled it. When I went to WebConsole for the server, I saw an agent for the job. Then I was able to kill the job. Thanks to everyone. simba

simba, you might enjoy the technique of typing out a tiny file into the agent, at the top of the fex that will help you identify an agent and know what fex is running.
-SET &FEXNAME = 'MYFEX';
(or use one of the mre variable like &MR_ITEM_HANDLE, if that works for you)
FILEDEF MYFILE DISK &FEXNAME|.TXT
-RUN
-WRITE MYFILE &FEXNAME &TOD WHATEVER ELSE YOU WANT
...
that way, you'll have a tiny file in your agent named after the fex that is running. Can be very handy.

I always recommend proper naming of intermediate hold files, so instead of H1, H2 etc. I suggest [report id}_H1, [report id}_H2 etc.

Not only will it enable you to see what agent is being used to run what process, but if someone has kindly turned TEMPERASE OFF then if one of your hold files fails your process will not use one created by another process.

If you use a five char report identifier then your hold ifles will normally have eight chars (unless of course you have GT 9 of them ).

BTW, I suggest TEMPERASE is only ever used in a dev environment for many reasons.

T