04-04-2011
"Run window" should specify the time interval of the job run
Anupdas..
"Run window" should specify the time interval of the job run..
Below exmaple would allow the job to run on every Sunday for every 10 minutes, between 7:30AM and 11:59 PM
days_of_week: su
start_mins: 0,10,20,30,40,50
run_window:"07:30 - 23:59"
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT DEBIAN
globus_gram_protocol_job_state
GRAM Job States(3) globus gram protocol GRAM Job States(3)
NAME
GRAM Job States -
Enumerations
enum globus_gram_protocol_job_state_t { GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDING = 1, GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE = 2,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILED = 4, GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE = 8, GLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDED = 16,
GLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTED = 32, GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_IN = 64, GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUT
= 128, GLOBUS_GRAM_PROTOCOL_JOB_STATE_ALL = 0xFFFFF }
Detailed Description
The globus_gram_protocol_job_state_t contains information about the current state of the job as known by the job manager.
Job state changes are sent by the Job Manager to all registered clients. A client may ask for information from the job manager via the
status request.
Enumeration Type Documentation
enum globus_gram_protocol_job_state_t
GRAM Job States.
Enumerator:
GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDING
The job is waiting for resources to become available to run.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE
The job has received resources and the application is executing.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILED
The job terminated before completion because an error, user-triggered cancel, or system-triggered cancel.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE
The job completed successfully.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDED
The job has been suspended. Resources which were allocated for this job may have been released due to some scheduler-specific
reason.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTED
The job has not been submitted to the scheduler yet, pending the reception of the GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUEST
signal from a client.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_IN
The job manager is staging in files to run the job.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUT
The job manager is staging out files generated by the job.
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ALL
A mask of all job states.
Author
Generated automatically by Doxygen for globus gram protocol from the source code.
Version 11.3 Mon Apr 30 2012 GRAM Job States(3)