Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Shell script - Finding Autosys job status Post 302588831 by Rksiva on Tuesday 10th of January 2012 04:28:08 AM
Old 01-10-2012
Try this,

Code:
#!/bin/ksh
 
while read line
do
    . <<Path>>
    autorep -j $line
done<Jobs_List.txt

 

10 More Discussions You Might Find Interesting

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

2. Shell Programming and Scripting

autosys job name in the called script

Hi, i have an autosys job 'AUTJOBA' that calls a script script1.sh Now, inside the script i would like to know the autosys job that kicked off this script. When AUTJOBA runs script1.sh, will it set an environmental variable for this shell session that can be accessed within this script? ... (1 Reply)
Discussion started by: ysrinu
1 Replies

3. Shell Programming and Scripting

How to list the Autosys jobs thats in failure status using Shell Script

hello There, I am pretty much new to Shell Scripting and also to AutoSys. I would like to know how to list the Autosys jobs in FA status using shell scripting. I would like to get an email alert as and when any Autosys job fails. Also, it should give the path of the Log file. Could you please... (0 Replies)
Discussion started by: supragna
0 Replies

4. UNIX for Dummies Questions & Answers

How to list the Autosys jobs thats in failure status using Shell Script

Hello There, I am pretty much new to Shell Scripting and also to AutoSys. I would like to know how to list the Autosys jobs in FA status using shell scripting. I would like to get an email alert as and when any Autosys job fails. Also, it should give the path of the Log file. Could you please... (5 Replies)
Discussion started by: supragna
5 Replies

5. Windows & DOS: Issues & Discussions

Autosys unable to set the job to the status of FAILED

Hi The Autosys job that call DOS batch file which in turn calls java and this java program has successful completion though there are series of exception occurred in the data it handles and want the job to be set to Fail in its autosys, how could it be done? a.bat { java sample.class ... (1 Reply)
Discussion started by: muthupus
1 Replies

6. UNIX for Dummies Questions & Answers

Job Status for running shell script

Hello, I am running a shell script whose execution often takes several hours to complete. Is there way I can get some kind of status update as the job is running? Something as simple as the start and the current time stamp. Thanks, Gussi (2 Replies)
Discussion started by: Gussifinknottle
2 Replies

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

8. UNIX for Dummies Questions & Answers

How to findsuccessful job status completion in Autosys, programatically

We are using autosys for job scheduling. How to find successful job status completion in Autosys, programatically. Based on the successful job completion , mail has to be trigeered to Business users. Please help Thanks (0 Replies)
Discussion started by: vkalya
0 Replies

9. Shell Programming and Scripting

Please help me to develop this script for autosys job

:wall:Hi All, I want to build script to force start the list of child jobs under a box. I prepared this below script, but this script need to some bug fix at run time. Please help me to to develop this script. Please let me know if any thing require for this script. Advance thank for all.. ... (3 Replies)
Discussion started by: pradipta_pks
3 Replies

10. Shell Programming and Scripting

Shell script to set trap for finding cron job failures

Unix box: solaris 5.8 Server: IP Need to to set trap for cron job failures by writing a shell script (5 Replies)
Discussion started by: ChandruBala73
5 Replies
read(1) 							   User Commands							   read(1)

NAME
read - read a line from standard input SYNOPSIS
/usr/bin/read [-r] var... sh read name... csh set variable= $< ksh read [-prsu [n]] [name ? prompt] [name]... ksh93 read [-Aprs] [-d delim] [-n nsize] [-N nsize] [-t timeout][-u unit] [vname?prompt] [vname... ] DESCRIPTION
/usr/bin/read The read utility reads a single line from standard input. By default, unless the -r option is specified, backslash () acts as an escape character. If standard input is a terminal device and the invoking shell is interactive, read prompts for a continuation line when: o The shell reads an input line ending with a backslash, unless the -r option is specified. o A here-document is not terminated after a NEWLINE character is entered. The line is split into fields as in the shell. The first field is assigned to the first variable var, the second field to the second vari- able var, and so forth. If there are fewer var operands specified than there are fields, the leftover fields and their intervening separa- tors is assigned to the last var. If there are fewer fields than vars, the remaining vars is set to empty strings. The setting of variables specified by the var operands affects the current shell execution environment. If it is called in a sub-shell or separate utility execution environment, such as one of the following: (read foo) nohup read ... find . -exec read ... ; it does not affect the shell variables in the caller's environment. The standard input must be a text file. sh One line is read from the standard input and, using the internal field separator, IFS (normally space or tab), to delimit word boundaries, the first word is assigned to the first name, the second word to the second name, and so on, with leftover words assigned to the last name. Lines can be continued using ewline. Characters other than NEWLINE can be quoted by preceding them with a backslash. These backslashes are removed before words are assigned to names, and no interpretation is done on the character that follows the backslash. The return code is 0, unless an end-of-file is encountered. csh The notation: set variable = $< loads one line of standard input as the value for variable. (See csh(1)). ksh The shell input mechanism. One line is read and is broken up into fields using the characters in IFS as separators. The escape character, (), is used to remove any special meaning for the next character and for line continuation. In raw mode, the -r, the , and the character are not treated specially. The first field is assigned to the first name, the second field to the second name, and so on, with leftover fields assigned to the last name. The -p option causes the input line to be taken from the input pipe of a process spawned by the shell using |&. If the -s flag is present, the input is saved as a command in the history file. The flag -u can be used to specify a one digit file descriptor unit n to read from. The file descriptor can be opened with the exec special command. The default value of n is 0. If name is omitted, REPLY is used as the default name. The exit status is 0 unless the input file is not open for reading or an end-of-file is encountered. An end-of-file with the -p option causes cleanup for this process so that another can be spawned. If the first argument con- tains a ?, the remainder of this word is used as a prompt on standard error when the shell is interactive. The exit status is 0 unless an end-of-file is encountered. ksh93 read reads a line from standard input and breaks it into fields using the characters in the value of the IFS variable as separators. The escape character, , is used to remove any special meaning for the next character and for line continuation unless the -r option is speci- fied. If there are more variables than fields, the remaining variables are set to empty strings. If there are fewer variables than fields, the leftover fields and their intervening separators are assigned to the last variable. If no var is specified, the variable REPLY is used. When var has the binary attribute and -n or -N is specified, the bytes that are read are stored directly into var. If you specify ?prompt after the first var, read displays a prompt on standard error when standard input is a terminal or pipe. OPTIONS
/usr/bin/read, ksh The following option is supported by /usr/bin/read and ksh: -r Do not treat a backslash character in any special way. Considers each backslash to be part of the input line. ksh93 The following options are supported by ksh93: -A Unset var, and create an indexed array containing each field in the line starting at index 0. -d delim Read until delimiter delim instead of to the end of line. -n nsize Read at most nsize bytes. Binary field size is in bytes. -N nsize Read exactly nsize bytes. Binary field size is in bytes. -p Read from the current co-process instead of standard input. An end of file causes read to disconnect the co-process so that another can be created. -r Do not treat specially when processing the input line. -s Save a copy of the input as an entry in the shell history file. -t timeout Specify a timeout in seconds when reading from a terminal or pipe. -u fd Read from file descriptor number fd instead of standard input. The default value is 0. -v When reading from a terminal, display the value of the first variable and use it as a default value. OPERANDS
The following operand is supported: var The name of an existing or non-existing shell variable. EXAMPLES
Example 1 Using the read Command The following example for /usr/bin/read prints a file with the first field of each line moved to the end of the line: example% while read -r xx yy do printf "%s %s " "$yy" "$xx" done < input_file ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of read: LANG, LC_ALL, LC_CTYPE, LC_MES- SAGES, and NLSPATH. IFS Determines the internal field separators used to delimit fields. PS2 Provides the prompt string that an interactive shell writes to standard error when a line ending with a backslash is read and the -r option was not specified, or if a here-document is not terminated after a NEWLINE character is entered. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 End-of-file was detected or an error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: /usr/bin/read, csh, ksh, sh +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ |Standard |See standards(5). | +-----------------------------+-----------------------------+ ksh93 +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |Interface Stability |Uncommitted | +-----------------------------+-----------------------------+ SEE ALSO
csh(1), ksh(1), ksh93(1), line(1), set(1), sh(1), attributes(5), environ(5), standards(5) SunOS 5.11 18 Dec 2007 read(1)
All times are GMT -4. The time now is 12:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy