Messages of the network processes

U301

&OBJ1 ( pid: &PID ): Invalid number of arguments

U303

&OBJ1 ( pid: &PID, &NETPROC ): &TNSPROP does not exist for &TNSNAME

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

U304

&OBJ1 ( pid: &PID, &TNSNAME ): &NETFCT call: Error &NETERR

The error causes in U304 relate to the UTM-internal mapping of the CMX transport interface to the socket interface in the utmnets process.

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

The meaning of the NETFTC and NETERR inserts is given in the table on "Inserts in U messages".

U305

U306

&OBJ1 ( pid: &PID ): CMX application &BCAP already attached

&OBJ1 ( pid: &PID, &TNSNAME ): Error &UERRNO during process run

The insert &UERRNO has the following meaning:

&UERRNO	Meaning	Response
	Problems during attaching to the IPC shared memory
1	Parameter error during sign-on; network process inconsistently linked	PR
2	Network process started too often	User error
3	No additional can be started because the administration table is completely occupied	PR
4	Buffer bottleneck at sign-on	PR
9	Unexpected return code during sign-on	PR
	Problems when receiving messages from the work processes
11	Parameter error when receiving; network process inconsistently linked	PR
12	No work process when receiving	Normal behavior when an application terminates
13	Invalid message received from work process	PR
14	utmmain process has initiated the termination of the work process	Subsequent error
19	Unexpected return code when receiving	PR
	Problems when sending messages to the work processes
21	Parameter error when sending; network process inconsistently linked	PR
22	No work process when sending - application terminated	Normal behavior when an application terminates
23	Buffer bottleneck when sending to work process	Normal behavior under high loads
24	UTM buffer locked for sending	PR
25	Connection was cleared down by openUTM	Normal behavior
26	Connection cleardown was identified on sending	Normal behavior
27	Waiting for a resource to be released on sending. Note: This message is output once a second as of the 2nd second.	Normal behavior under high loads
29	Unexpected return code when sending	PR
	General problems when running net processes
34	Memory bottleneck on receiving data in the network process	Normal behavior under high loads
35	Memory shortage in the network process while storing an utput message because sends are not permitted	Normal behavior under high loads
36	Stored output message not found.	PR
37	Sign-on failed for a local communication end point	User error UTM generation incorrect or incomplete or port occupied by another application. In the case of the implicit BCAMAPPL which is formed from the application name, this is port 0. The implicit BCAMAPPL can also be explicitly defined with a port; see U320 / U323.
38	Invalid send data request	PR
39	Length of the message received from ICMX(L) is greater than 64K	User error Message sent by partner system is too long
41	Invalid sender in connection setup request to openUTM	PR
42	Buffer bottleneck when processing connection setup request from openUTM	PR
43	Internal status incompatible with connection setup request from openUTM	PR
44	It was not possible to determine any IP address for the host name of the recipient of the connection setup request from openUTM.	User error UTM generation incorrect or incomplete
45	Connection cleardown contention: The partner application has already cleared down a connection over which openUTM wishes to send a further message.	Normal behavior
46	Invalid port number on connection setup request from openUTM	User error UTM generation incorrect or incomplete
47	Error getting address of recipient of connection setup request from openUTM with t_getaddr()	PR
48	Error constructing address of recipient of connection setup request from openUTM with t_setaddr()	PR
49	Error while converting a generic host na to the host name of the recipient	PR
50	Invalid address on connection setup request from openUTM	User error UTM generation incorrect or incomplete, see U319
51	Recipient‘s address used for connection setup by openUTM is not available in the TNS	User error TNS generation incorrect, see U303
52	Template address could not be fetched	PR, see U313
82	Sender of connection setup request from ICMX(L) could not be determined	User error UTM generation incorrect or incomplete
83	Recipient of connection setup request from ICMX(L) is not known	PR
84	Buffer bottleneck when determining connection ID during processing of a connection setup request from ICMX(L)	User error Increase number of semaphores
85	Application end was detected when sending ICMX(L) connection request to a work process.	PR or normal behavior on end of application
86	Buffer bottleneck when processing connection setup request from ICMX(L)	Increase number of semaphores or or maximum number of connections
87	Internal status does not correspond to connection setup confirmation from ICMX(L)	PR
88	Invalid connection setup confirmation from ICMX(L)	PR
89	Invalid connection cleardown from ICMX(L)	PR
100	Error on call of semaphore in IPC receive thread	PR or normal behavior on end of application
101	Error while sending socket message in IPC receive thread	PR
	Problems during transport system calls
201	t_attach in socket network process. Parameter error: option pointer is NULL	PR
202	t_attach in socket network process. Parameter error: invalid option structure	PR
203	t_attach in socket network process. Initialization of socket environment failed	PR
204 205 206	t_attach in socket network process. Shortage of resources at the IPC shared memory when attaching to the transport system.	PR
211	t_event in socket network process. Parameter error: option pointer is NULL	PR
212	t_event in socket network process. Parameter error: invalid option structure	PR
213	t_event in socket network process. Parameter error: invalid value for Cmode	PR
214	t_event in socket network process. Parameter error: invalid connection cleardown stored	PR
215	t_event in socket network process. Not enough freely available sockets	Increase number of socket network processes.
216	t_event in socket network process. An unexpected except socket occurred with the select call.	Client cannot send out-of-band data.
217	t_event in socket network process. An incoming connection request could not be accepted.	User error Maximum number of connections that can be established at a time has been reached.
221	t_conrq in socket network process. Parameter error: invalid option structure	PR
222	t_conrq in socket network process. Not enough freely available sockets	Increase number of socket network processes.
223	t_conrq in socket network process. bind() call for sender address was unsuccessful.	Check UTM generation and network
224	t_conrq in Socket net process. Invalid recipient address.	Check UTM generation
226	t_conin in socket network process. Parameter error: invalid value for transport reference	PR
227	t_conin in socket network process. Parameter error: a connection cleardown already exists for the specified transport reference	PR
228	t_conin in socket network process. Parameter error: the specified transport reference is no longer valid	PR
231	t_concf in socket network process. Parameter error: invalid value for transport reference	PR
232	t_concf in socket network process. Parameter error: a connection cleardown already exists for the specified transport reference	Normal behavior
235	t_conrs in socket network process. Parameter error: invalid value for transport reference	PR
236	t_conrs in socket network process. Parameter error: invalid option structure	PR
237	t_conrs in socket network process. Parameter error: a connection cleardown already exists for the specified transport reference	Normal behavior
238	t_conrs in socket network process. Parameter error: the specified transport reference is no longer valid	Normal behavior
241	t_datain in socket network process. Parameter error: invalid value for transport reference	PR
242	t_datain in socket network process. Parameter error: there is no data for the specified transport reference	PR
243	t_datain in socket network process. Parameter error: invalid value for data length	PR
244	t_datain in socket network process. Parameter error: a connection cleardown already exists for the specified transport reference	Normal behavior
251	t_datarq in socket network process. Parameter error: invalid value for transport reference	PR
252	t_datarq in socket network process. Parameter error: invalid value for data length	PR
253	t_datarq in socket network process. Parameter error: a connection cleardown already exists for the specified transport reference	Normal behavior
254	Buffer shortage when saving a message for sending at a later time.	Shortage results in disconnection
261	t_disin in socket network process. Parameter error: invalid value for transport reference	PR
266	t_disrq in socket network process. Parameter error: invalid value for transport reference	PR
281	t_info in socket network process. Parameter error: invalid value for transport reference	PR
282	t_info in socket network process. Parameter error: option pointer is NULL	PR
283	t_info in socket network process. Parameter error: invalid option structure	PR
	Problems concerning openSSL
301*)	The openSSL library could not be loaded.	User error e.g. missing or uncorrect environment variable UTM_SSL_LIBRARY
302*)	Method TLSv1_2 could not be specified: (SSL call: TLSv1_2_method())	User error e.g. wrong version of openSSL library
303*)	Variable TLS Method could not be specified: (SSL call: TLS_method())	User error e.g. wrong version of openSSL library
304*)	SSL context could not be created. (SSL call: SSL_CTX_new())	User error
305*)	SSL certificat could not be loaded (SSL call: SSL_CTX_use_certificate_file())	User error Check entry RSACertificateFile in configfuration file
306*)	SSL private key could not be loaded (SSL call: SSL_CTX_use_PrivateKey_file())	User error Check entry RSAKeyFile in configuration file
307*)	Check SSL private key and certificate failed (SSL call: SSL_CTX_check_private_key())	User error Check entries RSACertificateFile and RSAKeyFile in configuration file
311*)	The file <filebase>/utm.ssl.conf could not be opened.	User error e.g. configuration file missing
312*)	Invalid content of file <filebase>/utm.ssl.conf	User error
313*)	File <filebase>/utm.ssl.conf does not contain an entry RSACertificateFile	User error
314*)	File <filebase>/utm.ssl.conf does not contain an entry RSAKeyFile	User error
316	SSL structure for socket connection could not be created (SSL call: SSL_new())	User error
321	On a connection for a BCAMAPPL with SECURE=YES unencrypted data was received.	User error Client has used a wrong port number for addressing
322	Error during SSL communication (read)	User error
323	Buffer shortage when saving a SSL message for sending at a later time.	Shortage results in disconnection
324	Error during SSL communication (write)	User error
	General problems during communication over RFC1006 protocol
331	Buffer shortage when saving a message part of a protocol element	Shortage results in disconnection
332	Parameter error: Invalid type of element when building a protocol element	PR Error results in disconnection
333	Parameter error: Invalid length of the erroneous TPDU protocol element when building a protocol element of type ER-TPDU	PR Error results in disconnection
334	Parameter error: Erroneous TPDU protocol element is missing when building a protocol element of type ER-TPDU	PR Using protocol class 0  the erroneous protocol element must be send within an ER-TPDU protocol element as an error information. Error results in disconnection
335	Protocol element CC-TPDU could not be send	Error results in disconnection
	General protocol errors during communication over RFC1006 protocol
341	RFC protocol error - invalid protocol version in protocol header	Client sends erroneous protocol data Error results in disconnection Note: Problem may occur when a socket client initiates a connection request to a net process which only manages connections for BCAMAPPL with T-PROT=RFC1006 or ACCESS-POINTs. i.e. the Client has used a wrong port number for addressing
342	RFC protocol error - invalid value for a reserved field in protocol header	Client sends erroneous protocol data Error results in disconnection
343	RFC protocol error - invalid value for total length of protocol element	Client sends erroneous protocol data Error results in disconnection
344	RFC protocol error - invalid value for field LI in ISO8073 protocol	Client sends erroneous protocol data Error results in disconnection
345	RFC protocol error - value of field LI in ISO8073 protocol does not match total length of protocol element	Client sends erroneous protocol data Error results in disconnection
346	RFC protocol error - Protocol element of type CR-TPDU is not allowed in this state	Client sends erroneous protocol data CR-TPDU protocol element must only be send immediately after connection confirmation. Error results in disconnection
347	RFC protocol error - Protocol element of type DC-TPDU was received	Client sends erroneous protocol data DC-TPDU protocol element is not allowed in protocol class 0. Error results in disconnection
348	RFC protocol error - A protocol element unequal to type CR-TPDU was received	Client sends erroneous protocol data First protocol element after connection confirmation must be a CR-TPDU element. Error results in disconnection
349	RFC protocol error - Invalid type of a protocol element was received	Client sends type of protocol element which is not supported by openUTM Error results in disconnection
	Protocol errors concerning CR-TPDU protocol element
351	RFC protocol error -  invalid value for ISO length in the protocol element of type CR-TPDU	Client sends erroneous protocol data Error results in disconnection
352	RFC protocol error - invalid value for field 'credit' in the protocol element of type CR-TPDU	Client sends erroneous protocol data Error results in disconnection
353	RFC protocol error - invalid value for field 'option' in the protocol element of type CR-TPDU	Client sends erroneous protocol data Error results in disconnection
354	RFC protocol error - invalid length for the value of the transport selector of the sender in the protocol element of type CR-TPDU	Client sends erroneous protocol data Error results in disconnection
355	RFC protocol error - invalid length for the value of the transport selector of the receiver in the protocol element of type CR-TPDU	Client sends erroneous protocol data Error results in disconnection
356	RFC protocol error - invalid parameter length for max TPDU in the protocol element of type CR-TPDU	Client sends erroneous protocol data Error results in disconnection
357	RFC protocol error -  invalid value for maximal length of a protocol element in the protocol element of type CR-TPDU	Client sends erroneous protocol data Error results in disconnection
358	RFC protocol error - invalid parameter code value in the protocol element of type CR-TPDU	Client sends erroneous protocol data Error results in disconnection
359	RFC protocol error - value for the transport selector of the receiver is missing in the protocol element of type CR-TPDU	Client sends erroneous protocol data When communicating with openUTM, sending of the called transport selector is mandatory. Error results in disconnection
360	RFC protocol error - value for transport selector of the sender is missing in the protocol element of type CR-TPDU	Client sends erroneous protocol data When communicating with openUTM, sending of the calling transport selector is mandatory. Error results in disconnection
361	RFC protocol error -  the value for the length of user data in the protocol element of type CR-TPDU is more then 65	Client sends erroneous protocol data openUTM supports a maximal length of 65 for CR-TPDU user data. Error results in disconnection
	Protocol errors concerning CC-TPDU protocol element
371	RFC protocol error - invalid value for ISO length in the protocol element of type CC-TPDU	Client sends erroneous protocol data Error results in disconnection
372	RFC protocol error - invalid value for field 'option' in the protocol element of type CC-TPDU	Client sends erroneous protocol data Error results in disconnection
373	RFC protocol error - invalid length for  the value of the transport selector of the sender in the protocol element of type CC-TPDU	Client sends erroneous protocol data Error results in disconnection
374	RFC protocol error - invalid length for the value of the transport selector of the receiver in the protocol element of type CC-TPDU	Client sends erroneous protocol data Error results in disconnection
375	RFC protocol error - invalid parameter length for max TPDU in the protocol element of type CC-TPDU	Client sends erroneous protocol data Error results in disconnection
376	RFC protocol error - invalid value for maximal length of a protocol element in the protocol element of type CC-TPDU	Client sends erroneous protocol data Error results in disconnection
377	RFC protocol error - invalid parameter code value in the protocol element of type CC-TPDU	Client sends erroneous protocol data Error results in disconnection
378	RFC protocol error - the value for the length of user data in the protocol element of type CC-TPDU is more then 65	Client sends erroneous protocol data openUTM supports a maximal length of 65 for CC-TPDU user data. Error results in disconnection
	Protocol errors concerning DT-TPDU protocol element
381	RFC protocol error - invalid value for ISO length in the protocol element of type DT-TPDU	Client sends erroneous protocol data Error results in disconnection
	Protocol errors concerning DR-TPDU protocol element
385	RFC protocol error - invalid value for ISO length in the protocol element of type DR-TPDU	Client sends erroneous protocol data Error results in disconnection
386	RFC protocol error - invalid length of error information in the protocol element of type DR-TPDU	Client sends erroneous protocol data Error results in disconnection
387	RFC protocol error - invalid parameter code value in the protocol element of type DR-TPDU	Client sends erroneous protocol data Error results in disconnection
	Protocol errors concerning ER-TPDU protocol element
391	RFC protocol error - invalid value for ISO length in the protocol element of type ER-TPDU	Client sends erroneous protocol data Error results in disconnection
392	RFC protocol error - invalid length of error information in the protocol element of type ER-TPDU	Client sends erroneous protocol data Error results in disconnection
393	RFC protocol error - invalid parameter code value in the protocol element of type ER-TPDU	Client sends erroneous protocol data Error results in disconnection

*) Message U306 with this error reason causes an abnormal termination of the UTM application.

U307

&OBJ1 ( pid: &PID, &TNSNAME ): Invalid event &EVENT

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

U308

&OBJ1 ( pid: &PID, &TNSNAME ): UTM application &APPL terminated

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

U309

&OBJ1 ( pid: &PID, &TNSNAME ): KCSTRMA called - reason: &TRMA (
&STRTIME )

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

The insert &TRMA describes the reason (TRMA reason) for the abnormal termination of the application.

A list of the termination codes, an explanation, and, if required, recommendations for changing the application's configuration can be found in section “UTM dump error codes”.

For a more detailed diagnosis, please also see the most recent U messages.

U310

U311

U312

&OBJ1 ( pid: &PID, &APPL ): Invalid fork() call errno: &ERRNO

&OBJ1 ( pid: &PID, &APPL ): Starting error errno: &ERRNO

&OBJ1 ( pid: &PID, &TNSNAME ): Resource bottleneck on transmission

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

U313

&OBJ1 ( pid: &PID, &NETPROC ): Warning: &TNSNAME not found in TNS

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

U314

U315

&OBJ1 ( pid: &PID, &NETPROC ): &HST4 changed to &HST1

&OBJ1 ( pid: &PID ): Network message: &TNSNAME &NETREAS

The insert &TNSNAME has the following structure:

partner name / UTM processor name / ([real processor name /] ip address)

All information is related to the communication partner of the connection

The individual name parts have the following meaning:

Name part	Meaning
partner name	Name of the partner application. For socket connections this is the socket port number of the partner application.
UTM processor name	Internal processor name. This is either a processor name shortened to eight characters or a generic processor name.
real processor name	Real processor name (only if not equal to the UTM processor name)
ip address	IPv4 or IPv6 address of the partner application

The insert &NETREAS has the following meaning:

&NETREAS	Meaning
1	Connection setup confirmation for a connection already set up by the partner
2	Rejection of the connection setup request for a connection already cleared down by the partner
3	Connection cleardown for a connection already cleared down by the partner
6	Network main process detected that the application was terminated
7	Message received from openUTM for a connection which has already been cleared down
11	openUTM rejected a request to establish a connection
12	openUTM received request to clear down connection
13	Partner received request to clear down connection
14	Partner detected that the connection has been cleared down when sending data
15	Partner detected that the connection has been cleared down when receiving data
20	Active connection setup
21	Passive connection setup

U316

&OBJ1 ( pid: &PID, &NETPROC ): TSEL-FORMAT(&NETNAME) change: &TFOLD to &TFNEW.

&TFOLD corresponds to the value of TSEL-FORMAT (format of the transport selectors), &TFNEW corresponds to the new value TSEL-FORMAT.

The inserts have the following meanings:

&TFOLD /&TFNEW	Meaning
?	Undefined TSEL-FORMAT (not for &TFNEW)
T	TRANSDATA format
E	EBCDIC character format
A	ASCII character format

The KDCDEF generation should be checked.

Recommendation: Set the TSEL-FORMAT in the corresponding KDCDEF statement.

U317

&OBJ1 ( pid: &PID, &NETPROC ): &TNSNAME CMX error(&CMXERR) in &CMXFUNC.

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

The insert &CMXERR contains the CMX error codes (see the CMX manual).

U318

&OBJ1 ( pid: &PID, &NETPROC ): Listen-port(&TNSNAME) : &LPOLD not valid.

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

The insert &LPOLD corresponds to the current values of LISTENER-PORT (listener port number), where only the port numbers 102, 1025 through 32767 are allowed.

The KDCDEF generation should be checked.

Recommendation: set the LISTENER-PORT in the corresponding KDCDEF statement.

U319

&OBJ1 ( pid: &PID, &NETPROC ): IP address (0.0.0.0) for proname &PNAM not valid.

There is an invalid IP address stored for the partner &NETPROC.

The KDCDEF generation or the name service (e.g hosts file on Unix, Linux or Windows systems) should be checked.

Recommendation: after checking, the IP address should be changed using the dynamic administration or WinAdmin/WebAdmin using the function KC_UPDATE_IPADDR.

U320

&OBJ1 ( pid: &PID, &TNSNAME ): &SOCKFCT call: Error &ERRNO

The meaning of the &TNSNAME insert is given at the U315 message on "Messages of the network processes".

Error on socket function call &SOCKFCT. The insert &ERRNO corresponds to the return code of the socket function call &SOCKFCT.

U321

&OBJ1 ( pid: &PID ): Connection request rejected ( &TNSNAME )

A connection request from the partner application was rejected, because there is no suitable application name in the UTM application for the addressed T selector.

The insert &TNSNAME has the following structure:

port number / T selector / ip address

The individual name parts have the following meaning:

Namensteil	Bedeutung
port number	local port number of the utm application to which the connection  request was addressed by the partner application.
T-Selektor	T selector - in hexadecimal format - which was given as a reciever application name in the connection request of the partner application.
IP-Adresse	IPv4 or IPv6 address of the partner application

U323

&OBJ1 ( pid: &PID ): &BCAP port &PORT permission denied