Hello,
Thanks for your help guys. In - fact when you need to create, let's say 300 jobs (in my case) and a customer is asking those jobsto be set ON_ICE, the main problem is with the file-watchers, or jobs having pretty intensive schedule.
If some of the jobs start, you need to terminate them first, if they have already started and so on, which leads to additional work.
So I think we're going to an improvement/feature suggestion here.
I am suggesting a flag/string in a job definition that is setting the job in a desired status upon committing it to the AutoSys DB.
/* ----------------- SOMESAMPLEJOB001 ----------------- */
insert_job: SOMESAMPLEJOB001 job_type: c
box_name: SOMESAMPLEBOX
command: $${EPICHOST_SHELLSCRIPTS}/SCRIPT.sh FLUSH
machine: EPICHOST
owner: noob@EPICHOST
permission: gx,ge,wx,we,mx,me
condition: s(SOMESAMPLEJOB000)
description: "Transfert du fichier de la machine UNIX vers le bridge"
std_out_file: $${AUTOSYS_LOG_PATH}/SOMESAMPLEJOB001.out
std_err_file: $${AUTOSYS_LOG_PATH}/SOMESAMPLEJOB001.err
max_run_alarm: 20
alarm_if_fail: 1
creation_status_use: 0/1
creation_status: SUCCESS / ON_HOLD / ON_ICE...TERMINATED(why not, might be useful for DEV purposes )
What do you think?
Have a great day And thanks again for the help.
BR,
Iriney