A set of LOOK-BACK jobs using the ",0" setting are moving to a new R12 instance, how will it handle the first job run

Products

• CA Workload Automation AE

Issue/Introduction

AutoSys 12.0.x

We plan to migrate from R11 to R12.X. 

Something came up concerning the look-back setup in some of our jobs.

Since the jobs will be running in R12 for the first time after the cutover, will the jobs continue to run in their normal way? 

how will the look-back work if there was no prior job run in the new R12 instance?

 

Environment

Release : 12.1

Resolution

You are moving jobs from one install to another via autorep'ing the jobs' definitions and their statuses, and then jil'ing them into the new instance.

The question is/was if a job has a look-back with a comma zero how will the job behave.

We tested the following.

We jil'ed in the following two jobs:

insert_job: b_peadl_IT_broadcom_raw_daily
job_type: box
status: SUCCESS 

insert_job: b_peadl_IT_broadcom_dq_daily   
condition: s(b_peadl_IT_broadcom_raw_daily,0)
owner: autosys11
permission: gx,wx
max_run_alarm: 0
alarm_if_fail: n
avg_runtime: 27
date_conditions: y
days_of_week: mo,tu,we,th,fr,sa,su
start_times: 
start_mins: 00,05,10,15,20,25,30,35,40,45,50,55

As they are both new jobs neither has any last end time.
When b_peadl_IT_broadcom_dq_daily tries to start based on the
date/time conditions it then checks the conditional dependency.
As the raw job is in a state of SUCCESS and neither job has a last
end time the job does run.