Sponsored Content
Full Discussion: Script execution information
Top Forums Shell Programming and Scripting Script execution information Post 302079002 by manthasirisha on Thursday 6th of July 2006 08:51:11 AM
Old 07-06-2006
Thank you so much thestevew and grial.. for your inputs!

here's my code:


script1:
#! /bin/ksh

BBLOG="$HOME/bb_quickview/Log"
datestamp=`TZ=EDT+24 date +%m%d%y`
retcode=$?

if [ `ps -e | grep script1.ksh` ]
then
stat=`ksh -x script2.ksh` >> $BBLOG/$datestamp.log 2 >&1
echo retcode
else
echo "Script2 already running"
exit 1
fi


Script 2:
it's 300 line script that fetches different values by connecting to database (Oracle) and writes all these values into an output file that is later emailed.

This much is achieved by means of functions:

func_read_configfile ##to read the configuration variables

func_connectstring ##to read connection information

get_counts ## to fetch the desired values from DB and mail them

recheck_counts ## to handle exceptions if counts are not available in the database

archive ## to zip the output file and save in Archive directory

cleanup ## to remove any temporay files

pls note that I cannot paste all lines of the code here.. coz i'm writing from a browser that's connected with a server of restricted access. I, in no way, can copy-paste from my script.

The whole issue before me is to see how the script2 runs, what happens in each of these functions, what values are assigned to variables (if any) in the functions and thus save all this information.. kind of a "LOG" which helps in tracing errors if anything fails.


ERRORs / Concerns: When I run script1.ksh i see all the debug info on the STDOUT rather than in the LOG i want to create. I only am able to redirect the error messages that Script2 generates into the LOG.. :-S


I hope this would suffice to pour in your suggestions.

Lots of Thanks!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

pb with script execution

Hello, Can somebody tell me the differnce between a call of a ksh with the dot : >. script.ksh and the call without the dot: >script.ksh In my script I have writen a test for the number of parameters: if then echo 'Usage : '$0 exit 1 fi as my script doesn't need any... (3 Replies)
Discussion started by: Cecile
3 Replies

2. Shell Programming and Scripting

help on script execution

Hi, Please help me on the below code of line of what it actually does ${Script_dir}/scrip1.sh & export script1_pid=$! ${Scipt_dir}/script2.sh & export script2_pid=$! ${Scrip_dIR}/script3.sh & export script3_pid=$! wait ${script1_pid} //could u tell me wht this... (8 Replies)
Discussion started by: sussane
8 Replies

3. Shell Programming and Scripting

Script to carry-over the script execution to another system

The situation is like this. If I need to know the parameters of all the unix servers connected to a common network, is it possible to get all the parameter details of all the system with the help of a script written in one server?? Can a script be written like that ? Let me give some... (3 Replies)
Discussion started by: yuvanash
3 Replies

4. Shell Programming and Scripting

Expect Issue Serial Forground Execution vs Concurrent Background Execution

I have an expect script that interrogates several hundred unix servers for both access and directories therein using "ssh user@host ls -l /path". The combination of host/path are unique but the host may be interrogated multiple times if there are multiple paths to test. The expect script is run... (2 Replies)
Discussion started by: twk
2 Replies

5. Shell Programming and Scripting

Script Execution

Hello all, I generally get 6 or more files at location /usr/example.Files listed below er 1 2 3 9.txt er 2 2 3 9.txt er 3 2 3 9.txt er 4 2 3 9.txt abc.next del pa.txt cr ad.txt ps tr as er.txt Now the issue is i need to transfer 2 files (one file is fixed called abc.next) at a... (12 Replies)
Discussion started by: j_panky
12 Replies

6. UNIX for Advanced & Expert Users

SSH using shell script terminates the script execution

Hello, I am writing a shell script in which i do ssh to remote server and count the number of files there and then exit. After the exit the shell script terminates which i believe is expected behavior. Can some one suggest me a way where even after the exit the script execution resumes. ... (2 Replies)
Discussion started by: manaankit
2 Replies

7. Emergency UNIX and Linux Support

invoke one script based on previous script execution

I am database guy and not very good at shell scripts. I am seeking help to sharp my script coding. I have 5 scripts 1. master script. I use this one to call other four scripts to do database work. 2. db_backup_1 and log_backup_1 3. db_backup_2 and log_backup_2 in master script, I want to... (4 Replies)
Discussion started by: duke0001
4 Replies

8. Shell Programming and Scripting

execution of a script

Hi i have a small script like this $ cat test.sh #!/usr/bin/sh name="ram" echo ${1} set 1 2 3 4 5 6 7 8 9 0 123 o870 echo $9 echo ${12} when i am trying to execute like below i am not getting the output jena samp_perl $ sh test.sh test.sh: This: not found (12 Replies)
Discussion started by: ragilla
12 Replies

9. Solaris

Script on Solaris spawning 2 processes for one shell script execution

Hi, I am having a shell script on Solaris 10 which has a while loop as shown below. #!/usr/bin/ksh # while do sleep 60 done Name of the shell script is coldcentric.sh. I executed script /DATAWAREHOUSE/LOAD/Scripts/coldcentric.sh from a command task in Informatica worklow as... (3 Replies)
Discussion started by: chekusi
3 Replies

10. UNIX for Advanced & Expert Users

Script execution

I need to call a script if the month end falls on Saturday or Sunday (5 Replies)
Discussion started by: bala1985
5 Replies
shell_builtins(1)														 shell_builtins(1)

NAME
shell_builtins, case, for, foreach, function, if, repeat, select, switch, until, while - shell command interpreter built-in commands The shell command interpreters csh(1), ksh(1), and sh(1) have special built-in commands. The commands case, for, foreach, function, if, repeat, select, switch, until, and while are commands in the syntax recognized by the shells. They are described in the Commands section of the manual pages of the respective shells. The remaining commands listed in the table below are built into the shells for reasons such as efficiency or data sharing between command invocations. They are described on their respective manual pages. | Command | Shell alias |csh, ksh bg |csh, ksh, sh break |csh, ksh, sh case |csh, ksh, sh cd |csh, ksh, sh chdir |csh, sh continue |csh, ksh, sh dirs |csh echo |csh, ksh, sh eval |csh, ksh, sh exec |csh, ksh, sh exit |csh, ksh, sh export |ksh, sh false |ksh fc |ksh fg |csh, ksh, sh for |ksh, sh foreach |csh function |ksh getopts |ksh, sh glob |csh goto |csh hash |ksh, sh hashstat |csh history |csh if |csh, ksh, sh jobs |csh, ksh, sh kill |csh, ksh, sh let |ksh limit |csh login |csh, ksh, sh logout |csh, ksh, sh nice |csh newgrp |ksh, sh nohup |csh notify |csh onintr |csh popd |csh print |ksh pushd |csh pwd |ksh, sh read |ksh, sh readonly |ksh, sh rehash |csh repeat |csh return |ksh, sh select |ksh set |csh, ksh, sh setenv |csh shift |csh, ksh, sh source |csh stop |csh, ksh, sh suspend |csh, ksh, sh switch |csh test |ksh, sh time |csh times |ksh, sh trap |ksh, sh true |ksh type |ksh, sh typeset |ksh ulimit |ksh, sh umask |csh, ksh, sh unalias |csh, ksh unhash |csh unlimit |csh unset |csh, ksh, sh unsetenv |csh until |ksh, sh wait |csh, ksh, sh whence |ksh while |csh, ksh, sh Bourne Shell, sh, Special Commands Input/output redirection is now permitted for these commands. File descriptor 1 is the default output location. When Job Control is enabled, additional Special Commands are added to the shell's environment. In addition to these built-in reserved command words, sh also uses: : No effect; the command does nothing. A zero exit code is returned. .filename Read and execute commands from filename and return. The search path specified by PATH is used to find the directory con- taining filename. C shell, csh Built-in commands are executed within the C shell. If a built-in command occurs as any component of a pipeline except the last, it is exe- cuted in a subshell. In addition to these built-in reserved command words, csh also uses: : Null command. This command is interpreted, but performs no action. Korn Shell, ksh, Special Commands Input/Output redirection is permitted. Unless otherwise indicated, the output is written on file descriptor 1 and the exit status, when there is no syntax error, is zero. Commands that are preceded by one or two * (asterisks) are treated specially in the following ways: 1. Variable assignment lists preceding the command remain in effect when the command completes. 2. I/O redirections are processed after variable assignments. 3. Errors cause a script that contains them to abort. 4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari- able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not performed. In addition to these built-in reserved command words, ksh also uses: * : [ arg ... ] The command only expands parameters. * .file [ arg ..Read the complete file then execute the commands. The commands are executed in the current shell environment. The search path specified by PATH is used to find the directory containing file. If any arguments arg are given, they become the posi- tional parameters. Otherwise, the positional parameters are unchanged. The exit status is the exit status of the last com- mand executed. the loop termination test. intro(1), alias(1), break(1), cd(1), chmod(1), csh(1), echo(1), exec(1), exit(1), find(1), getoptcvt(1), getopts(1), glob(1), hash(1), his- tory(1), jobs(1), kill(1), ksh(1), let(1), limit(1), login(1), logout(1), newgrp(1), nice(1), nohup(1), print(1), pwd(1), read(1), read- only(1), set(1), sh(1), shift(1), suspend(1), test(1B), time(1), times(1), trap(1), typeset(1), umask(1), wait(1), chdir(2), chmod(2), creat(2), umask(2), getopt(3C), profile(4), environ(5) 29 Jun 2005 shell_builtins(1)
All times are GMT -4. The time now is 10:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy