After my extract program completes (creates a save file), the agent is still 'in use' and the brower window is still open and appears to be running. I have an END, -RUN and -EXIT immediately following the 'ON TABLE SAVE' command.

Any suggestions as to how to end this process?

Thanks!

This message has been edited. Last edited by: Kerry,

Is the still occupied agent really the agent that ran your process?
Is it also still consuming cpu time?
What does the last command executed tell you?
Have you switched on tracing and looked at the resulting file(s)? If so, did it tell you what it was doing?
Is the request accessing a relational table? If so, has the transaction been released by the dbms?

There are probably many more questions that can be asked but the above ones make a nice start.

micro
you can go to the server console
and kill the agent.
do you know how to do that?
usually its port 8121 http://yourserver:8121/ibi_apps/webconsole
then workspace, Monitor, data services(agents)
click right on the agent, and hit kill.
Why its happening..thats another story. its happened to me, when i've run some long job, live not deferrred, and logged out of mre.
and lo and behold the job finishes but the agent hangs.
eh bien! i just kill it and go home.

quote:

on

I wonder what would happen if you removed the -EXIT and let it finish its 'natural' course.

You could try -QUIT instead to try a hard stop

GamP: Yes, it is still that same agent. No CPU time is being consumed. The IO, CPU and Mem Usage numbers do not change once the extract completes. Trace on gives no clues. Last request is a TABLE of a HOLD file which was built from a relational table.

Susannah: I can kill the agent (Lord knows I've done that enough times in my career!) but this will eventually be a scheduled Reportcaster job and I don't want the agent alive and kicking.

KenFR: Tried your suggestions already to no avail.

Any other thoughts?

Try:

-RUN
-QUIT FOCUS

That should stop the music.

j.gross: The -QUIT FOCUS line worked!

Thanks everyone!