08-22-2008
How are you running it? Perl's system function, for instance, reports the exit status back in $?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello there!
Here is my problem. I hope I can get some help about it.
I need to know how can I get the return code of an application in the Unix shell script.
The script is like below:
PREVIOUS STATEMENT & VARIABLES
sqlplus scott/tiger @$sqldir/$sqlscript
NEXT STATEMENT (Like... (7 Replies)
Discussion started by: Shaz
7 Replies
2. UNIX for Dummies Questions & Answers
I am trying to capture the exit status of a parent shell
in a subshell.
I am using the trap .. Exit command in the subshell
I cant use the export command in the parent shell to
to export a variable with the exit status to the subshell.
I would have tooooo many parent shells to change.
... (2 Replies)
Discussion started by: Bob Bannon
2 Replies
3. Shell Programming and Scripting
How to capture output or numeric part given by $? command into the variable?
If I go for
var=`$?`
then $var is found empty. (2 Replies)
Discussion started by: videsh77
2 Replies
4. Shell Programming and Scripting
Hello,
I have a C++ binary that runs in my perl script. But, Currently, the binary is doing a core dump and i want to capture the retrun status of the binary to report as an issue.
Can you please help me on this.
Thanks,
Sateesh (1 Reply)
Discussion started by: kotasateesh
1 Replies
5. Shell Programming and Scripting
Hi All,
I have a scenario where I am executing some child shell scripts in background (using &)through a master parent script.
Is there a way I can capture the exit status of each individual child script after the execution is completed. (2 Replies)
Discussion started by: paragkalra
2 Replies
6. Shell Programming and Scripting
Hi,
I have a problem that I am sure someone will know the answer to. Currently I have a script which returns a binary output if it finds a certain search string (in this case relating to a DRBD cluster) as follows:
searchstring="cs:Connected st:Primary/Secondary ds:UpToDate/UpToDate"
&& echo... (3 Replies)
Discussion started by: almightybunghol
3 Replies
7. Shell Programming and Scripting
Folks ,
I have a korn shell script that i have written for assembly, the variable that is a final result is returning hexadecimal, now the value is to be converted to binary and return the place holder in the binary that has a 1 in its place and send it to a variable assigned for the... (0 Replies)
Discussion started by: venu
0 Replies
8. Shell Programming and Scripting
Hi can you explain me, what does variables $@ and $* return and how are they used, if can give me a sample example it could be helpful.
Thanks in advance,
Regards,
Abhishek S. (1 Reply)
Discussion started by: abhisheksunkari
1 Replies
9. Shell Programming and Scripting
Hi
I am pretty confused in returning and capturing multiple values
i have defined a function which should return values "total, difference"
i have used as
#!/usr/bin/ksh
calc()
{
total=$1+$2
echo "$total"
diff=$2-$1
echo "$diff"
}
I have invoked this function as
calc 5 8
Now i... (2 Replies)
Discussion started by: Priya Amaresh
2 Replies
10. Shell Programming and Scripting
Hi All,
I was out not working on unix from quite sometime and came back recently. I would really appreciate a help on one of the issue I am facing....
I am trying to kick off the CodeNameProcess.sh in PARALLEL for all the available codes. The script runs fine in parallel.
Let say there are... (1 Reply)
Discussion started by: rkumar28
1 Replies
vmsish(3pm) Perl Programmers Reference Guide vmsish(3pm)
NAME
vmsish - Perl pragma to control VMS-specific language features
SYNOPSIS
use vmsish;
use vmsish 'status'; # or '$?'
use vmsish 'exit';
use vmsish 'time';
use vmsish 'hushed';
no vmsish 'hushed';
vmsish::hushed($hush);
use vmsish;
no vmsish 'time';
DESCRIPTION
If no import list is supplied, all possible VMS-specific features are assumed. Currently, there are four VMS-specific features available:
'status' (a.k.a '$?'), 'exit', 'time' and 'hushed'.
If you're not running VMS, this module does nothing.
"vmsish status"
This makes $? and "system" return the native VMS exit status instead of emulating the POSIX exit status.
"vmsish exit"
This makes "exit 1" produce a successful exit (with status SS$_NORMAL), instead of emulating UNIX exit(), which considers "exit 1" to
indicate an error. As with the CRTL's exit() function, "exit 0" is also mapped to an exit status of SS$_NORMAL, and any other
argument to exit() is used directly as Perl's exit status.
"vmsish time"
This makes all times relative to the local time zone, instead of the default of Universal Time (a.k.a Greenwich Mean Time, or GMT).
"vmsish hushed"
This suppresses printing of VMS status messages to SYS$OUTPUT and SYS$ERROR if Perl terminates with an error status. and allows
programs that are expecting "unix-style" Perl to avoid having to parse VMS error messages. It does not suppress any messages from
Perl itself, just the messages generated by DCL after Perl exits. The DCL symbol $STATUS will still have the termination status, but
with a high-order bit set:
EXAMPLE:
$ perl -e"exit 44;" Non-hushed error exit
%SYSTEM-F-ABORT, abort DCL message
$ show sym $STATUS
$STATUS == "%X0000002C"
$ perl -e"use vmsish qw(hushed); exit 44;" Hushed error exit
$ show sym $STATUS
$STATUS == "%X1000002C"
The 'hushed' flag has a global scope during compilation: the exit() or die() commands that are compiled after 'vmsish hushed' will be
hushed when they are executed. Doing a "no vmsish 'hushed'" turns off the hushed flag.
The status of the hushed flag also affects output of VMS error messages from compilation errors. Again, you still get the Perl
error message (and the code in $STATUS)
EXAMPLE:
use vmsish 'hushed'; # turn on hushed flag
use Carp; # Carp compiled hushed
exit 44; # will be hushed
croak('I die'); # will be hushed
no vmsish 'hushed'; # turn off hushed flag
exit 44; # will not be hushed
croak('I die2'): # WILL be hushed, croak was compiled hushed
You can also control the 'hushed' flag at run-time, using the built-in routine vmsish::hushed(). Without argument, it returns the
hushed status. Since vmsish::hushed is built-in, you do not need to "use vmsish" to call it.
EXAMPLE:
if ($quiet_exit) {
vmsish::hushed(1);
}
print "Sssshhhh...I'm hushed...
" if vmsish::hushed();
exit 44;
Note that an exit() or die() that is compiled 'hushed' because of "use vmsish" is not un-hushed by calling vmsish::hushed(0) at
runtime.
The messages from error exits from inside the Perl core are generally more serious, and are not suppressed.
See "Pragmatic Modules" in perlmod.
perl v5.12.1 2010-04-26 vmsish(3pm)