Perl Script return value in DOS batch file

Question

I have a DOS batch file that calls a Perl Script file:

ssutexec.pl prog=MyProg I_CARD=MyCard O_F071=ME007 F70P=MYF70P TRIG=MYTRIG
set status=%errorlevel%
if NOT %status% == 0 (
  echo *******************************************************
  echo   MPSBM070 JOB stopped with a RETURN CODE of %status%
  echo ************** END OF JOB *****************************
  goto JobEnd
 )

Inside the ssutexec.pl perl script file, an error condition is executed and the script exits with exit($status):

if ($status != 0)
 {
  system("ssutdttm.pl SSUTEXEC \"finished processing $prog_nam (Abnormal End) on\"") ;
  print "******************************************************************" ;
  print "              JOB STOPPED - Due to Return code of ($status)" ;
  print "*****************END OF JOB***************************************" ;
  system("ssutdttm.pl SSUTEXEC \"finished processing $prog_nam (Abnormal End) on\"") ;
  system("ssuttmdr.pl -c -b $starttime -m \"$prog_nam\"") ;
  exit($status) ;
 }

I am not a perl script guy. Errorlevel isn't being triggered so I am not getting the error. How can I trap the value of the perl script exit code within my DOS batch file?

INDLUDING EDITS: The new batch file looks like this:

@echo off
setlocal enabledelayedexpansion 


if not defined run_env goto ScriptExit

echo ******************************************************************
echo *                      MYPROG                                  *
echo ******************************************************************

perl ssutdttm.pl MYPROG Start -
perl ssutexec.pl prog=MyProg I_CARD=MyCard O_F071=ME007 F70P=MYF70P TRIG=MYTRIG
set status=!errorlevel!
if NOT %status% == 0 (
  echo *******************************************************
  echo   MYPROG JOB stopped with a RETURN CODE of %status%
  echo ************** END OF JOB *****************************
  goto JobEnd
 )

:JobEnd
  if %status% == 0 (
    echo *******************************************************
    echo       NORMAL END OF JOB - RETURN CODE of %status%
    echo ******** NORMAL END OF JOB ****************************
   ) ELSE (
    echo !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    echo     ABNORMAL END OF JOB - RETURN CODE of %status%
    echo !!!!!! ABNORMAL END OF JOB !!!!!!!!!!!!!!!!!!!!!!!!!!!!
   )
  ssutdttm.pl MYPROG end - 
  exit /b %status%
::
:ScriptExit
echo run_env: %run_env%

Are you sure `$status` is being set to a non-zero value in the Perl script? — Jonah Bishop, Jan 23 '13 at 21:22
@Jonah...yes, the Print statement in the code prints out a value of 44 — MikeTWebb, Jan 23 '13 at 21:33
@MikeTWebb What is the value of $status after those last two system() calls right before the exit? — Craig Treptow, Jan 24 '13 at 15:58

score 2 · Answer 1 · answered Jan 23 '13 at 21:40

2

Working with batch files can really be a pain (DOS batch files make bash scripts look wonderful, and bash stinks!). The problem could be cropping up from the way batch files handle variable expansion. Here's something to try:

Add the following line to the top of your batch script (I usually put it at the top, just under my @echo off line): setlocal enabledelayedexpansion
Change all %ERRORLEVEL% references to !ERRORLEVEL! instead (exclamation marks instead of percent signs).

These changes will have the effect of causing variables to get expanded at execution time, rather than at parse-time. I've seen the %ERRORLEVEL% value get mangled when not using the delayed expansion option. Read this EnableDelayedExpansion information page for more.

answered Jan 23 '13 at 21:40

Jonah Bishop

12,279
6
49
74

@Jonah...I will aslo give you approach a try tomorrow and post the result. Thanks as well! – MikeTWebb Jan 23 '13 at 22:29
@Jonah...I tried this and still my scenario doesn't see the !errorlevel! variable – MikeTWebb Jan 24 '13 at 21:13
Hmm. Here's another thing to try ... try wrapping your conditional in quotes: `if not "%status%" == "0"` – Jonah Bishop Jan 24 '13 at 21:16

score 2 · Answer 2 · edited May 23 '17 at 10:34

2

I think you should be calling perl.exe with the script as an argument:

perl ssutexec.pl prog=MyProg ...

In my tests, if I have just the script name, I get prompted for what I want to use to open the test.pl file. That means perl.exe is not executing my Perl code.

Your file associations could likely be there, but your script could still be failing because of the nuances of Windows.

I tested with my two very simple scripts:

test.bat

@ECHO OFF

perl test.pl

set status=%errorlevel%

if NOT %status% == 0 (
 echo status was set with value of %status%
)

and test.pl

use warnings;
use strict;

my $status = 44;

exit($status)

and the expected output:

C:\Dropbox\Programming\Perl\Learn\blah>test
status was set with value of 44

edited May 23 '17 at 10:34

Community

1
1

answered Jan 23 '13 at 21:55

Craig Treptow

834
7
19

2

The [strict](http://perldoc.perl.org/strict.html) pragma enables a bunch of safety checks on your code. Using it in production environments is encouraged. Don't be surprised if your script initially chokes, though; it's not called "strict" for nothing. – Jonah Bishop Jan 24 '13 at 01:02
@Craig....I tried the above scenario and it worked with test.pl being called by perl and without. Andy ideas? – MikeTWebb Jan 24 '13 at 15:00

Perl Script return value in DOS batch file

2 Answers2