0

I want to call a KSH script a KSH script.

Script 1 performs the following:

  1. Loops thru a list of database server
  2. Perfroms a query
  3. Appends output from query from each database server to a txtfile

Script 2 performs the following:

  1. Creates an HTML file that displays the each row in the text file in an HTML File

  2. Emails the HTML file with the query results to a list of receipeints

    Usage: KSH backup_report.ksh qry_rslt_textfile.txt
    (txtfile contains results of query from each server)

Is the following syntax correct?

#! /bin/ksh
< Start of Script 1 Code>
.
.
.
< End of Script 1 Code>

< Start of Script 2 Code - Call Script 2>
/sybase/dba/backup_report.ksh qry_rslt_textfile.txt
<End of Script 2 Code>
Improve this question

2 Answers 2

Reset to default
2

Yes - providing that the script has execute permission, this will do what you want. It will in actuality call the second script as the last command of the first script, but that's splitting a technical hair that you're probably not going to need to worry about.

Improve this answer
0

To call a script from another program (or script), you must take care of a list of things:

  1. The script must be found
  2. The script must have execute permissions
  3. The script must include a hint to its interpreter

Finding the script

Check. You've already included the full path to the script. An alternative is to include /sybase/dba in the PATH variable at the top of script 1:

PATH=/sybase/dba:$PATH

Correct permissions

The script will need execute permissions for all categories of users that may need to run it.

For most interpreters execute permissions are not sufficient; the chosen interpreter also needs to be able to read the script's code.

$ ls -l  /sybase/dba/backup_report.ksh
-rwxr-x---   1 Henk     sys           805 Apr  3 07:00 /sybase/dba/backup_report.ksh

The right interpreter

Scripts are not executed directly. The kernel needs a hint to tell it which interpreter to use. This is accomplished by including a #! (hashbang) mark on the first line, followed by the path to the interpreter:

#! /bin/ksh

Assure you know where your ksh lives and insert the right path.

Final Note

Also make sure you know which version of ksh. These days, ksh implies ksh93, which is still actively developed and available on most platforms.

Improve this answer
2
  • The "Final Note" is dubious at least: on AIX the system shell (and the one you get when calling "ksh" is a ksh88, the ksh93 is called by "/bin/ksh93". This is true since AIX v4 (~1998), before that (AIX 3.2.5) the system shell was a Bourne shell and "/bin/ksh" was still a ksh88. Commented Jun 22 at 11:30
  • You're not wrong. That last paragraph could be rephrased. Development of ksh93 shifted to new leadership since 2020, regathering the community with a focus on stability and compatibility. Ksh88 is more stable but only because it has not seen any development, afaik. We had pdksh and now mksh. Commented Jul 2 at 18:23

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.