Automic Workload Automation

Hi,
I have two jobs  (Job 1 and Job 2) that run on a host group, say with two agents: agent A and agent B.

From time to time Job 1 hangs and it's ended because it exceeded the Maximun Runtime (MRT). Then I need to run Job 2 on the same agent where Job 1 was running and restart Job 1 when Job 2 ends.

If I configure Job 2 to be activated by Job 1 in the General-> Running -> MRT section it may run on a different agent. The same happens when I activate Job 2 in the post condition of Job 1.

Any hints on how to do that?

Best,
Marco

Marco, basically in that case it would be the best to add a specific host instead of a hostgroup to the job you want to run. There is currently no way to force a hostgroup to assign a follow-up task of a task to run on the same host, but it might be a good idea to place this under ideas.automic.com as a feature request.

I know, but that's not possible, we need parallel processing.

I actually solved the problem by:
 1. Setting a variable on the first job of the workflow 

:PSET &ACTUAL_TARGET_AGENT# = &$AGENT#

 2. Using this variable in the pro-process tab of the activated job

:PUT_ATT HOST = &ACTUAL_TARGET_AGENT#

It gave me a hint this post: https://community.automic.com/discussion/6132/set-agent-group-of-a-job-programmatically

I wonder where such feature is documented though.

The solution which is given by Michael_Lowry contains a lot of programming, each of the commands and system variable he is using is documented, but the process itself he is sharing here - which is totally awsome programmed - is an individual code he created based on automic script and variables, so it can not be documented within our documentation. But of course, it would solve your issue, and there should be no issue using it for your purpose.

My question was more about the :PUT_ATT HOST thing.
I could not find where is documented that this variable can be set to fix the agent on which a job will be running. Also, I guess, other variables exist that can be leveraged for different purposes. Do you know where this is in the documentation? It would be an interesting read.
Thanks in advance.

Hi Marco,

here ist the general description of put_att
https://docs.automic.com/documentation/WEBHELP/English/AWA/11.2/AE/11.2/All%20Guides/help.htm#ucaads.htm?Highlight=put_att

and here a list of Attributes (for every executable object) to use with put_att or get_att
https://docs.automic.com/documentation/WEBHELP/English/AWA/11.2/AE/11.2/All%20Guides/help.htm#ucaaal.htm

Further info: there do exist special pre-defined Agent Variables - possibly they can help too:
https://docs.automic.com/documentation/WEBHELP/English/AWA/11.2/AE/11.2/All%20Guides/help.htm#ucabkq.htm?Highlight=agent-variables

For some reason I do not understand, it works for a test workflow but with the real one. The PUT_ATT fails with this error:

Changing the Agent is not allowed because the resources of the agent has already been reserved.

Do you use a promptset variable or object variable in agent definition somewhere before?

The main workflow does when we trigger the job manually.

Marco Tizzoni said:

For some reason I do not understand, it works for a test workflow but with the real one. The PUT_ATT fails with this error:

Changing the Agent is not allowed because the resources of the agent has already been reserved.

execute :PUT_ATT from the PreProcess tab. This error message is typical if you do it from the Process tab.

It's already in the pre-process tab