In your case is the agent still online? If it is, I think you want to modify the 'JOB_TIMEOUT' or 'JOB_PART_TIMEOUT' setting on the job, since it's not the agent connection that's timing out, it's timing out on waiting for whatever you're running to return.
So as long as the agent is online, it will still "chatter" with the console enough to keep the Agent Connection Timeout from triggering?
I will also take a look at the JOB_PART_TIMEOUT, hadn't considered that angle. Thanks.
EDIT: Setting JOB_PART_TIMEOUT to 0 would effectively disable it, is that correct? (Can't find that explicitly stated in the manual, though that's how JOB_TIMEOUT works so I would assume it is the same.)
Message was edited by:
Well, ideally yes - the agent will still be 'chattering' unless for some reason whatever you are deploying prevents that :)
JOB_PART_TIMEOUT=0 should set it to unlimited afaik, though there's another timeout setting in blasadmin for this kind of thing (so jobs don't stay forever) but I can't remember off the top of my head.