# 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
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... (0 Replies)
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 Replies)
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... (2 Replies)
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' |... (6 Replies)
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 (1 Reply)
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)
... (1 Reply)
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... (3 Replies)
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... (1 Reply)
#!/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... (3 Replies)
Discussion started by: Kamesh G
3 Replies
LEARN ABOUT OSF1
trap
trap(1) User Commands trap(1)NAME
trap, onintr - shell built-in functions to respond to (hardware) signals
SYNOPSIS
sh
trap [ argument n [n2...]]
csh
onintr [-| label]
ksh
*trap [ arg sig [ sig2...]]
DESCRIPTION
sh
The trap command argument is to be read and executed when the shell receives numeric or symbolic signal(s) (n). (Note: argument is scanned
once when the trap is set and once when the trap is taken.) Trap commands are executed in order of signal number or corresponding symbolic
names. Any attempt to set a trap on a signal that was ignored on entry to the current shell is ineffective. An attempt to trap on signal 11
(memory fault) produces an error. If argument is absent all trap(s) n are reset to their original values. If argument is the null string
this signal is ignored by the shell and by the commands it invokes. If n is 0 the command argument is executed on exit from the shell. The
trap command with no arguments prints a list of commands associated with each signal number.
csh
onintr controls the action of the shell on interrupts. With no arguments, onintr restores the default action of the shell on interrupts.
(The shell terminates shell scripts and returns to the terminal command input level). With the - argument, the shell ignores all inter-
rupts. With a label argument, the shell executes a goto label when an interrupt is received or a child process terminates because it was
interrupted.
ksh
trap uses arg as a command to be read and executed when the shell receives signal(s) sig. (Note that arg is scanned once when the trap is
set and once when the trap is taken.) Each sig can be given as a number or as the name of the signal. trap commands are executed in order
of signal number. Any attempt to set a trap on a signal that was ignored on entry to the current shell is ineffective. If arg is omitted
or is -, then the trap(s) for each sig are reset to their original values. If arg is the null (the empty string, e.g., "" ) string then
this signal is ignored by the shell and by the commands it invokes. If sig is ERR then arg will be executed whenever a command has a non-
zero exit status. If sig is DEBUG then arg will be executed after each command. If sig is 0 or EXIT for a trap set outside any function
then the command arg is executed on exit from the shell. The trap command with no arguments prints a list of commands associated with each
signal number.
On this man page, ksh(1) 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.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), exit(1), ksh(1), sh(1), attributes(5)SunOS 5.10 23 Oct 1994 trap(1)