I need to extract the list of Jobs running with a specific calendar in Autosys.
Is there any autosys command to extract this information?
Thanks,
Bob
There is no CLI for that. You can only do by DB select or via WCC
Related
(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
We have a SQL table that is populated by some jobs. The table structure is
ID Date Name
1 6/10/2017 sales
2 6/10/2017 marketing
3 6/17/2017 Loans
We recieve files on our server from vendors weekly.
For instance we received a file called Sales_6/10/2017.txt.
My autosys job need to watch this file and search it within table above. If the date and name matches in table then only further my job should run. If it doesn't find the entry in table then it must not run.
i am not able to figure out how to get this file watch along with checking with entry in table.
Autosys can handle the file watcher, but it cannot execute a SQL query as a condition for starting a job. You should put that functionality into a shell script that is called by Autosys when the file arrives. The shell script should perform the query and then decide whether to proceed, depending on the results.
How do I stop my running Control-M jobs from executing? Basically I want them to stop running, remove them from the Monitoring view.
in Control-M version 8 you can un-schedule a whole folder by just selecting Manual Order in Order Method. if it's just one specificjob, you can edit the scheduling properties of that job directly and select Manual Order too.
Right click on your job and select "Hold". Now more actions/delete should be available
at controlM V7 and V8/9 open Desktop/Planning environment, Load the schedule table, select the job individually, at Scheduling tab un-select Months, Verify and Checkin. This method is to disable jobs to load and execute( obviously will not show at monitoring window).
Note: Always at planning load the scheduling table, not individual jobs or subapplications. This will overwrite CtmServer DB.
I have a question with regards to batch processing in Microsoft Dynamics AX 2012. I have created a Recalculate stock batch job and assigned it to a batch group. However, when I looked at the tasks inside the batch job, I noticed that some of these tasks were NOT using the batch group I assigned but the empty batch group. Why is this please?
It appears to be because it creates batch task helpers from \Classes\InventCostTaskController\createBatchTasks which might use the batch group setup on inventParameters.CloseBatchGroupId which is on the Inventory Parameters form on the general tab.
The batch you created just starts the tasks.
I want to make a report of start and end times of a Autosys job from last three months.
How can i get it. Do i need to check archived history or logs?
If yes, please lemme know the details.
TIA
Autosys internally uses Oracle or Sybase database. As long as the data is available in the DB you can fetch it using autorep command. To get past run time use -r handle.
For example: autorep -J JobA -r -30
The above will give you last 30th run time for the job.
However, due to performance bottleneck that may arise due to historical data in the DBs the DBAs generally purge the data after a while. I have seen period of 1 day to 7 days based on the number of the jobs and database instance power.
Other approximate way would to be use the log files created by autosys if the option stdout is specified with unique filenames.
For example: you can have the attribute as std_out: $JOB_NAME.out.date +%m.%s
In this case the log file will be created as soon as the job starts which you can get from the filename using text function on unix,etc.
For the end-time, you can use the last modified time - this is where the approximate part comes in as the time would depend if your job had an echo to the log file or not. It can either be close or far based on the command of the script.
This method will not let you know the times for the box jobs as they never have a log attribute, for that you can depend on the first job in the box.