Sponsored Content
Full Discussion: Autosys job run on Sunday
Top Forums UNIX for Advanced & Expert Users Autosys job run on Sunday Post 302509869 by anupdas on Friday 1st of April 2011 01:18:42 AM
Old 04-01-2011
Autosys job run on Sunday

Hi,

I need to create a autosys job which will run on every sunday at 7:30 AM NY time for each 10 min interval of time.

days_of_week: su
start_mins: 0,10,20,30,40,50
run_window:"07:30"

Is it fine? Please help

Thanks,
Anup
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cron job -- to execute at every first Sunday of every month

Dear all How can I schedule the cronjob to be run sometime at every first Sunday at every month? I have the edit the cronjob every month now, thanks (2 Replies)
Discussion started by: shanemcmahon
2 Replies

2. 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

3. AIX

Crontab job on sunday with two week interval

Hi experts, Please help me to set a backup script run at 6AM on Sunday every two week It means the 1st sunday, run script backup at 6AM the 2nd sunday, skip the 3rd sunday, run script backup at 6AM the 4nd sunday, skip ... so on Thank you so much (4 Replies)
Discussion started by: tan.pham
4 Replies

4. Shell Programming and Scripting

Crontab job to run every sunday

Hello, I wanted to run one of my shell script for every sunday at 5PM. Here is the crontab entry i am using.. 00 17 * * 0 /inventory/update.sh > /inventory/update.log 2>&1 The job is not kicking on sunday at the specified time.. Am i missing anthing? Any help is appreciated... (2 Replies)
Discussion started by: govindts
2 Replies

5. 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

6. UNIX for Dummies Questions & Answers

Run script on every second sunday

I was to schedule a script in a crontab after every 15 days specically on every 2nd Sunday. I know that i can schedule on basis of weekdays, but can it be done by skipping in between???:wall: (5 Replies)
Discussion started by: masquerer
5 Replies

7. 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

8. UNIX for Dummies Questions & Answers

To run ksh script via autosys job without asking password for file transfer

I've K shell script. It will transfer the files from one server to other server using 'SCP' command. While running the script alone as a command line in UNIX ssh terminal its running with out asking password and files are transferred with out asking for password. But by running the script using... (6 Replies)
Discussion started by: maheshbabu
6 Replies

9. Solaris

Job Run Slower using Autosys than running through terminal

Hi All, We run Many jobs evryday using Autosys. Sometimes due to various reason we got to run the job from terminal as well (using nohup). We observed that the job running through terminal(nohup) takes much less time then the autosys (for same job). What can be the possible reason for such... (1 Reply)
Discussion started by: kg_gaurav
1 Replies

10. AIX

cron job on 3rd sunday of every month

Hi, Actually scheduled my test scripts on test severs as shown below. They are supposed to run on 3rd sunday of every month. Unfortunately it ran on 2nd sunday of the month (suspecting that it will run every sunday). I am sorry if I miss something. Could you please let me know if I did any... (1 Reply)
Discussion started by: System Admin 77
1 Replies
job(n)								 Tnm Tcl Extension							    job(n)

__________________________________________________________________________________________________________________________________________________

NAME
job - Invoke Tcl procedures at regular intervals. _________________________________________________________________ DESCRIPTION
The job command provides a convenient mechanism to implement Tcl procedures that are invoked at regular intervals. Jobs are activated from the Tcl event loop. Every job can have arbitrary attributes to store job specific state information between two invocations. These attributes help to avoid global variables in order to keep the Tcl name-space clean. The job scheduler itself relies heavily on the Tcl timer interface which itself depends on the system clock. Moving the system clock back- wards can have the effect that jobs are not activated for the amount of time the system clock was moved backwards. Similarly, moving the system clock forward can have the effect that jobs are activated earlier for the amount of time the system clock was moved forward. JOB COMMAND
The job command allows to create new jobs and to wait for jobs to complete. The job command can also be used to retrieve status information from the job scheduler. job create [option value ...] The job create command creates a new job object. The options can be used to configure the behaviour of the new job. See the config- ure command below for the details. job current The job current command returns the name of the currently running job. An empty string is returned if no job is running. job info The job info command returns a list of all job names. The list will be empty if there are no jobs known in this Tcl interpreter. job schedule The job schedule command invoke the scheduler. This is usually done automatically from the event loop. This command may be used dur- ing long computations since the scheduler is not preemptive. Note, this command can cause arbitrary side effects and should be used with care. job wait The job wait command blocks until all existing jobs have been finished. The command will wait infinitely if there is at least one job left. Events are processed while waiting for the jobs to finish which can have arbitrary side effects. JOB INSTANCE COMMAND
Every job is represented by a job object command which allows to manipulate the job. job# attribute [name [value]] The job# attribute command allows to save job specific data in job attributes. If called without any arguments, all existing attribute names for this job will be returned. If called with a name argument, the current value of the attribute will be returned. Non-existing attributes do not produce an error. Instead, an empty string is returned. Calling the option with a name and a value causes the value to be saved in the job attribute. job# cget option The job# cget command returns the current value of a configuration option. See the description of supported options below. job# configure [option value ...] The job# configure command manipulates configuration options. See the description of supported options below. A list describing all current options is returns if the options argument is missing. job# destroy The job# destroy command destroys the job object. This command forces the object to change into the expired state. The scheduler will cleanup this object the next time it is active. job# wait The job# wait command blocks and processes events until the current job changes into the expired state. JOB OPTIONS
Every job has associated configuration options which control when a job is activated and which Tcl command is bound to the job. -command command The -command option defines the Tcl command that is evaluated whenever the job is activated. -interval time The -interval option defines the time interval between two job activations in milliseconds. -iterations number The -iterations option defines the total number of times that a job is activated. If this value reaches 0, the job will change its state to expired. Note, if the iterations options is never used, it will also have the value 0 but nothing special happens to the job object. -status state The -status option provides access to the current job state. A job is always in one of the states waiting, suspended, running and expired. A job in the expired state will be removed from the system once the scheduler gets activated again. Suspended jobs are not activated by the job scheduler. A suspended job can be resumed by changing its state to running. -time time The -time option returns the number of milliseconds until this job is activated the next time. This option is read-only. SEE ALSO
scotty(1), Tnm(n), Tcl(n) AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl> Tnm job(n)
All times are GMT -4. The time now is 07:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy