02-13-2007
Job scheduler without using cron
Hi,
I want to schedule the scripts/batches to run simultaneously. I had all the information in the config (flat)file, which contains script name, time, dependency, path, priority and status etc.,
I want to run the jobs parellelly and some jobs are required to give the input. How can I do this? All these to be logged also.
I don't want put this job as a cron.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi Gurus,
I'm looking for a real Jobs Scheduler Agent-based.
My customer is using cron, but need something a little bit clever, where
you could configure chain of process ("script x will run if script y is
finished", etc). Of course I know solutions like control-M (from BMC... (1 Reply)
Discussion started by: maquinte
1 Replies
2. Shell Programming and Scripting
Do any one know any way of scheduling jobs on Unix without using cron as thats not supported within the company (5 Replies)
Discussion started by: Yziee
5 Replies
3. Solaris
I have akorn shell job that I can run manually but when I run via cron it starts and finishes, but does not do what it does when I run it manually.
Any ideals on why this is happening? (3 Replies)
Discussion started by: CAGIRL
3 Replies
4. UNIX for Dummies Questions & Answers
Hi All,
Pardon me if this turns out to be a dumb question. But I am trying to schedule a cron job for a my script which takes input options. So an entry in crontab would be something like:
1 * * * * run_report.sh -o out.csv -m monthly -e somename@email.com > cron_output.log 2> cron_error.log... (3 Replies)
Discussion started by: trueharsh
3 Replies
5. Shell Programming and Scripting
Hi All,
I have a script which will restart some web server and bring it up again. For that I need to retrieve 3 password from CyberArk (Cyber-Ark - Wikipedia, the free encyclopedia) vault.
My question is:
Is this possible to schedule the script through cron and automatic password... (0 Replies)
Discussion started by: saps19
0 Replies
6. Shell Programming and Scripting
Dear All.
I have a scripts which does many task like house keeping, moving file to different location and loading the data into oracle.
I run this scripts daliy manually , I decided to put it into cron. I have put the scripts into crantab but the behaviour of the scripts have changed. it... (2 Replies)
Discussion started by: guddu_12
2 Replies
7. UNIX for Advanced & Expert Users
Hi Experts,
I am new to Autosys. I created a Autosys box job to run at 10 AM daily. As scheduled, the job starts on time.
There is another box job inside the box. I have scheduled it to run at 11 AM but it kicks off automatically with the main job at 10 AM.
insert_job: Main-job ... (2 Replies)
Discussion started by: pk_bohra
2 Replies
8. Red Hat
I am trying to schedule a script in Linux to between 8th and the 31st of each month on Sundays @ 6:50 only and i scheduled it as follows:
50 6 8-31 * 0 ksh /home/cpac/SPID_Files/GetFiles.ksh
Which did it run on the 8th on Saturday instead of only Sundays !!! (3 Replies)
Discussion started by: mrn6430
3 Replies
9. UNIX for Advanced & Expert Users
Hi team,
O.S : Oracle Linux
Issue : I am facing issue when running OS watcher script from cron scheduler. But when i run the same command manually, its getting executed.
Note : I have to press " Enter " button to get out of the blank screen when I execute the script manually.
Below is... (1 Reply)
Discussion started by: madhuraju
1 Replies
10. UNIX for Beginners Questions & Answers
Good Afternoon,
I have a sh script that the admin added to the cron schedule.
It runs fine when I run it manually...but not when scheduled.
I added the path that is found for my user to the script. Still no luck.
Any ideas what I should look at?
Thanks
Marty (8 Replies)
Discussion started by: MSpeare
8 Replies
LEARN ABOUT OSF1
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - Queue description file for at, batch, and cron commands
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron or specifies other characteristics for cron. Each noncom-
ment line in this file describes either one queue or a cron characteristic. Each uncommented line should be in one of the following for-
mats.
q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode
The fields in these lines are as follows: The name of the queue. Defined queues are as follows: The default queue for jobs started by at
The default queue for jobs started by batch The default queue for jobs run from a crontab file
Queues d to z are also available for local use. The maximum number of jobs that can be run simultaneously in the queue; if more
than njob jobs are ready to run, only the first njob jobs will be run. The others will be initiated as currently running jobs ter-
minate. The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser. The number of seconds to
wait before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide
limit of jobs executing (max_jobs) has been reached. The maximum number of active jobs from all queues that may run at any one
time. The default is 25 jobs. Logging level of messages sent to a log file. The default is 4. Defined levels are as follows:
level-code level
0 None
1 Low
2 Medium
3 High
4 Full
Lines beginning with # are comments, and are ignored.
EXAMPLES
The following file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run
with a nice value of 20. If a job cannot be run because too many other jobs are running, cron will wait 60 seconds before trying again to
run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2. If a job cannot be run
because too many other jobs are running cron will wait 60 seconds before trying again to run it. b.50j20n60w
The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will log
all messages to the log file. The last two lines are comments that are ignored. max_jobs=25 log=4 # This is a comment # And so is this
FILES
Main cron directory The default location for the queue description file.
RELATED INFORMATION
Commands: at(1), cron(8), crontab(1), nice(1)
delim off
queuedefs(4)