Signal handling
Program units in C have limited usage of signals on Unix and Linux systems. The SIGUSR1 and SIGUSR2 signals can be trapped by the C program unit in the start exit of a work process. All other signals are handled by the openUTM system code itself by default.
As an alternative to the default handling of signals in openUTM, you can program a separate user signal routine for certain signals and register it in openUTM, see section “Programming user-specific error handling (Unix and Linux systems)".
CMX interface in utmwork
You must note the following when using CMX calls in C/C++ program units:
For technical reasons, a CMX simulation is used in the UTM library libwork.a and libwork.so in UTM applications with OSI TP. It is therefore not possible in this case to use CMX calls in a C/C++ program unit.
Calling the fork() function in a C/C++ program unit
You must note the following when calling the fork() function in C/C++ program units: No openUTM program interfaces may be used in a child process created using fork(). Otherwise, the UTM application will terminate abnormally.
 | For details on creating and linking shared objects, compiling program units and linking applications, see the manual openUTM manual “Using UTM Applications on Unix, Linux and Windows Systems”, section "Creating the application program". |