I am new to this forum, but like what I am seeing. I hope you folks
can collectively lend a hand.

I am running a shell script to launch a perl script and then create a
log file I can read from the program. The shell script runs, the perl scrip
runs, the log is created and then everthing stops. Control never returns to
the COBOL program. I run lots of scripts using the same basic format and
have never had this problem. Any ideas?

The script is created as a print file.
********************************

#!/bin/ksh

set -x

## Purpose: Run a PERL Script and
## capture output.
## Date Written: 08/14/2008

export Log=/lawson/apps/prod/work/ArchivePerl.log
echo "starting PERL script" >> $Log
date >> $Log
cd /lawson/gen/bin/
perl zzarch_import.pl ar
export ErrLvl=$?
if [[ $ErrLvl != 0 ]]
then echo "Error Level = $ErrLvl" >> $Log
date >> $Log
echo "Not Complete" >> $Log
echo "---------- Non-Zero Abend : ERROR ----------------" >> $Log
echo "Script Exiting" >> $Log
exit $ErrLvl
else
date >> $Log
echo "Perl script complete" >> $Log
exit
fi

**********************************

The command to execute the script is created:

INITIALIZE WS-COMMAND-STRING.
STRING "ksh " DELIMITED BY SIZE
ICLAWDWS-LAWDIR DELIMITED BY SPACES
"/print/" DELIMITED BY SIZE
CRT-USER-NAME DELIMITED BY SPACES
"/" DELIMITED BY SIZE
WS-FORMAT-OUT DELIMITED BY SPACES
"/1/ararcprl" DELIMITED BY SIZE
INTO WS-COMMAND-STRING.
CALL "system" USING WS-COMMAND GIVING WS-RETURN-COMMAND.

WS-FORMAT-OUT is the CRT-JOB-NAME in lower case. It runs great,
it just never returns.

Thanks

So how are you sure that control never returns?
Try putting a DISPLAY statement after the system call.

Also, it may be necessary to have a return statement in your secripts.

Is your Perl script returning conrtol back to your shell?

Hi,

The perl script is returning control to the shell script. The output log is completed and the script exit is echoed in the lawson log. At this point the log just sits with an
----------------------------end------------------------------------------------

The program never goes to the next line of code after the system call.

Dan

More information

here is the pertenant job log from a new run

* PHASE 2 Ended: 14:17:37
*****************************************
**********************************
* PHASE 3 - ARCHIVE AR SYSTEM *
**********************************

## Shell script starts

* Started: 14:17:37
+ export Log=/lawson/apps/prod/work/ArchivePerl.log
+ echo starting PERL script
+ 1>> /lawson/apps/prod/work/ArchivePerl.log
+ date
+ 1>> /lawson/apps/prod/work/ArchivePerl.log
+ cd /lawson/gen/bin/
+ perl zzarch_import.pl ar
Thu Aug 21 14:17:55 EDT 2008

## perl script starts

Loading ARADJUST ... 93 records processed.
Loading from /lawson/archive/ADJ.00

File Processed Added Duplicate Bad
---- --------- ----- --------- ---
ARADJUST 93 0 93 0

File Processed Added Duplicate Bad
---- --------- ----- --------- ---
ARRTM 1 0 1 0
Loading from /lawson/archive/ARJ.00
Loading from /lawson/archive/BLH.00
Loading from /lawson/archive/FTT.00
Loading from /lawson/archive/RVH.00
Loading from /lawson/archive/RVD.00

Thu Aug 21 14:44:37 EDT 2008
+ export ErrLvl=0
+ [[ 0 != 0 ]]
+ date
+ 1>> /lawson/apps/prod/work/ArchivePerl.log
+ echo Perl script complete
+ 1>> /lawson/apps/prod/work/ArchivePerl.log
+ exit
======================================End=======================================
Help Find FndNxt Show Send Home
Bottom


The "loading" statements are from the perl script. the "+" lines are the echo from the shell script. The last line of the shell is exit. The program is not responding and has to be killed from the command line.

Dan

as Trezaei said you need to put a display after the call in your cobol program just to see if it returns from the call routine. You may also need to post the WS of your WS-COMMAND-STRING.

Usually here's what I do in unix:
1. Create a ksh script (Sample.ksh) in a common bin directory. Something like
GENDIR/bin.

2. In your cobol program you string the name of the ksh script
STRING "Sample.ksh parm1 parm2 parm3" DELIMITED BY SIZE
INTO WS-COMMAND-STRING.
CALL "SYSTEM" USING WS-COMMAND-STRING.

Works everytime.

Post the part of your code and the few lines around it that do the system call.
And put it in CODE tag so it looks like this:

Here is the section that creates the script and executes it.

The first display produces the following text:

The script executes perfectly, but the program never gets to the second display.

Dan

My apologies to all of you. By adding the display after the call I found that the script was returning and the problem was programatical at a point after the script completed. I do thank you for the help in finding what to look for.

Thanks,

Dan

Awesome! Glad we could help :D