06-29-2017
I assume you want to run your script from crontab.
You can store the current job name in a file.
Before you do it, compare it with the old file contents; if different then send mail.
This User Gave Thanks to MadeInGermany For This Post:
5 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Thanks in advance.
i need to kill a unix background running job after that job process completes.
i can kill a job by giving the following unix command
kill -9 processid
how to kill the job after the current process run gets completed ?
Appreciate your valuable help.
... (1 Reply)
Discussion started by: dtazv
1 Replies
2. UNIX for Dummies Questions & Answers
Just spent the last hour cruising the FAQ and doing some searches. I learn best by getting one or two books and just starting from scratch and building up a system. Looks like that's the way most of you recommend getting going anyway. I'm armed with several book titles now, and I'll head off to... (2 Replies)
Discussion started by: Rowan
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I have multiple functions that can be called by any shell script. These functions have inbuilt echo statements to logs their activity into a log file. When I run multiple shell scripts that call these functions, they all log into the same log file and I am not able to differentiate which... (2 Replies)
Discussion started by: new_learner
2 Replies
4. Shell Programming and Scripting
I would like to know the maximum integer that a variable can hold. Actually one of my variable holds value 2231599773 and hence the script fails to process it.Do we have any other data type or options available to handle this long integers? (9 Replies)
Discussion started by: michaelrozar17
9 Replies
5. Shell Programming and Scripting
Hi..
I need to put multiple jobs on ON HOLD in Autosys.. please help me on this.
For Example:
1)ABCD_EFGH_IJKL
2)abcd_efgh_ijkl (2 Replies)
Discussion started by: Maanjesh
2 Replies
proto(4) Kernel Interfaces Manual proto(4)
NAME
proto - prototype job file for at
SYNOPSIS
DESCRIPTION
When a job is submitted to or the job is constructed as a POSIX shell script (see at(1)). The job file is created in as follows:
o creates a header describing the job as an job or a job. jobs submitted to all queues other than queue are listed as jobs. The header
is:
for an job, or
for a job.
o A set of POSIX shell commands is added to make the environment (see environ(5)) for the job the same as the current environment.
o then copies text from the prototype file to the job file, except for special variables that are replaced by other text:
Replaced by the current working directory.
Replaced by the current file size limit (see
ulimit(2)).
Replaced by the current umask (see
umask(2)).
Replaced by the time at which the job should be run,
expressed as seconds since January 1, 1970, 00:00 Coordinated Universal Time, preceded by a colon.
Replaced by text read by
from the standard input (that is, the commands provided to to be run in the job).
o When a job is submitted to queue queue, uses the file as the prototype file if it exists. Otherwise, it uses the file
EXAMPLES
The following file creates commands to change the current directory, file size limit, and umask in the job to their respective values as
they existed when was originally run. These commands are inserted before the commands in the job:
SEE ALSO
at(1), queuedefs(4).
STANDARDS CONFORMANCE
proto(4)