U184 | &OBJ1 DMS error &DMSE for file &FNAM Action: See the DMS error code in Error codes or inform system service. |
U185 | kdcdef not allowed during application run Action: User error. You can update the proxy container configuration only after you have stopped the proxy container. |
U189 | &OBJ1 ( &PTRM, &PRNM ): IPC shortage of &IPCOBJ &IPCREAS Action: For the meaning of the inserts &IPCOBJ and &IPCREAS see the table below. For inserts which are not contained in the table inform system service. &IPCOBJ | &IPCREAS | Meaning | Action | TSAP | tsapname | UTM network process not yet started.
It was not possible to log in at transport system | Normal behavior at application start.
Otherwise:
Check BCAMAPPL and ACCESS-POINT in UTM generation. | EXTP
EXTP
EXTP | WORK USED
NET USED
EXTP USED | Entire process administration table in use | Check UTM generation regarding semaphores | NET | PROC DEAD | UTM network process terminated. | See the earlier message U3nn. | LETT | IPC FULL | Data area already too full to take any more data for this connection. | Check UTM generation or UTM_IPC_LETTER environment variable (see note below). | LETT | EXTP FULL | Data area for received messages already fully occupied. | Check UTM generation or UTM_IPC_LETTER environment variable (see note below). | LETT | USED | Data area is occupied. | Check UTM generation or UTM_IPC_LETTER environment variable (see note below). | LETT
LETT | MAX ILETT
MAX OLETT | Maximum data area per connection in use. | Check UTM generation or UTM_IPC_EXPT_LETTER environment variable (see note below). | SEMA | USED | Maximum number of semaphores in use. | Check UTM generation or UTM_IPC_EXPT_LETTER environment variable (see note below). |
|
U190 | &OBJ1 SHM error ( key: &SHMKEY, lth: &SHMLTH): &UERRNO The insert &UERRNO has the following meaning: &UERRNO | Meaning | Action | 1 | The shared memory cannot be established with the specified size. | User error.
Action: If necessary, the system has to be tuned. Please refer to the release notes. | 2 - 5 | The shared memory cannot be established. | Inform system service. |
|
U205 | utmtimer: Error &UERRNO during utmtimer run The insert &UERRNO has the following meaning: &UERRNO | Meaning | 1 - 11 and 13 - 21 | Internal error. | 12, 22, 32 | Proxy container is being terminated. | 29 - 31, 40 | Internal error. |
|
U206 | utmtimer: Message with incorrect type received Action: Inform system service. |
U207 | utmtimer: Reallocation of timer list from &DIA1 to &DIA2 elements Action: Inform system service. |
U223 | &OBJ1 UTM application &APPL still running according to internal status, applifile: &OBJ3 You have tried to start the proxy container more than once. |
U227 | &OBJ1 UTM application &APPL terminated by kdcrem Action: Remove script or Forced Clear has been activated. |
U228 | utmmain: Read error on pipe, errno: &ERRNO Action: Inform system service. |
U229 | utmmain: &OBJ1 process died, pid: &PID, &SIGEXIT ( &STRTIME ) Action: Inform system service. |
U231 | utmmain: utmwork process died, pid: &PID
unexpected exit code: &EXTCODE &SIGEXIT ( &STRTIME ) Action: Inform system service. |
U304 | &OBJ1 ( pid: &PID, &TNSNAME ): &NETFCT call: Error &NETERR Error during activation of communication endpoint &NETFCT. Action: Configuration problem (see message U305) or inform system service. |
U305 | &OBJ1 ( pid: &PID): CMX application &BCAP already attached Error during activation of communication endpoint &BCAP. This communication endpoint is not unique on the host. Action: The communication endpoints depend on the container name and the generated container port number. The used communication endpoints are written to the file <Proxy_home>/def/input.system.txt (BCAMAPPL <communication endpoint>). You must install the proxy container with another container name or port number. |
U306 | &OBJ1 ( pid: &PID, &TNSNAME ): Error &UERRNO during process run Action: See the table below. The insert &UERRNO has the following meaning: &UERRNO | Meaning | Action | 1 - 11 | Internal error during container connection setup. | Inform system service. | 12 | No work process when receiving. | Normal behavior when the proxy container terminates. | 13 | Internal error during container connection setup. | Inform system service. | 14 | Concurrent clearing of connections. | Normal behavior. | 19 - 21 | Internal error during container connection setup. | Inform system service. | 22 | No work process when sending - application terminated. | Normal behavior when the proxy container terminates. | 23 - 24 | Internal error during container connection setup. | Inform system service. | 25 | Connection was cleared down by the container. | Normal behavior. | 26 | Connection cleardown was identified on sending. | Normal behavior. | 27 - 36 | Internal error during container connection setup. | Inform system service. | 37 - 38 | Login for local communication endpoints was unsuccessful (error when activating the communication endpoint) | User error: Change the configuration, see also U304/U305. | 41 - 43 | Internal error during container connection setup. | Inform system service. | 44 | Recipient of connection setup request could not be determined. | User error: Change the configuration. | 45 | Connection already cleared down. | Normal behavior. | 46 | Invalid port number on connection setup request from UTM | User error: Generation incorrect or incomplete | 47 - 58 | Internal error during container connection setup. | Inform system service. | 82 | Sender of connection setup request could not be determined. | User error: Change the configuration. | 83 - 283 | Internal error during container connection setup. | Inform system service. |
|
U307 | &OBJ1 ( pid: &PID, &TNSNAME ): Invalid event &EVENT Action: Inform system service. |
U309 | &OBJ1 ( pid: &PID, &TNSNAME ): KDCSTRMA called - reason: &TRMA ( &STRTIME ) Action: Inform system service. |
