Automic Workload Automation

Hi,

I'm using the UC4 version 11.2 and java console interface. I have the flow as below:

Start --> job1 --> job2 --> end

The job1 starts at 9:00 PM. It will complete intentionally at 11:00 PM, it can be shorter or longer.

The job2 starts at 11:00 PM if the job1 completed. Job1 is the dependency of job2.

So,

• If job1 completes on time, job2 will start
• if job1 completes before 11:00 PM, job2 needs to wait until to 11:00 PM to start.
• if job1 completes at 11:30, job2 needs to start immediately.

Do we have any feature to set 2 conditions on job2: dependency and start time?

Hi

I would use preconditions of job2 to fulfill those requests: Automic 

cheers, Wolfgang

Hi Wolfgang,

Can we use the "Earliest" tab? I think It can be an option.

Hi

Yes it could be an option but using Earliest you are not able to trigger on Status "Waiting for host" only.

That means if the job is currently running and exceeds max runtime it will be chancelled as well.

Plan B would be using an agent group for your job.

Another possibility would be checking in Prescript of your JOBS, if the Agent is up and running using SYS_HOST_ALIVE

if not, you can read an alternative agent from a VARA or out of an agent group.

cheers, Wolfgang

I read here about earliest tab Automic  I think it meet with the requirement.

but using Earliest you are not able to trigger on Status "Waiting for host" only.

That means if the job is currently running and exceeds max runtime it will be chancelled as well.

--> how can we know max runtime for this? and "waiting for host"?

This is an excerpt from that article:

For example: 
The task that is shown above can first begin at 12:00 o'clock on the workflow's activation day. If it is activated later than 12:00 o'clock, this task starts immediately provided that all other preconditions have been met.

If you do not check the job state, earliest tab is your choice.

--> how can we know max runtime for this?

Thats a setting you must specify

--> "waiting for host"?

I would prvent this by script - see suggestion above

cheers, Wolfgang

We don't specify the max run time, just estimation. The job state is defined in the dependencies with ENDED_OK.

In the example the link of earliest Automic  I can see it can specify the predecessor job MM.DAY.SET.

But in my case, it's same with original job, I cannot add/modify

How can we update it the predecessor job?