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)
Hi All;
Is there anybody can explain this script please?
trap 'C_logmsg "F" "CNTL/c OS signal trapped, Script ${G_SCRIPTNAME] terminated"; exit 1' 2
trap 'C_logmsg "F" "Kill Job Event sent from the Console, Script ${G_SCRIPTNAME] terminated"; exit 1' 15 (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)
Discussion started by: naresh85
1 Replies
LEARN ABOUT DEBIAN
test::lectrotest::regressiontesting
Test::LectroTest::RegressionTesting(3pm) User Contributed Perl Documentation Test::LectroTest::RegressionTesting(3pm)NAME
Test::LectroTest::RegressionTesting - How to do regression testing (for free!)
SYNOPSIS
use Test::LectroTest
regressions => "regressions.txt";
# -- OR --
use Test::LectroTest
playback_failures => "regression_suite_for_my_module.txt",
record_failures => "failures_in_the_field.txt";
# -- OR --
use Test::LectroTest::Compat
regressions => "regressions.txt";
# -- OR --
use Test::LectroTest::Compat
playback_failures => "regression_suite_for_my_module.txt",
record_failures => "failures_in_the_field.txt";
DESCRIPTION
Say that LectroTest uncovers a bug in your software by finding a random test case that proves one of your properties to be false. If you
apply a fix for the bug, how can you be sure that LectroTest will re-test the property using the exact same test case that "broke" it
before, just to be certain the bug really is fixed? And how can you be sure that future changes to your code will not reintroduce the same
bug without your knowing it?
For situations like these, LectroTest can record failure-causing test cases to a file, and it can play those test cases back as part of its
normal testing strategy.
The easiest way to take advantage of this feature is to set the regressions parameter when you "use" Test::LectroTest or
Test::LectroTest::Compat:
use Test::LectroTest
regressions => "regressions.txt";
This tells LectroTest to use the file "regressions.txt" for both recording and playing back failures. If you want to record and play back
from separate files, use the record_failures and playback_failures options:
use Test::LectroTest::Compat
playback_failures => "regression_suite_for_my_module.txt",
record_failures => "failures_in_the_field.txt";
Here is how it works:
1. When testing a property named N, LectroTest will check for a play-back file. If the file exists, LectroTest will search it for test
cases associated with N. If any such test cases exist, LectroTest will play them back before and in addition to performing the usual,
random testing of the property.
2. When performing the usual, random testing of a property named N, if a failure occurs (i.e., LectroTest finds a counterexample),
LectroTest will record the test case that caused the failure to the recording file, associating the test case with the name N.
NOTE: If you pass any of the recording or playback parameters to Test::LectroTest::Compat, you must have version 0.3500 or greater of
Test::LectroTest installed. (Module authors, update your modules' build dependencies accordingly.) The Test::LectroTest module itself,
however, has always ignored unfamiliar parameters, and thus these options are backward compatible with older versions.
SEE ALSO
Test::LectroTest gives a quick overview of automatic, specification-based testing with LectroTest. This module accepts failure recording
and play-back options.
Test::LectroTest::Compat lets you mix LectroTest with the popular family of Test::Builder-based modules such as Test::Simple and
Test::More. This module accepts failure recording and play-back options.
LECTROTEST HOME
The LectroTest home is http://community.moertel.com/LectroTest. There you will find more documentation, presentations, mailing-list
archives, a wiki, and other helpful LectroTest-related resources. It's also the best place to ask questions.
AUTHOR
Tom Moertel (tom@moertel.com)
COPYRIGHT and LICENSE
Copyright (c) 2004-06 by Thomas G Moertel. All rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.12.3 2007-08-30 Test::LectroTest::RegressionTesting(3pm)