You need to take the following steps to start an application with utmmain:
Set the UTMPATH environment variable to utmpath. It makes sense to add the following commands to the .profile or in the login-file of the login name under which the application will be run:
UTMPATH=
utmpath
export UTMPATHFor more information on utmpath see "Installing UTM system functions on Unix and Linux systems".
Create the start parameter file as described on "Start parameters for openUTM".
Start utmmain in the filebase directory as a background process:
utmpath
/ex/utmmain
filebase [ startparam-file]&
filebase
is the fully qualified base name for the UTM application (the name of the directory of the application).
startparam-file
is the fully qualified name of the file in which the start parameters are defined. If this parameter is omitted, then the start parameters must be in the file filebase
/startparameter
.
utmmain produces messages on stdout at the start of the application as well as during the application run; error messages occurring at the start are output to stderr (see also "Error messages at the application start"). These messages can be redirected to a file or a filter program as in the following example.
Example
The application and the start parameter file are located in the directory /home/utmbsp
, the start parameter file has the default name startparameter
.
If all output is to be redirected to a file, then call utmmain as follows:
utmpath/ex/utmmain /home/utmbsp 1>utmp.out 2>utmp.err &
If the output is to be handled further by a program or a shell script named filter
instead, then call utmmain as follows, for example:
utmpath/ex/utmmain /home/utmbsp 2>&1 | filter
Using this method, you can react to messages from the network process, for example, which is not possible with an MSGTAC program.
filter
script is only possible if automatic switchover of the log files has not been activated (see SYSPROT in section "Start parameter file of the application").Network processes
When utmmain is started, it generates the following network processes.
One or more utmnet processes.
One or more utmnets resp. utmnetssl for TLS communication socket network processes are also started for TCP/IP communication, see also section "Using different socket network processes (Unix and Linux systems)".