UTM Messages when rejecting connection requests

Communication between two UTM applications resp. a client application and an UTM application takes place via netprocesses.

There are three types of netprocesses, one for each type of client resp. protocol.

• • utmnet – netprocess for
    • OSI-TP and LU6.1 communication
    • communication with clients of type UPIC-R and APPLI
  • utmnets – socket netprocess for
    • communication with USP-Socket applications
    • communication with HTTP clients without encryption
  • utmnetssl – socket netprocess for
    • communication with HTTP clients with TLS encryption
    • communication with secure USP-Socket applications

In order for a connection to be established between a partner application (UTM application or client) and an UTM application, two conditions must be met:

1. The partner application must address the network process that is responsible for this partner type.

2. The transport selector (T-SEL), addressed by the partner application when the connection is established, must be configured in UTM in the same format (ASCII/EBCDIC/TRANSDATA) and with the appropriate partner type.

If this is not the case, the attempt to establish a connection is rejected by the UTM application. openUTM then creates certain messages that are output by default to STDOUT, STDERR and (some) also to SYSLOG, see Targets of UTM messages. The messages that appear depend on how the BCAMAPPL or ACCESS-POINT is generated.

Examples of the output of messages in the case of negative connection attempts

utmnet

BCAMAPPL ..., T-PROT=RFC1006

1. U321
   Invalid transport selector (T-SEL)
   Attempt to establish a connection to a suitable network process, but with a T-SEL that is not configured in UTM.
   Note: The presentation of the T-SEL takes place in hexadecimal format.
   
   
2. U306 with UERRNO=341
   protocol error
   Attempt to establish a connection to a netprocess of type utmnet from a socket client.

utmnets

1. BCAMAPPL ..., T-PROT=SOCKET without TPOOL
   K036 with RSLT=N, REA1=11
   U315 with NETREAS=12
   partner unknown
   Attempt to establish a connection to a socket netprocess from a UPIC or HTTPS client.
   
   
2. BCAMAPPL ..., T-PROT=(SOCKET,*HTTP), with TPOOL
   K036 with RSLT=Y
   U315 with NETREAS=21
   K033
   connection request is accepted (for now) because of socket TPOOL
   K064
   K070
   K069
   U315 with NETREAS=12
   K154 with TCPCL=DISCONNECT_REQ
   connection request is then rejected because of an invalid HTTP protocol
   Attempt to establish a connection to a socket netprocess from a UPIC or HTTPS client.
   
   

utmnetssl

BCAMAPPL ..., T-PROT = (SOCKET,*HTTP,SECURE)

1. U306 with UERRNO=321
   partner sends invalid TLS data
   Attempt to establish a connection to a socket TLS netprocess from a partner who sends no valid TLS data.