(Alert) I am new with autosys.
Our team is using autosys version 11.3.5 in remote server(no access to idash).What we are looking for is , if any job is running for more that its mentioned max run time in JIL script , it should email a report containing details of such jobs to a particular mailbox.
Please provide answer with details.So , that a newbie can understand.if possible please provide with the script as we are on tight schedule .
Thanks in Advance.
You can simply use 1max_run_alarmof Autosys to set the alarm and it will send an email to the email id that you put as a part ofnotification_emailaddress` parameter.
References:
https://wiki.orphicsolutions.com/doku.php?id=autosys:jil
Autosys Email Generation if the job runs more than the time specified
Related
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 triggering that alarm, but I cannot spend all day monitoring the logs to see which job is taking long as i have many jobs. my question is am i using max_run_alarm in the correct way or is there something else i am missing or is there entirely different way for the emails to generate.
There is an added functionality where you can configure the email id where all Autosys notification to be sent out.
Incase of any event such as Job Failure / Termination / Run Alarms etc are notified to that email address.
This is configured by the Autosys Admin or the Scheduling Team which i call them as.
I'm exploring different options to send email notifications when the job is not started before 11:00 PM .
My job type is OS and it is dependent on other job(not owned by me), some time the source job run for long time and causing my job to wait , in this case I would like get a notification as my job is not started .
I could see there is a option in Actions tab --> Notifications before job completion --> when : Job not submitted by time , have different option to specify the time but in the Send notification section Don't have email as destination .
Could you please help me if we have options to send email alert .
This is a common requirement. It can be solved by creating custom shout destinations on the Control-M server. Any custom shout destination will show up in the list in your screenshot.
Custom shout destinations can be configured to send an email to a hardcoded email address among other things.
See following link for more details:
http://documents.bmc.com/supportu/9.0.18/help/Main_help/en-US/index.htm#ShoutDestManager.htm
We have a task that was created in IBM BPM and assigned to a Group.
In case someone from my Group has claimed it, how do I find which user of the group claimed the task?
Thanks,
Bharath
You may use Process Inspector application at /ProcessInspector with a user with administrative privileges.
You may search for and locate your process instance, and then locate the task you're interested in at details panel at the right-hand side. If the task is not yet claimed, you'll see the group name here, or if it's claimed by someone in that group you'll see that user's name.
You can get this info from the REST APIs. If you know the Process ID you can use the task summary REST API: http://host_name:port_number/rest/bpm/wle/v1/process/<process_id>/taskSummary/
Or if you know the Task ID you can use the Task Details REST API: http://host_name:port_number/rest/bpm/wle/v1/task/<task_id>?parts=all
You can test using the IBM BPM REST Test Tool: http://host_name:port_number/bpmrest-ui
When i changed the start time of a coordinator job in job.properties in oozie, the job is not taking the changed time, instead its running in the old scheduled time.
Old job.properties:
startMinute=08
startTime=${startDate}T${startHour}:${startMinute}Z
New job.properties:
startMinute=07
startTime=${startDate}T${startHour}:${startMinute}Z
The job is not running at the changed time:07th minute,its running at 08th minute in every hour.
Please can you let me know the solution, how i can make the job pickup the updated properties(changed timing) without restarting or killing the job.
You can't really change the timing of the co-ordinator via any methods given by Oozie(v3.3.2) . When you submit a job the contents properties are stored in the database whereas the actual workflow is in the HDFS.
Everytime you execute the co-ordinator it is necessary to have the workflow in the path specified in properties during job submission but the properties file is not needed. What I mean to imply is the properties file does not come into the picture after submitting the job.
One hack is to update the time directly in the database using SQL query.But I am not sure about the implications of it.The property might become inconsistent across the database.
You have to kill the job and resubmit a new one.
Note: oozie provides a way to change the concurrency,endtime and pausetime as specified in the official docs.
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 triggering that alarm, but I cannot spend all day monitoring the logs to see which job is taking long as i have many jobs. my question is am i using max_run_alarm in the correct way or is there something else i am missing or is there entirely different way for the emails to generate.
pls advise.
We are using autosys R11 at work. I believe the triggering of emails is already automated in higher versions of autosys, but, in our version, to send automatic emails after a certain time, we create two extra autosys jobs. One autosys job starts at the same time as the job you want to "monitor". This job contains a 'sleep' command. (in your example, the command would be "sleep 180" for the job to run for 3 minutes until completion). The second extra job is the sending of the email and only starts after successful completion of the sleep-job.
To prevent the mail from being send every time the autosys box starts, you have to add your first job as BOX_SUCCESS condition. The sleep-job will run to completion, but the mail-job went from the "ACTIVATED" state to the "INACTIVE" state because the autosys box isn't RUNNING anymore.