Sponsored Content
Top Forums UNIX for Advanced & Expert Users Issue while killing the process using autosys job Post 302535228 by Kattoor on Thursday 30th of June 2011 06:29:10 AM
Old 06-30-2011
Thanks for your reply..

I am not using any sendevent command inside this particular script, but still I am getting the staus as TE. Smilie
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

killing unix job after the job process completes

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

killing a unix job after the job process gets completed

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. Thanks... (7 Replies)
Discussion started by: dtazv
7 Replies

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

4. Shell Programming and Scripting

Killing of a process and send a mail if the process doesnot come up within 2 minutes

Hi Friends, I am new to this forum as well as new to shell scripting. I have a problem here and i need someone to solve this. Let us consider there are two processes(abc & def).There is a script which kills these two processes(i.e killtheprocess abc). Here abc is the argument . There is a... (1 Reply)
Discussion started by: Prince89
1 Replies

5. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies

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

7. Shell Programming and Scripting

Autosys Job

I need to know the list of autosys job that run between given time. I have the following command. job_depends -t -J abc% -F "12/25/2010 03:00" -T "12/26/2010 05:00" Above command will give the list of job that run between time 3 AM and 5 AM. But the it gives me in random order how to... (1 Reply)
Discussion started by: diehard
1 Replies

8. UNIX for Dummies Questions & Answers

Shell Scripts - Killing a job....

Hello all, I need to write a shell script that does the following; Allows you to kill a job,(1) listing only the jobs you own, (2) asks for which job to kill, (3) kills the job and (4) confirms kill... I am not sure if I need to first run the job command and pipe it with kill? Which options... (6 Replies)
Discussion started by: citizencro
6 Replies

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

10. Shell Programming and Scripting

Autosys job scheduling issue,

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
kill(1) 							   User Commands							   kill(1)

NAME
kill - terminate or signal processes SYNOPSIS
/usr/bin/kill -s signal_name pid... /usr/bin/kill -l [exit_status] /usr/bin/kill [-signal_name] pid... /usr/bin/kill [-signal_number] pid... DESCRIPTION
The kill utility sends a signal to the process or processes specified by each pid operand. For each pid operand, the kill utility performs actions equivalent to the kill(2) function called with the following arguments: 1. The value of the pid operand is used as the pid argument. 2. The sig argument is the value specified by the -s option, the -signal_name option, or the -signal_number option, or, if none of these options is specified, by SIGTERM. The signaled process must belong to the current user unless the user is the super-user. See NOTES for descriptions of the shell built-in versions of kill. OPTIONS
The following options are supported: -l (The letter ell.) Writes all values of signal_name supported by the implementation, if no operand is specified. If an exit_status operand is specified and it is a value of the ? shell special parameter and wait corresponding to a process that was terminated by a signal, the signal_name corresponding to the signal that terminated the process is written. If an exit_status operand is specified and it is the unsigned decimal integer value of a signal number, the signal_name cor- responding to that signal is written. Otherwise, the results are unspecified. -s signal_name Specifies the signal to send, using one of the symbolic names defined in the <signal.h> description. Values of sig- nal_name is recognized in a case-independent fashion, without the SIG prefix. In addition, the symbolic name 0 is recog- nized, representing the signal value zero. The corresponding signal is sent instead of SIGTERM. -signal_name Equivalent to -s signal_name. -signal_number Specifies a non-negative decimal integer, signal_number, representing the signal to be used instead of SIGTERM, as the sig argument in the effective call to kill(2). OPERANDS
The following operands are supported: pid One of the following: 1. A decimal integer specifying a process or process group to be signaled. The process or processes selected by pos- itive, negative and zero values of the pid operand is as described for the kill function. If process number 0 is specified, all processes in the process group are signaled. If the first pid operand is negative, it should be preceded by -- to keep it from being interpreted as an option. 2. A job control job ID that identifies a background process group to be signaled. The job control job ID notation is applicable only for invocations of kill in the current shell execution environment. The job control job ID type of pid is available only on systems supporting the job control option. exit_status A decimal integer specifying a signal number or the exit status of a process terminated by a signal. USAGE
Process numbers can be found by using ps(1). The job control job ID notation is not required to work as expected when kill is operating in its own utility execution environment. In either of the following examples: example% nohup kill %1 & example% system( "kill %1"); kill operates in a different environment and does not share the shell's understanding of job numbers. OUTPUT
When the -l option is not specified, the standard output is not be used. When the -l option is specified, the symbolic name of each signal is written in the following format: "%s%c", <signal_name>, <separator> where the <signal_name> is in upper-case, without the SIG prefix, and the <separator> is either a newline character or a space character. For the last signal written, <separator> is a newline character. When both the -l option and exit_status operand are specified, the symbolic name of the corresponding signal is written in the following format: "%s ", <signal_name> EXAMPLES
Example 1 Sending the kill signal Any of the commands: example% kill -9 100 -165 example% kill -s kill 100 -165 example% kill -s KILL 100 -165 sends the SIGKILL signal to the process whose process ID is 100 and to all processes whose process group ID is 165, assuming the sending process has permission to send that signal to the specified processes, and that they exist. Example 2 Avoiding ambiguity with an initial negative number To avoid an ambiguity of an initial negative number argument specifying either a signal number or a process group, the former is always be the case. Therefore, to send the default signal to a process group (for example, 123), an application should use a command similar to one of the following: example% kill -TERM -123 example% kill -- -123 ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of kill: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. EXIT STATUS
The following exit values are returned: 0 At least one matching process was found for each pid operand, and the specified signal was successfully processed for at least one matching process. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: /usr/bin/kill, csh, ksh, sh +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ ksh93 +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |CSI |Enabled | +-----------------------------+-----------------------------+ |Interface Stability |Uncommitted | +-----------------------------+-----------------------------+ SEE ALSO
csh(1), jobs(1), ksh(1), ksh93(1), ps(1), sh(1), shell_builtins(1), wait(1), kill(2), signal(3C), signal.h(3HEAD), attributes(5), envi- ron(5), standards(5) NOTES
sh The Bourne shell, sh, has a built-in version of kill to provide the functionality of the kill command for processes identified with a jobid. The sh syntax is: kill [ -sig ] [ pid ] [ %job ]... kill -l csh The C-shell, csh, also has a built-in kill command, whose syntax is: kill [-sig][pid][%job]... kill -l The csh kill built-in sends the TERM (terminate) signal, by default, or the signal specified, to the specified process ID, the job indi- cated, or the current job. Signals are either specified by number or by name. There is no default. Typing kill does not send a signal to the current job. If the signal being sent is TERM (terminate) or HUP (hangup), then the job or process is sent a CONT (continue) signal as well. -l Lists the signal names that can be sent. ksh The syntax of the ksh kill is: kill [-sig][pid][%job]... kill -l The ksh kill sends either the TERM (terminate) signal or the specified signal to the specified jobs or processes. Signals are either speci- fied by number or by names (as specified in signal.h(3HEAD) stripped of the SIG prefix). If the signal being sent is TERM (terminate) or HUP (hangup), then the job or process is sent a CONT (continue) signal if it is stopped. The argument job can be the process id of a process that is not a member of one of the active jobs. In the second form, kill -l, the signal numbers and names are listed. ksh93 The syntax of the ksh93 kill is: kill [-n signum] [-s signame] job ... kill [-n signum] [-s signame] -l [arg ...] With the first form in which -l is not specified, kill sends a signal to one or more processes specified by job. This normally terminates the processes unless the signal is being caught or ignored. Specify job as one of the following: number The process id of job. -number The process group id of job. %number The job number. %string The job whose name begins with string. %?string The job whose name contains string. %+ The current job. %% %- The previous job. If the signal is not specified with either the -n or the -s option, the SIGTERM signal is used. If -l is specified, and no arg is specified, then kill writes the list of signals to standard output. Otherwise, arg can be either a signal name, or a number representing either a signal number or exit status for a process that was terminated due to a signal. If a name is speci- fied the corresponding signal number is written to standard output. If a number is specified the corresponding signal name is written to standard output. -l List signal names or signal numbers rather than sending signals as described above. The -n and -s options cannot be speci- fied. -n signum Specify a signal number to send. Signal numbers are not portable across platforms, except for the following: 0 No signal. 1 HUP 2 INT 3 QUIT 6 ABRT 9 KILL 14 ALRM 15 TERM -s signame Specify a signal name to send. The signal names are derived from their names in <signal.h> without the SIG prefix and are case insensitive. kill -l generates the list of signals on the current platform. kill in ksh93 exits with one of the following values: 0 At least one matching process was found for each job operand, and the specified signal was successfully sent to at least one matching process. >0 An error occurred. SunOS 5.11 2 Nov 2007 kill(1)
All times are GMT -4. The time now is 09:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy