UPIC is a lean, highly efficient and easy-to-use carrier system that is customized for use with openUTM as the server. In UPIC, the client program always initiates communication. The UPIC protocol is used for communication.
A UPIC client can optimally use the UTM functions because
UPIC supports the transfer of format names and function keys, for example.
UPIC supports the encryption of system access and user data.
UPIC can use the SIGNON event service (see "System access control (identification and authentication)" for more information).
A UPIC client can request the status of the last transaction after a malfunction and is therefore included in the openUTM restart concept.
A UPIC client can maintain several conversations simultaneously during a program run (“multi-conversations”) as long as the corresponding system supports multi-threading.
UPIC clients can use the “multi-signon” function. In other words, a number of UPIC clients can sign on at the same time using the same UTM user ID if service restarting is dispensed with for this user ID.
A UPIC client can establish several parallel transport connections to a UTM application under the same application name (multi-connect”).
UPIC provides simple load distribution functionality for communication with UTM cluster applications. The UPIC client communicates with one of the associated node applications. This application is selected at random. For more details, see "High availability and load distribution with UTM cluster applications".
Workload Capture & Replay can be used to simulate load situations for UPIC clients, see section “Workload Capture & Replay”.
UPIC is available for all major Unix, Linux and Windows platforms and for BS2000 systems.