Sponsored Content
Full Discussion: Job Runtimes by AWK
Top Forums Shell Programming and Scripting Job Runtimes by AWK Post 302527959 by cgk1983 on Monday 6th of June 2011 06:32:00 AM
Old 06-06-2011
Yes Ahamed
 

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. Shell Programming and Scripting

Job dependent on other job

Hi All I am trying to run one command ie grep but I want it should execute only after the completion of a shell script has finished. eg Following is my script : java -mx64m $JAVA_OPTS -Dant.home=$ANT_HOME -classpath $_CLASSPATH org.apache.tools.ant.Main -verbose -buildfile /opt/bea/wls... (4 Replies)
Discussion started by: pankajkrmishra
4 Replies

4. UNIX for Dummies Questions & Answers

How to insert child job under a box job?

I have this box job and it contains only one job under it which is to load a file. I want to insert a "File Watcher", "Copy File" to it? Have no clue how to do that...any help plzzz... (4 Replies)
Discussion started by: xejatt
4 Replies

5. Shell Programming and Scripting

Need logic for check automated Job work in awk or SED.

I have a Java program which will automatically trigger some scheduled job to update Db or some other work. I am tracking the jobs with log messages and finding out it is properly run or not. I want to write a script to capture it correctly on time. Say Job1 is running on 15, 30, and 45 every... (5 Replies)
Discussion started by: senthilkumar_ak
5 Replies

6. Shell Programming and Scripting

PL SQL Runtimes different in Shell script log

Hi, This run times recorded in UX shell script appears peculiar to me. The PL / SQL stored procedure is called through sqlplus from UNIX shell script and then a log is created with run times recorded. The first set has actually taken 6 Hrs but the recorded time indicates it is only 2 Hrs and... (1 Reply)
Discussion started by: Nanu_Manju
1 Replies

7. Advertise with Us

Looking for job

Hi, i just got laid off :D, not fun, but i have a very wierd feeling. I want to continue my cloud computing exciting work and I am looking for takers. A brief of my skills is 10 years exp in dev client server apps on unix platform using java/c++. 3 years of ruby. last one year of amazon ec2 and... (1 Reply)
Discussion started by: linuxpenguin
1 Replies

8. Shell Programming and Scripting

Script to Start a Job after finding the Old job completed

Hi Experts, I need a script advice to schedule 12 jobs ( SAS Codes execute back ground ). Algorithem: 1. Script checks first job. 2. Finds first job is done; invoke second job. 3. finds second job is done; invoke third job. .. Request you to please assist. (3 Replies)
Discussion started by: Jerald Nathan
3 Replies

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

10. 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
jobs(1) 						      General Commands Manual							   jobs(1)

NAME
jobs - Displays status of jobs in the current session SYNOPSIS
jobs [-l | -p] job_id... [Tru64 UNIX] jobs [-n] job_id... Note The C shell has a built-in version of the jobs command. If you are using the C shell, and want to guarantee that you are using the command described here, you must specify the full path /usr/bin/jobs. See the csh(1) reference page for a description of the built-in command. STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: jobs: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Provides more information about each job listed. This information includes the job number, current job, process group ID, state and the command that formed the job. Displays only the process IDs for the process group leaders of the selected jobs. [Tru64 UNIX] Displays jobs that have stopped or exited since last notified. By default, the jobs utility displays the status of all stopped jobs, running background jobs and all jobs whose status has changed and has not been reported by the shell. OPERANDS
Specifies the jobs for which the status is to be displayed. If no job_id operand is given, the status information for all jobs is dis- played. The format of job_id is described in the Jobs section of the ksh(1) reference page. DESCRIPTION
The jobs utility displays the status of jobs that were started in the current shell environment. When jobs reports the termination status of a job, the shell removes its process ID from the list of those "known in the current shell exe- cution environment". See the Jobs section of the ksh(1) reference page. RESTRICTIONS
The jobs utility does not work as expected when it is operating in its own utility execution environment because that environment has no applicable jobs to manipulate. EXIT STATUS
The following exit values are returned: Successful completion. An error occurred. ENVIRONMENT VARIABLES
The following environment variables affect the execution of jobs: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to affect the format and contents of diagnostic messages written to standard error and informative messages written to standard output. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Commands: bg(1), csh(1), fg(1), kill(1), ksh(1), sh(1p), wait(1) Standards: standards(5) jobs(1)
All times are GMT -4. The time now is 01:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy