← Using the BASH Definition TypeUsing the CSH Definition Type →

Using the KSH Definition Type

The Korn shell is the default UNIX shell on various UNIX systems such as AIX, HP-UX and Solaris. It is also available for Linux and Microsoft Windows in the form of pdksh.

note

You must assign at least one process server to run KSH process definitions in order to use the definition type.

Interpreter

By default, the interpreter for KSH scripts defaults to /bin/ksh on most platforms. You can override this by specifying an interpreter on process server-level with the LocalInterpreter_KSHprocess server parameter, for example, /usr/local/bin/pdksh. You can also specify a list of allowed interpreters on process server-level using the InterpreterWhitelist_KSHprocess server parameter and override the default interpreter on process definition-level with the parameter JCS_INTERPRETER_KSH. Simply create the parameter and point it to your preferred interpreter, it must exist and be white-listed using the InterpreterWhitelist_KSH process server parameter.

The InterpreterWhitelist_KSH process server parameter takes a regular expression that must match the value of the JCS_INTERPRETER_KSH parameter.

Writing portable KSH scripts

KSH is not the same implementation on all platforms. We have found the following compatibility issues between these variations:

  • Some versions of KSH do not support aliases in non-interactive invocations of the Korn shell. In other implementations, aliases can only be used in scripts that are not sourced, but executed. Since the process definition script code is sourced, it cannot call any aliases. We highly recommend that you use functions instead.
  • On Solaris, the syntax $(command) to execute a program and substitute its standard output is not allowed. You should use a pair of backtiocks (grave accents) to remain portable to Solaris: ``command.
  • The pdksh does not implement all the features of AT&T ksh so there are minor differences between the two.
  • The AT&T Korn shell has been released with an Eclipse Public License and the source code is freely available on github. This means that most major Linux distributions can now offer AT&T's Korn shell. If you have an older Solaris or Linux system, you might consider building and deploying it.

Environment

See Using Platform Definition Types for more information regarding the predefined variables and how to create per-system or per-user environment variables.

In addition, the KSH definition type will source ${JCS_HOME}/admin/ksh.profile if it exists, for backwards compatibility with v7. You can set JCS_HOME with the EnvironmentFile or EnvironmentVariables mechanism documented in Using Platform Definition Types.

Variables and Parameters

  • Parameters in the process definition are manipulated in the KSH source simply as variables, using the standard $VARIABLE syntax.
  • The Korn shell does not have actual data types; all parameter values are stored as strings. Numbers are translated automatically. Dates are sent and retrieved using the Script Date Format.
  • Out parameters are supported by setting the parameter using the VARIABLE=VALUE syntax.
  • Array parameters are supported for KSH, provided your interpreter supports them

Returning an Error

If your script code exits with a non-zero exit code this is correctly reflected in the server.

Code a set -e command to abort script execution immediately on running a command that has a non-zero exit status.

KSH Examples

The following shows how to use a normal environment variable:

echo "This is running under user $USER with home directory $HOME and temporary directory $TMPDIR."

The following shows how to pass numeric (N1), string (S1) and date (D1) parameters to and from KSH scripts:

# Note KSH allows no spaces around = in variable assignment
N1=`expr $N1 + $N1` # Add numeric variable to itself
S1="$S1 $S1"  # Concatenate string
echo "Concatenated string" $S1
DTEMP="1999/12/31 23:59:59,000 GMT"
echo You said $D1, I propose $DTEMP
D1=$DTEMP   # Set DateTime to new string value

The following example shows you how to return a non-zero exit code resulting in the process going into Error:

N=1
echo "Exiting with value $N."
exit $N

echo "Not reached"

See Also

← Using the BASH Definition TypeUsing the CSH Definition Type →