During distributed processing, the UTM application is connected to the network via network processes. These processes are responsible for handling connection setup requests and for managing data transfer via the connection.
The main process utmmain of a UTM application starts one or more network processes, which can in turn establish and manage numerous connections. Assignments between connections and processes are controlled through the use of listener IDs. All connections with the same listener ID are managed by threads of the same network process.
There are particular network process types for CMX and socket connections. CMX connections use a process type called utmnet, and socket connections use utmnets or utmnetssl.
 | Listener IDs can be defined in the ACCESS-POINT statement for access points and in the BCAMAPPL statement for application names:
This assigns a listener ID to the access point or application name as administrative information. Due to the different types of net processes, the listener IDs for CMX connections and the listener IDs for Socket or SSL Socket connections are separate value ranges. |
The connection is assigned to a network process by means of the listener ID allocated to the local application name or the local access point. openUTM assigns the listener ID 0 to all application names and access points for which a listener ID has not been explicitly defined. All of these connections are then served by a single network process.
Unix-, Linux- und Windows-Systeme
Please note that only a maximum of 1000 connections can be established per network process at a time. If you need moreconnections in your application, you must define several local application names e.g. local access points. For Details see BCAMAPPL statement in section "BCAMAPPL - define additional application names" e.g. ACCESS-POINT statement in section "ACCESS-POINT - create an OSI TP access point".