autosys

问题 I have tried with Jan MNTHD#1.... |Jan MNTHD#14|Apr MNTHD#1... so on, but autosys has date condition limitation for 255 chars. Can you please suggest me. 回答1: Autosys CYCLE and EXTENDED CALENDAR can he helpful here. Step 1: Create a CYCLE, to define a range. cycle: YEARLY_QUARTER start_date: 01/01/1972 end_date: 01/14/1972 start_date: 04/01/1972 end_date: 04/14/1972 start_date: 07/01/1972 end_date: 07/14/1972 start_date: 10/01/1972 end_date: 10/14/1972 Note: To set the cycle to repeat every

问题 What is the difference of putting job on hold and putting it on ice? 回答1: There are two notable differences between ON HOLD and ON ICE jobs, which dictate when to use them. When an ON_HOLD job is put off hold, it runs, if it's starting conditions are satisfied, while an ON ICE job will not run, after putting into OFF ICE, even if it's starting conditions are met. It will only run, when it's starting condition will reoccur. For example, if you have a job which starts your Java services at 3.00

问题 In shell script, echo can be used to return values from functions. But, if those functions want to print some messages. Then, this can be done by redirecting it to error stream. Below is a simplified example :- #this is a function that returns a value, as well as #print some messages function logic(){ echo >&2 "start of logic" echo >&2 "perform logic, to get value" echo "ok" } function smain(){ local result=$(logic) echo "result is >$result<" if [ "$result" == "ok" ];then echo "script

问题 In shell script, echo can be used to return values from functions. But, if those functions want to print some messages. Then, this can be done by redirecting it to error stream. Below is a simplified example :- #this is a function that returns a value, as well as #print some messages function logic(){ echo >&2 "start of logic" echo >&2 "perform logic, to get value" echo "ok" } function smain(){ local result=$(logic) echo "result is >$result<" if [ "$result" == "ok" ];then echo "script

问题 We have an Autosys job (let's call it job_a) that has a 3am time dependency and is also supposed to await successful completion of a mainframe job (job_m, which in our case is always successful). Job_m is run via the OPC scheduler on the mainframe, which communicates job completion to Autosys. It can run any time between 2am and 6am. My understanding of how Autosys works is that it writes an entry into a table in its database when job_m completes, and when job_a checks its dependencies, it

问题 What happens when you start an Autosys job that is already running? Is the start ignored or is another instance of the job created and executed in parallel with the already-running job? I know for a fact that issuing a FORCE_STARTJOB against a running job results in an error saying that the job is already running and that FORCE_STARTJOB has no effect, but I'm not sure how a STARTJOB is handled when the job is already running. 回答1: I found out that an already running job ignores any FORCE

问题 I got 4 jobs: 1, 2, 3, 4. 2's condition: s(1); 3's condition: s(2); 4's condition: s(1) & s(2) & s(3) all these jobs are daily jobs the first day is ok. the second day, the 4th job triggered mutilple times : I think when 1 success, and the status of 2 and 3 are still 'success'(the last days status), so the job 4 triggered, then 2 success, triggered again... so is there any solution for this? becase I only want these condition is based on the current day's result. 回答1: This is already answered

问题 I'm currently working with a process that imports a CSV file into our database, then produces and zips an output flat file that details the entries added that hadn't existed before or were changed. At the moment, if the process is run in Visual Studio or from the .exe file, everything goes off without a hitch, and we are provided the files and can verify the changes to the database. If, however, the process is called through Autosys (our workload automation tool), we're given the output file

问题 Currenty I have requirement in my enviroment for the autosys email notifition. Requirement: If the job runs more than the specified time it should trigger an email. What I am trying is using max_run_alam, but I am not successful. Lets say i have a job that runs for 10mins(lets say the time as 10.00). i set max_run_alarm as 3. i should get an email at 10.03 where i can goahead and see why the job is running more than the max_run_alarm. if i use max_run_alarm i am able to see in the logs