Help to understand the script Post: 302480341

Sponsored Content

Top Forums Shell Programming and Scripting Help to understand the script Post 302480341 by citaylor on Tuesday 14th of December 2010 03:08:36 PM

12-14-2010

Registered User

Code:

# If the user hits Control-C this line of script will be run.  
# My guess is the C_logmsg script function will log the below message somewhere, 
# and then the script will terminate with return code 1
trap 'C_logmsg "F" "CNTL/c OS signal trapped, Script ${G_SCRIPTNAME] terminated"; exit 1' 2
# If the script has a TERMINATE signal sent to it (usually when machines shutdown, etc
# the below line will again log a message using C_logmsg and exit with code 1
trap 'C_logmsg "F" "Kill Job Event sent from the Console, Script ${G_SCRIPTNAME] terminated"; exit 1' 15
#----------------------------------------------------------------------------------------------
# If the shell variable $DEBUG is set...
if [${DEBUG} ]; then
# The shell will turn on its internal debug and verbosity, displaying lots of messages
# to the user who runs the script.
set -xv; # Verbose Trace
fi
# Set the variable DOC_SCRIPTS to the string value of the contents of
# the variable $CONTROL_BASE with "/scripts" concatenated on the end.
# For example if CONTROL_BASE="/home/user1" then
# DOC_SCRIPTS would now equal "/home/user1/scripts"
typeset DOC_SCRIPTS=${CONTROL_BASE}/scripts
# Set the variable DOC_ARCHIVE to the string value of the contents of
# the variable $FileNet with "/archive" concatenated on the end
typeset DOC_ARCHIVE=${FileNet}/archive
# Set the variable DOC_SSI to the string value of the contents of
# the variable $CONTROL_BASE with "/ssi" concatenated on the end
typeset DOC_SSI=${CONTROL_BASE}/ssi
# Change the current working directory to the value of the contents of
# the variable $DOC_SCRIPTS.
cd ${DOC_SCRIPTS}
# Split the value of the contents of the variable $CONTROL_BASE into
# pieces delimited by the character "/" and place the 4th value into the variable
# DOC_LEVEL.  For example if $CONTROL_BASE="a/b/c/d/e" then
# DOC_LEVEL would equal "d"
typeset DOC_LEVEL=`echo ${CONTROL_BASE}|cut -d/ -f4`
# "source" the script located in the file denoted by the contents of the 
# values of the variables below. Sourcing a file is slightly different from running
# a script in that it will keep all the values of variables and functions defined within
# the new script.  This does not happen if the script is simply run.
. ${DOC_SSI}/DCS_${DOC_LEVEL}01_${HOSTNAME}.ssi
# "source" the script located in the file denoted by the contents of the 
# values of the variables below. 
. /cm/vgi/etc/ssi/DCS_${DOC_LEVEL}01_${HOSTNAME}_secure.ssi.v1

I hope this is clearer...

This User Gave Thanks to citaylor For This Post:

citaylor

View Public Profile for citaylor

Find all posts by citaylor

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

help wanted to understand MQ script

hi , i am writing a script to copy the MQ messages from onw queue to another. The following i got from one site, but i di not understand , can anyone explain. /root/scripts/sap/q -m$Q_MANAGER -i$Q_NAME_SRC_1 -F/logs/mq/MQ_COPYdump_$Q_NAME_SRC_1.$$ /root/scripts/sap/q -m$Q_MANAGER...

2. Shell Programming and Scripting

Can't understand the script

I am relatively new to Shell Scripting. I can't understand the following two scripts. Can someone please spare a minute to explain? 1) content s of file a are (021) 654-1234 sed 's/(//g;s/)//g;s/ /-/g' a 021-654-1234 2)cut -d: -f1,3,7 /etc/passwd |sort -t: +1n gives error

3. Shell Programming and Scripting

Need to understand the script pls help

Can u please explain what it is doing #!/bin/sh fullyear=`/home/local/bin/datemmdd 1`"."`date +%Y` uehist=/u05/home/celldba/utility/ue/prod/history echo $fullyear cd $uehist ls -ltr pwroutages.master.$fullyear* | awk '{print $9}' > /u01/home/celldba/tmp/pwroutages_master_all_tmp while...

4. Shell Programming and Scripting

Need help to understand ksh script

Hi All, I have a ksh script & would like to understand mening of below lines in script, Starting lines of script is as below, #!/bin/ksh #%W% %I% %D% %T% ---- ??? #%W%G --- ??? num_ctrl_files=0 OS=`uname` if then //g' | egrep -v '(.sh:|.ksh:)' | sed 's/^.*://g' | sed 's/^M//g' |...

5. Shell Programming and Scripting

Understand script formte

Hi i have one script and i am running it but not getting current output so i want to understand how to input in the script. when i do help then i am getting below massage thanks got it

6. Shell Programming and Scripting

Help to understand a script

Hello world! Can someone please explain me how this code works? I'ts supposed to find words in a dictionary and show the anagrams of the words. { part = word2key($1) data = $1 } function word2key(word, a, i, x, result) { x = split(word, a, "") asort(a) ...

7. Shell Programming and Scripting

Can't understand script output

New to korn shel1 and having an issue. The following is suppose to read the parameter values from files in a source directory and then pass them on to a log file in a different directory, The ArchiveTracker scripts is suppose to call the parameterreader script to exact the parameter values and...

8. Shell Programming and Scripting

Need help to understand the below shell script

Please help me to understand the below 3 lines of code.execute shell in jenkins 1)APP_IP=$( docker inspect --format '{{ .NetworkSettings.Networks.'"$DOCKER_NETWORK_NAME"'.IPAddress }}' ${PROJECT_NAME_KEY}"-CI" ) 2)HOST_WORKSPACE=$(echo ${WORKSPACE} | sed...

9. UNIX for Beginners Questions & Answers

Help me understand this script

#!/bin/awk -f BEGIN {i=1;file="modified.txt"} { if ($0 !~ /^DS:/) {print $0 >> file} else { if ($0 ~ /^DS:/) {print "DS: ",i >> file;if (i==8) {i=1} else {i++}}; } } END {gzip file} Can someone explain to me how this above script works, I got it from a friend but not able...

LEARN ABOUT OPENDARWIN

script

SCRIPT(1)						    BSD General Commands Manual 						 SCRIPT(1)

NAME

     script -- make typescript of terminal session

SYNOPSIS

     script [-a] [-k] [-q] [-t time] [file [command ...]]

DESCRIPTION

     The script utility makes a typescript of everything printed on your terminal.  It is useful for students who need a hardcopy record of an
     interactive session as proof of an assignment, as the typescript file can be printed out later with lpr(1).

     If the argument file is given, script saves all dialogue in file.	If no file name is given, the typescript is saved in the file typescript.

     If the argument command ... is given, script will run the specified command with an optional argument vector instead of an interactive shell.

     Options:

     -a       Append the output to file or typescript, retaining the prior contents.

     -k       Log keys sent to program as well as output.

     -q       Run in quiet mode, omit the start and stop status messages.

     -t time  Specify time interval between flushing script output file.  A value of 0 causes script to flush for every character I/O event.  The
	      default interval is 30 seconds.

     The script ends when the forked shell (or command) exits (a control-D to exit the Bourne shell (sh(1)), and exit, logout or control-d (if
     ignoreeof is not set) for the C-shell, csh(1)).

     Certain interactive commands, such as vi(1), create garbage in the typescript file.  The script utility works best with commands that do not
     manipulate the screen.  The results are meant to emulate a hardcopy terminal, not an addressable one.

ENVIRONMENT

     The following environment variable is utilized by script:

     SHELL  If the variable SHELL exists, the shell forked by script will be that shell.  If SHELL is not set, the Bourne shell is assumed.  (Most
	    shells set this variable automatically).

SEE ALSO

     csh(1) (for the history mechanism).

HISTORY

     The script command appeared in 3.0BSD.

BUGS

     The script utility places everything in the log file, including linefeeds and backspaces.	This is not what the naive user expects.

     It is not possible to specify a command without also naming the script file because of argument parsing compatibility issues.

     When running in -k mode, echo cancelling is far from ideal.  The slave terminal mode is checked for ECHO mode to check when to avoid manual
     echo logging.  This does not work when in a raw mode where the program being run is doing manual echo.

BSD
								   June 6, 1993 							       BSD