This is what it looks like when there *ARE* agents present for a given abl application in PASOE.
Notice that it says "there are no agents available". This is directly contradicted by other evidence (eg. PASOE instance control) which shows all the agent process details for this ABL application. Moreover, when new ABL sessions are initialized in the agent, the PID will come back into the screen again.
It seems that the same "no agents available" message is shown under the "agents" screen under two different circumstances. It is shown when there are actually no agents and it is shown when there is an agent that is running, but there are no ABL sessions within the agent.
It is unfortunate that the OEE console doesn't distinguish the two. It is misleading for it to simply say "no agents". Our agents run all day long. It is necessary for us to trim inactive sessions out of them, to free up memory leaks in badly written ABL code. But we rarely stop the MS-Agent processes altogether. Given that we always expect at least one agent to be running per application, it is a concern when OEE tells us that nothing is running.
When new ABL sessions are initialized in the agent, the PID will come back into the screen again. Very odd...
When new ABL sessions are initialized in the agent, the PID will come back into the screen again. Very odd...