Probably the reason for this is some ASCII-EBCDIC conversion problem: Unix machines, including AIX machines, encode files in ASCII (American Standard Code for Information Interchange) character sets. Not so the IBM-hosts, as they traditionally use a different character set called EBCDIC (Extended Binary Coded Decimal Interchange Code).
Usually there is some sort of conversion table, which tells the conversion program what character number x is to be replaced with in the other character set. Probably this conversion table is faulty at the place of the pipe character. I would bet on "M-3" not being a 3-character string like its representation here in this text but in fact some single-char non-printable character.
You can either correct this conversion process or run sed (or tr) over the file to correct the characters:
Hi,
We have a DEC Alpha 4100 Server with OSF1 Digital Unix 4.0.
Can any one tell me, if there are any commands on this Unix which are equivalent to "top" and "sar" on HP-UX or Sun Solaris ?
I am particularly interested in knowing the CPU Load, what process is running on which CPU, etc.
... (1 Reply)
Hi All,
I am trying to schedule a one time job using the at command with the help of shell script for my project. The shell script should take a parameter as a command line argument from the at command itself. Is it possible to take a command line parameter for a shell script in the command... (3 Replies)
hi,
I have
* an IBM P550 machine,
* an AIX 5.3 running on it and
* an oracle database, already installed on it.
The problem (or question of my own) is:
Oracle tns listener, "CT_LISTENER", and the enterprise manager (EM) of the instance, which is uniq instance and called... (0 Replies)
hi,
I have a problem about the Oracle related components. I'm not able to find any answer yet, and waiting for your responses...
Here is the configuration of my system:
* an IBM P550 machine,
* an AIX 5.3 running on it and
* an oracle database, already installed on it.
The problem (or... (1 Reply)
hello everybode.Got some sort of "problems" with this stuff;
well this is a program
int main()
{
int Pipe;
int origStdin, origStdout;
int childPID;
origStdin = dup(0);
origStdout = dup(1);
pipe(Pipe);
if( (childPID = fork()) < 0 )
{
perror(... (2 Replies)
Hi!
I've got a shell account on a FreeBSD machine. It doesn't have 'vim' installed, but only the original 'vi' text editor ("Version 1.79 (10/23/96) The CSRG, University of California, Berkeley.")
So, in PuTTY I've chosen "UTF-8 translation" to have my non-english characters appear correctly.... (2 Replies)
i am having text file below
NARGU S S 12358 SALES REP |22| Acccount/s
RAJU R B 64253 SALES REP |12| Acccount/s
RUKMAN S 32588 SALES REP |10| Acccount/s
NARGUND S S 12356... (3 Replies)
Hi,
I'm dealing with an issue and losing a lot of hours figuring out how i would solve this.
I have an input file which looks like this:
('BLABLA +200-GRS','Serviço ','TarifaçãoServiço','wap.bla.us.0000000121',2985,0,55,' de conversão em escada','Dia','Domingos')
('BLABLA +200-GRR','Serviço... (6 Replies)
Experts ,
In the given output of the log file, the 2nd field that is separated by "|" pipe is not aligned well due to the uneven data length, I would like it to align the 2nd column with 37 length (that is disturbed in the output) including the pipe . The two pepe "|" would be in a aligned way... (2 Replies)
hello All,
I am new user to shell scripting, kindly advise on the below?
I have a file where i have gaps & the delimiter falls in next line and new line is also created , plz see the example :employee.txt
Now the issue here is , i wan to write a script , where i can use "|" to get the... (6 Replies)
Discussion started by: sunnyd1
6 Replies
LEARN ABOUT DEBIAN
sigtrap
sigtrap(3perl) Perl Programmers Reference Guide sigtrap(3perl)NAME
sigtrap - Perl pragma to enable simple signal handling
SYNOPSIS
use sigtrap;
use sigtrap qw(stack-trace old-interface-signals); # equivalent
use sigtrap qw(BUS SEGV PIPE ABRT);
use sigtrap qw(die INT QUIT);
use sigtrap qw(die normal-signals);
use sigtrap qw(die untrapped normal-signals);
use sigtrap qw(die untrapped normal-signals
stack-trace any error-signals);
use sigtrap 'handler' => &my_handler, 'normal-signals';
use sigtrap qw(handler my_handler normal-signals
stack-trace error-signals);
DESCRIPTION
The sigtrap pragma is a simple interface to installing signal handlers. You can have it install one of two handlers supplied by sigtrap
itself (one which provides a Perl stack trace and one which simply "die()"s), or alternately you can supply your own handler for it to
install. It can be told only to install a handler for signals which are either untrapped or ignored. It has a couple of lists of signals
to trap, plus you can supply your own list of signals.
The arguments passed to the "use" statement which invokes sigtrap are processed in order. When a signal name or the name of one of
sigtrap's signal lists is encountered a handler is immediately installed, when an option is encountered it affects subsequently installed
handlers.
OPTIONS
SIGNAL HANDLERS
These options affect which handler will be used for subsequently installed signals.
stack-trace
The handler used for subsequently installed signals outputs a Perl stack trace to STDERR and then tries to dump core. This is the
default signal handler.
die The handler used for subsequently installed signals calls "die" (actually "croak") with a message indicating which signal was caught.
handler your-handler
your-handler will be used as the handler for subsequently installed signals. your-handler can be any value which is valid as an
assignment to an element of %SIG. See perlvar for examples of handler functions.
SIGNAL LISTS
sigtrap has a few built-in lists of signals to trap. They are:
normal-signals
These are the signals which a program might normally expect to encounter and which by default cause it to terminate. They are HUP,
INT, PIPE and TERM.
error-signals
These signals usually indicate a serious problem with the Perl interpreter or with your script. They are ABRT, BUS, EMT, FPE, ILL,
QUIT, SEGV, SYS and TRAP.
old-interface-signals
These are the signals which were trapped by default by the old sigtrap interface, they are ABRT, BUS, EMT, FPE, ILL, PIPE, QUIT, SEGV,
SYS, TERM, and TRAP. If no signals or signals lists are passed to sigtrap, this list is used.
For each of these three lists, the collection of signals set to be trapped is checked before trapping; if your architecture does not
implement a particular signal, it will not be trapped but rather silently ignored.
OTHER
untrapped
This token tells sigtrap to install handlers only for subsequently listed signals which aren't already trapped or ignored.
any This token tells sigtrap to install handlers for all subsequently listed signals. This is the default behavior.
signal
Any argument which looks like a signal name (that is, "/^[A-Z][A-Z0-9]*$/") indicates that sigtrap should install a handler for that
name.
number
Require that at least version number of sigtrap is being used.
EXAMPLES
Provide a stack trace for the old-interface-signals:
use sigtrap;
Ditto:
use sigtrap qw(stack-trace old-interface-signals);
Provide a stack trace on the 4 listed signals only:
use sigtrap qw(BUS SEGV PIPE ABRT);
Die on INT or QUIT:
use sigtrap qw(die INT QUIT);
Die on HUP, INT, PIPE or TERM:
use sigtrap qw(die normal-signals);
Die on HUP, INT, PIPE or TERM, except don't change the behavior for signals which are already trapped or ignored:
use sigtrap qw(die untrapped normal-signals);
Die on receipt one of an of the normal-signals which is currently untrapped, provide a stack trace on receipt of any of the error-signals:
use sigtrap qw(die untrapped normal-signals
stack-trace any error-signals);
Install my_handler() as the handler for the normal-signals:
use sigtrap 'handler', &my_handler, 'normal-signals';
Install my_handler() as the handler for the normal-signals, provide a Perl stack trace on receipt of one of the error-signals:
use sigtrap qw(handler my_handler normal-signals
stack-trace error-signals);
perl v5.14.2 2011-09-19 sigtrap(3perl)