Automic Workload Automation

Hi Everybody,

I need to cancel a job (and the calling JOBP) if it stays more than 1 hour in the Waiting for Host status. Is there a way to do it from within the job/jobp? I know it is doable by external job/p which will monitor those jobs and do the action needed.

Thanks

Hesham

Hi

its easier using preconditions for this adn I believe it should work using time since activation and user defined (prior write object status into an object variable)

cheers, Wolfgang

Yes, as @Wolfgang Brueckler  , mentioned, pre-conditions is the best way to handle this. Or you could have a unix JOBS with AE scripting which checks for the job's status every x minutes and cancel it when it reaches the threshold time, assuming your AE version supports it.

Well, I tried that already but the &$STATUS# object property is not available in precondition, only in postcondition. Also, even I stated the time since activation to be 2 min in the precondition, the job goes into "Waiting for host" status and stays there. Thanks for your support.

Hello,

Can you not just check the agent is with us in the pre condition loop and then if not kill the job?

:PRINT ARE WE WAITING FOR HOST ?

:PRINT &$AGENT#

:IF SYS_HOST_ALIVE("&$AGENT#") = "N"
: PRINT OH DEAR NOT ALIVE.....
: STOP
:ENDIF

Cheers,

Dan

This option as well, but I want to take advantage of the job resumes if the agent is back to live in less than an hour.

Hello,

I cannot test, this but can you just add a while loop and WAIT 600 in the loop and then exit the loop after 6 iterations/checks for the agents status?

Please ignore if this is nonsense?

Cheers,

Dan

I will try this as it is the closest solution for what I need. Thanks

Hi

here is a very simple solution:

Workflow with a job in it, Workflow Process contains the Agent the job is running on:

:SET &WIN03_ACT# = SYS_HOST_ALIVE(V112_WIN03)

Put &WIN03_ACT# into Variable&prompts tab to define an object variable

Precondition of the job in the workflow:

cheers, Wolfgang

Hi Wolfgang,

Thanks for the solution. I believe it will work perfectly to catch jobs waiting for stopped Agent for XX minutes (3 min in the example you provided) which is 60% of the time. But if the Agent is started after 2 minutes, the conditions above will not catch that as the check for agent is done once in the beginning and &WIN03_ACT# is never re-evaluated. Please correct me if I have wrong understanding.

Hesham

Hi

**** you ' re right!

We have to include a seperate ELSE clause in the condition:

CHECK PROCESS with the agent binary ucxjwx6.exe

this should work.

cheers, Wolfgang

Four star reply!

Did you self-censor that, or did a word filter hit you? Asking for a friend ...

Thanks  I believe this should work. Last question, how to make it re-evaluate both condition (process is running and time since activation is less than 30 min). Here is the precondition I made:

IF process ucxjwx6.exe on TEST (login with LOGIN.TEST) is running

   FINALLY run task

ELSE

   IF more than 00:30 hass passed since activation

      FINALLY skip job

   ELSE

       redo evaluation in 1 minutes

Only the inner IF will be re-evaluated or both. It is not clear in the documentation.

Thanks again,

Hesham

I changed the sequence to be

IF process ucxjwx6.exe on TEST (login with LOGIN.TEST) is running

   FINALLY run task

ELSE

   IF more than 00:30 hass passed since activation

      FINALLY skip job

redo evaluation in 1 minutes

now the re-evaluation is belonging to the ELSE of the first IF. But I got the following result (repeated hundred times) and the inner IF is not reached:

2018-05-30 18:28:16 - IF process ucxjwx6.exe on TEST (login with LOGIN.TEST) is running 2018-05-30 18:28:16 - U00021304 Condition/Action line '1': Agent 'TEST' not started. 2018-05-30 18:28:16 - U00020411 The command 'EXIT' in 'XC_INC.CONDITION.CHECK_PROCESS', line '00076' stopped the generation of this task.

Seems that this CHECK PROCESS can't be evaluated as it checks the process of the agent itself if it is down cause there is no agent to connect through.
Any possible workaround?

Thanks
Hesham

Hi

this is becoming a bit tricky :-)

what about this attemt (not tested myself)

IF process ucxjwx6.exe on TEST (login with LOGIN.TEST) is running

   FINALLY run task

ELSE

    IF more than 00:30 hass passed since activation
    
        IF process ucxjwx6.exe on TEST (login with LOGIN.TEST) is running
        FINALLY run task
    ELSE
    
        FINALLY skip job

    redo evaluation in 1 minutes

cheers, Wolfgang

Hi Wolfgang,

Well, the problem is not with the structure. The first IF is never evaluated. The first IF has two parts:

1- connect to agent TEST using LOGIN.TEST

2- then Check if the process ucxjwx6.exe.

So, as the agent itself is down the connection will never happen and the process will never be checked. so the above structure will hang in the outer IF.

Cheers, Hesham

****.... not good.

Thanks, XYZXYZ forum Software...

I meant DxAxMxN - and no silly software will prevent me from writing nmad.

D1a2m3m4n

not anyone...

D   A    M    N

I'll think if theres another solution...

cheers, Wolfgang

Think I did it..

finally...

I used a precondition - checking if agent is up.

If not, check if more than 4 (in your case 60) minutes are over since activation.

Then re-evaluate.

In my test env it worked fine.

pls test.

cheers, Wolfgang

Thanks Wolfgang. It working perfectly

You ' re welcome :-)