Sponsored Content
Top Forums Shell Programming and Scripting Autosys job scheduling issue, Post 302887355 by Jotne on Friday 7th of February 2014 02:00:58 AM
Old 02-07-2014
You can make a crontab running every day, and then test if its the second day on mont, like this:
Code:
20 0 * * * [[ $(date +%d) -eq 2 ]] && Your script here

It will then only run on date 2 in the month at 12:20 am
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Documentation and books on Autosys Job Control Tool from Autosys

My project uses Autosys. I am new to this product and I don't know where to start from. Q1. Please provide me the link where I can get Autosys documentation Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level) (0 Replies)
Discussion started by: gram77
0 Replies

2. Shell Programming and Scripting

Job Scheduling

I am working on UNIX AIX system, with Oracle OS. We are not supposed to use any tools to schedule our unix shell scripts. Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc. If anyone has worked/ is working... (4 Replies)
Discussion started by: singhabhijit
4 Replies

3. Shell Programming and Scripting

Job Scheduling Issue

Hi Guys, I am new to Unix, Please tell me how to schedule a job to be executed on saturday,sunday and on friday night 8:00 PM onwards. and also how to change the password of oracle user every year through unix? Please help me to resolve this issue... Regards, Mahesh Raghunandanan (1 Reply)
Discussion started by: mraghunandanan
1 Replies

4. UNIX for Advanced & Expert Users

Autosys job scheduling

Hi, I want to schedule a job through Autosys (in Linux server) to run on 1st day of every 3rd month(gap of 90 days). Please someone help me to achive my above requirement Example: Run the sample.sh on 01-Jan-2009, 01-Apr-2009, 01-Jul-2009, 01-Oct-2009. Thanks in advance (4 Replies)
Discussion started by: apsprabhu
4 Replies

5. UNIX and Linux Applications

Job Scheduling (Autosys)

Hello! I will be working with Autosys and I am looking for individuals that have knowledge of this UNIX application. Thank-you! (3 Replies)
Discussion started by: preshe79
3 Replies

6. Shell Programming and Scripting

autosys job configuration for job failure.

We need to configure autosys that when a job fails continously for 3 times, we need to call another job. Is this possible in Autosys, or can anyone advice on the alternative. (2 Replies)
Discussion started by: sangea
2 Replies

7. UNIX for Advanced & Expert Users

Issue while killing the process using autosys job

Hi, I have one autosys job that will retrieve the proccess id's and will kill those processess as follows, pid=`/usr/ucb/ps -auwwxx | grep MAIN |nawk '{print $2}'` kill -9 pid but after executing this particular job, its status is showing as TE(terminated) and the kill process is... (3 Replies)
Discussion started by: Kattoor
3 Replies

8. Shell Programming and Scripting

Autosys job scheduling on specific day

Below is the requirement i am trying to do using auto sysjob. I need to create a JOB or script which will do the below things for me I have a box and there corresponding jobs as below BOX_1 JOB_1 JOB_2 BOX_2--- SU(JOB_2), this will run only on completion (Success) of JOB_2 ... (2 Replies)
Discussion started by: j_panky
2 Replies

9. Shell Programming and Scripting

Job Scheduling

Hi All, I am new to unix and i have a task in front of me. The code part is "android update sdk" . I need to crontab this process. Hence i have written a script that runs the above command and sends a mail once the update is done. The problem with the automation is the installer asks for a... (5 Replies)
Discussion started by: Kashyap
5 Replies

10. UNIX for Advanced & Expert Users

Autosys Job: Job did not start

I have submitted an autosys job and force start it. Autosys hit the job 4 times to restart but it did not start and finally I terminate the job. Any idea why the job did not start. Below is the code I executed. 1214 missun0ap /export/home/bzn97r/develop/dswi/jil$ sendevent -E FORCE_STARTJOB... (0 Replies)
Discussion started by: jnrohit2k
0 Replies
CALENDAR(1)						    BSD General Commands Manual 					       CALENDAR(1)

NAME
calendar -- reminder service SYNOPSIS
calendar [-ax] [-d MMDD[[YY]YY]] [-f file] [-l days] [-w days] DESCRIPTION
The calendar utility processes text files and displays lines that match certain dates. The following options are available: -a Process the ``calendar'' files of all users and mail the results to them. This requires super-user privileges. -d MMDD[[YY]YY] Display lines for the given date. By default, the current date is used. The year, which may be given in either two or four digit format, is used only for purposes of determining whether the given date falls on a Friday in that year (see below). If the year is not specified, the current year is assumed. -f file Display matching calendar files from the given filename. By default, the following filenames are checked for: ~/calendar ~/.calendar /etc/calendar and the first which is found is used. The filename may be absolute. If not absolute, it is taken relative to the directory speci- fied by the CALENDAR_DIR environment variable, if set; otherwise, it is taken relative to the user's home directory. Or, if the -a flag is given, a non-absolute filename is taken relative to each user's home directory in turn. -l days Causes the program to ``look ahead'' a given number of days (default one) from the specified date and display their entries as well. -w days Causes the program to add the specified number of days to the ``look ahead'' number if and only if the day specified is a Friday. The default value is two, which causes calendar to print entries through the weekend on Fridays. -x Causes calendar not to set the CPP_RESTRICTED environment variable. Passing this flag allows users the (somewhat obscure) option of including a named pipe via cpp(1)'s #include syntax, but opens up the possibility of calendar hanging indefinitely if users do so incorrectly. For this reason, the -x flag should never be used with calendar -a. Lines should begin with a month and day. They may be entered in almost any format, either numeric or as character strings. A single aster- isk ('*') matches every month, or every day if a month has been provided. This means that two asterisks ('**') matches every day of the year, and is thus useful for ToDo tasks. A day without a month matches that day of every week. A month without a day matches the first of that month. Two numbers default to the month followed by the day. Lines with leading tabs default to the last entered date, allowing multi- ple line specifications for a single date. By convention, dates followed by an asterisk are not fixed, i.e., change from year to year. The ``calendar'' file is preprocessed by cpp(1), allowing the inclusion of shared files such as company holidays or meetings. If the shared file is not referenced by a full pathname, cpp(1) searches in the current (or home) directory first, and then in the directory /usr/share/calendar. Empty lines and lines protected by the C commenting syntax (/* ... */) are ignored. Some possible calendar entries: #include <calendar.usholiday> #include <calendar.birthday> 6/15 ... June 15 (if ambiguous, will default to month/day). Jun. 15 ... June 15. 15 June ... June 15. Thursday ... Every Thursday. June ... Every June 1st. 15 * ... 15th of every month. *15 ... 15th of every month. June* ... Every day of June. ** ... Every day FILES
The following default calendar files are provided: calendar.birthday Births and deaths of famous (and not-so-famous) people. calendar.christian Christian holidays. This calendar should be updated yearly by the local system administrator so that roving holidays are set correctly for the current year. calendar.computer Days of special significance to computer people. calendar.history Everything else, mostly U.S. historical events. calendar.holiday Other holidays, including the not-well-known, obscure, and really obscure. calendar.judaic Jewish holidays. This calendar should be updated yearly by the local system administrator so that roving holidays are set correctly for the current year. calendar.lotr Important dates in the Lord of the Rings series. calendar.music Musical events, births, and deaths. Strongly oriented toward rock 'n' roll. calendar.netbsd Important dates in the history of the NetBSD project. Mostly releases and port additions. calendar.usholiday U.S. holidays. This calendar should be updated yearly by the local system administrator so that roving holidays are set correctly for the current year. COMPATIBILITY
The calendar program previously selected lines which had the correct date anywhere in the line. This is no longer true, the date is only recognized when it occurs first on the line. In NetBSD 3.0, the calendar command was modified to search the user's home directory instead of the current directory by default. Users desiring the historical behavior should set the CALENDAR_DIR environment variable to ., or use the -f flag. SEE ALSO
at(1), cpp(1), cron(8) HISTORY
A calendar command appeared in Version 7 AT&T UNIX. BUGS
calendar doesn't handle events that move around from year to year, i.e., ``the last Monday in April''. The -a option ignores the user's CALENDAR_DIR environment variable. BSD
August 27, 2009 BSD
All times are GMT -4. The time now is 04:14 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy