03-16-2009
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
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I want to know about job scheduling utilities available in unix. It should not be responsible just for starting the job like in case of cron but should also be able to handle the execution of jobs.
Regards,
Ritesh (1 Reply)
Discussion started by: turlapaty
1 Replies
2. UNIX and Linux Applications
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... (1 Reply)
Discussion started by: singhabhijit
1 Replies
3. Shell Programming and Scripting
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
4. UNIX for Advanced & Expert Users
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. Shell Programming and Scripting
Hi,
I have scheduled two jobs, 2nd job is depend upon the 1st one.
Once the 1st job will finish the execution , then only 2nd job will start execution.
Both the jobs present in the cron file.
Please reply as earleist because this is one my requirement, where should put the condition,... (1 Reply)
Discussion started by: rajesh08
1 Replies
6. UNIX and Linux Applications
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
7. Shell Programming and Scripting
Hi All,
I have a script which is scheduled in the Cron. It runs every 10th and 40th min of an hour.The job has to run every 30min.
But, I do not want to have the 00:10 MST run every day.Is it possible to exclude that run from the schedule?Or any other way through which i can run my job every... (4 Replies)
Discussion started by: sparks
4 Replies
8. Shell Programming and Scripting
I am writing a script to run the jobs on demand, like when i am done with some online updates i want to run the sheduler script to schedule the job 1 by 1. It executes the following way
sched.ksh <data file>
The data file will have the jobs to be executed in the order to be executed and... (1 Reply)
Discussion started by: nw2unx123
1 Replies
9. Shell Programming and Scripting
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. Shell Programming and Scripting
Hi Friends,
There is an Autosys scheduled job that runs on the second day of the month, and it is using the Business day calendar.
So when the month starts on a weekend or there is a holiday at the beginning of the month the second business day and second day of the month obviously do not... (1 Reply)
Discussion started by: Aditya_001
1 Replies
LEARN ABOUT CENTOS
sge_shepherd
SGE_SHEPHERD(8) Sun Grid Engine Administrative Commands SGE_SHEPHERD(8)
NAME
sge_shepherd - Sun Grid Engine single job controlling agent
SYNOPSIS
sge_shepherd
DESCRIPTION
sge_shepherd provides the parent process functionality for a single Sun Grid Engine job. The parent functionality is necessary on UNIX
systems to retrieve resource usage information (see getrusage(2)) after a job has finished. In addition, the sge_shepherd forwards signals
to the job, such as the signals for suspension, enabling, termination and the Sun Grid Engine checkpointing signal (see sge_ckpt(1) for
details).
The sge_shepherd receives information about the job to be started from the sge_execd(8). During the execution of the job it actually
starts up to 5 child processes. First a prolog script is run if this feature is enabled by the prolog parameter in the cluster configura-
tion. (See sge_conf(5).) Next a parallel environment startup procedure is run if the job is a parallel job. (See sge_pe(5) for more infor-
mation.) After that, the job itself is run, followed by a parallel environment shutdown procedure for parallel jobs, and finally an epilog
script if requested by the epilog parameter in the cluster configuration. The prolog and epilog scripts as well as the parallel environment
startup and shutdown procedures are to be provided by the Sun Grid Engine administrator and are intended for site-specific actions to be
taken before and after execution of the actual user job.
After the job has finished and the epilog script is processed, sge_shepherd retrieves resource usage statistics about the job, places them
in a job specific subdirectory of the sge_execd(8) spool directory for reporting through sge_execd(8) and finishes.
sge_shepherd also places an exit status file in the spool directory. This exit status can be viewed with qacct -j JobId (see qacct(1)); it
is not the exit status of sge_shepherd itself but of one of the methods executed by sge_shepherd. This exit status can have several mean-
ings, depending on in which method an error occurred (if any). The possible methods are: prolog, parallel start, job, parallel stop, epi-
log, suspend, restart, terminate, clean, migrate, and checkpoint.
The following exit values are returned:
0 All methods: Operation was executed successfully.
99 Job script, prolog and epilog: When FORBID_RESCHEDULE is not set in the configuration (see sge_conf(5)), the job gets re-queued.
Otherwise see "Other".
100 Job script, prolog and epilog: When FORBID_APPERROR is not set in the configuration (see sge_conf(5)), the job gets re-queued. Oth-
erwise see "Other".
Other Job script: This is the exit status of the job itself. No action is taken upon this exit status because the meaning of this exit
status is not known.
Prolog, epilog and parallel start: The queue is set to error state and the job is re-queued.
Parallel stop: The queue is set to error state, but the job is not re-queued. It is assumed that the job itself ran successfully and
only the clean up script failed.
Suspend, restart, terminate, clean, and migrate: Always successful.
Checkpoint: Success, except for kernel checkpointing: checkpoint was not successful, did not happen (but migration will happen by
Sun Grid Engine).
RESTRICTIONS
sge_shepherd should not be invoked manually, but only by sge_execd(8).
FILES
sgepasswd contains a list of user names and their corresponding encrypted passwords. If available, the password file will be
used by sge_shepherd. To change the contents of this file please use the sgepasswd command. It is not advised to change that file manu-
ally.
<execd_spool>/job_dir/<job_id> job specific directory
SEE ALSO
sge_intro(1), sge_conf(5), sge_execd(8).
COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions.
SGE 6.2u5 $Date$ SGE_SHEPHERD(8)