BCSYSEX | K009 Transaction code &TAC is invalid (&RCDC) - input please Invalid service name called by an EIS using a UPIC, Socket or RFC1006 connection.
Action: The table below lists the possible error codes together with error causes and possible error recovery actions. If an error message occurs that is not described in the list below, inform system service. Error code &RCDC &RCDC | Meaning | KM01 | The service has not been generated. Action: Configure an inbound service and assign this service name to the inbound message endpoint or change the client program. |
|
BCSYSEX | K017 Service &TCVG terminated by openUTM (&RCCC/&RCDC &RCF2A) - input please An inbound transaction was rolled back. Action: Normal behavior if &RCCC is 70Z and &RCDC is K306. Otherwise inform system service. |
K036 | Connection setup: &PTRM/&PRNM/&BCAP/<RM &RSLT, &REA1 BeanConnect outputs the message when the connection from the resource adapter to the proxy container is set up. &RSLT | Meaning | Y | Connection set up. | N | Connection was not set up; the cause is given in &REA1. |
&REA1 | Meaning | X' 00' | Connection already set up. | X' 0A' | BeanConnect proxy container shut down. Action: Start the BeanConnect proxy container. | X' 0C' | Connection cleardown being executed. Action: Repeat the request. | X' 12' | No further free entry available in terminal pool. Action: Depends on the insert <ERM. | X' 1B' | The IP address of the EIS partner could not be determined Action: Check EIS partner host and /or inform network administration | X' 2E' | The connection has not yet been completely cleared down. Action: Repeat the request. |
<ERM | Meaning | BCRA | Action: Increase the Number of Parallel Outbound Connections in the Performance Settings tab of the Edit Properties of Proxy property sheet in the Management Console. | BCUP | Action: Increase the Number of Parallel Inbound UPIC Connections in the Performance Settings tab of the Edit Properties of Proxy property sheet in the Management Console. | BCSO | Action: Increase the Number of Parallel Inbound Socket Connections in the Performance Settings tab of the Edit Properties of Proxy property sheet in the Management Console. |
|
K040 | Warning level &WLEV for &PGPOOL no longer exceeded This message is only output if message K041 was previously output and means that the measures recommended there are currently no longer necessary. |
K041 | Warning level &WLEV for &PGPOOL exceeded Action: Increase the Proxy Container Storage Area Size (Page Pool) in the Performance Settings tab of the Edit Properties of Proxy property sheet using the Management Console and carry out the todo topics which are shown in the todo topic list of the Management Console. |
K043 | DMS error &DMSE for file &FNAM The DMS error code is output in insert &DMSE. Action: The possible DMS error codes are described in Error codes . Alternatively inform system service. |
K049 | Error = &RCCC2 during application startup The BeanConnect proxy container issues message K049 whenever the start of a container task is aborted due to an error. The error code &RCCC2 shows the cause of the error.
Action: The table below lists the possible error codes together with error causes and possible error recovery actions. If an error message occurs that is not described in the list below, inform system service. Error code &RCCC2 Code | Error cause | Action | 20 | Shared memory cannot be allocated by the first task of the BeanConnect proxy container due to insufficient address space. | Check system generation. | 21 | Shared memory cannot be allocated by the first task of the BeanConnect proxy container due to insufficient address space or due to the proxy container being terminated. | As for 20 or normal behavior. | 22 | File access error. | See DMS error code, Error codes . | 24 | File access error. | See DMS error code, Error codes . | 32 | The task lock bourse could not be created. This error occurs when there are too few semaphore entries available for the BeanConnect processes. This can occur when the termination of a process and its restart overlap. | Start again with a larger number of semaphores (see the Number of semaphores in the proxy container ). | 33 | BeanConnect refuses to start more tasks for the proxy container because the proxy container has already terminated (normal or abnormal termination). | Normal behavior. | 35 | While restarting a proxy container task, BeanConnect detects that the proxy container is being aborted. | Normal behavior. | 50 | As for 20. | Check system generation. | 55 | DMS error with KDCA file. | See DMS error code, Error codes . | 56 | DMS error with page pool file. | See DMS error code, Error codes . | 57 | DMS error with restart file. | See DMS error code, Error codes . | 58 | Error with the SYSLOG file of the BeanConnect proxy. Possible causes: The <Proxy_home>/SYSLOG directory is not correct. | Delete (if necessary) and regenerate the prepared SYSLOG file in the <Proxy_home> directory with following commands: | 59 | Error when opening SYSLOG file. | See DMS error code, Error codes . | 79 | A BeanConnect proxy container task makes a request, but it runs out of memory. | Check system generation. | 84 | Insufficient memory. | Check system generation. | 85 | Insufficient memory. | Check system generation. | 91 | Error when starting BeanConnect proxy container. You can find a detailed description of the error under message K124. | See message K124 on K messages. |
|
K055 | Asynchronous service &ATAC1 terminated by openUTM; KCRCCC=&RCCC; KCRCDC=&RCDC;user=&USER; LTERM=<RM An asynchronous inbound transaction was rolled back and the asynchronous inbound message will be redelivered if necessary. Action: Normal behavior when KCRCCC is 000 and KCRCDC is 0000 or KCRCCC is 70Z and KCRCDC is K306. Otherwise inform system service. |
K060 | Application run aborted; reason = &TRMA BeanConnect creates a memory dump whenever a proxy container application is aborted or a dump requested. Such a dump is produced for each work process of the proxy container. The Group column in the table below describes the reason group to which the dump error code (&TRMA) belongs. The following groups exist: A | The cause is a user error, e.g. an error in | D | The dump was created for diagnostic purposes. | F | The dump is a continuation dump, another task has caused the BeanConnect proxy container to terminate abnormally. | M | The cause is a memory bottleneck. | U, S, X | The cause is an internal error in BeanConnect. |
If an error message occurs that is not described in the list below, inform system service. Code | Group | Reason | ALGxxx | ASU | Shared memory bottleneck.
Action: Tune the system kernel. | ASIS99 | D | BeanConnect proxy container was terminated abnormally by the administrator. | BRSREM | F | BeanConnect proxy container was terminated abnormally by the administrator. | CACHT1 through CACHT6 | F | After a process has initiated the abnormal termination of the BeanConnect proxy container, another task of the BeanConnect proxy container has terminated abnormally itself (= continuation dump).
Action: Depends on the reason for the abnormal termination of the proxy container. | DIAGDP | D | A diagnostic dump has been generated. The BeanConnect proxy container is running normally. | ENDE14 | F | As for code CACHT1. | ENDPET | A | The BeanConnect proxy container cannot be terminated normally because distributed transactions still exist with the status PTC (prepare to commit). The transaction can be terminated after the BeanConnect proxy container has been restarted. Additionally, a connection to the EIS partners that are involved in the distributed transactions must exist.
Action: Restart the BeanConnect proxy container. | FMMM10 | A | An input message cannot be stored because the page pool is full.
Action: Increase the Proxy Container Storage Area Size (Page Pool) in the Performance Settings tab of the Edit Properties of Proxy property sheet in the Management Console. | IOyxxx | ASU | An unrecoverable error has occurred during file processing, yxxx = DMS error code, see the section Error codes . | IPC035 | A | Error on locking the IPC shared memory segment. This may be caused by the remove script being called or by a Forced Clear while the BeanConnect proxy container is still running. | IPC037 | FU | After a process has initiated abnormal termination of the BeanConnect proxy container, another task of the BeanConnect proxy container has terminated abnormally itself (= continuation dump). | IPCEND | FU | After a process has initiated abnormal termination of the BeanConnect proxy container, another process of the BeanConnect proxy container has terminated abnormally itself (= continuation dump). | IPCREM | F | The BeanConnect proxy container was terminated abnormally with the remove script or Forced Clear. | ISLPT1 through ISLPT4 | F | As for code CACHT1. | LATCT1 | F | As for code CACHT1. | JVMABT |
| The JVM has initiated the abnormal termination of the BeanConnect proxy container, see also file hs_err*.log in the proxy container directory | LCACT1 | F | As for code CACHT1. | LKAA04 | US | As for code CACHT1. | LKAAT1 | F | As for code CACHT1. | LKLCT1 through LKLCT4 | F | As for code CACHT1. | LPCMT1 | F | As for code CACHT1. | OSAFT2 | F | As for code CACHT1. | OSTM07 | A | A log record for a distributed transaction cannot be backed up, since the page pool is full.
Action: Increase the Proxy Container Storage Area Size (Page Pool) in the Performance Settings tab of the Edit Properties of Proxy property sheet in the Management Console. | PCMM05 | AU | The page pool is full.
Action: Increase the Proxy Container Storage Area Size (Page Pool) in the Performance Settings tab of the Edit Properties of Proxy property sheet in the Management Console. | PEND02 | A | No further data can be written because the page pool is full.
Action: Increase the Proxy Container Storage Area Size (Page Pool) in the Performance Settings tab of the Edit Properties of Proxy property sheet in the Management Console. | PENDER | AUD | A dump was created after abnormal termination of a transaction. Before this, the message K017 or K055 was output. The proxy container is still running normally. | PENDT1 PENDT2 | F | As for code CACHT1. | PUTR01 | AU | Error on writing to file. Possible reason: Disk storage bottleneck. | PWRT03 | AMU | Memory bottleneck.
Action: Check memory requirements and operating system generation. | PWRT06 | F | As for code CACHT1. | RESTRT | D | The diagnostic dump is taken with a restart of the BeanConnect proxy container after an abnormal termination. | SACT28 | M | Memory bottleneck.
Action: Modify the value for OSI-SCRATCH-AREA in the proxy container and update the configuration files of the proxy container. Otherwise inform system service. For details see National language support for message output in chapter "Encoding and national language support". | SHM002 | A | The shared memory key is not unique on the host. This may be an inherited error from K078 OSS 03.
Action: Check the proxy container generation.The used shared memory keys are written to the <Proxy_home>/def/input.system.txt file.
Parameter: MAX *SHMKEY. The shared memory keys depend on the generated port number. If necessary, you must generate the proxy container with another port number. | SLOG09 | SU | Problem when writing the message buffer to the current SYSLOG file.
Action: The DMS error code in the preceding K043 message may explain the cause of the error. Otherwise inform system service. | SLOG10 | SU | An attempt by a continuation work process to switch over to the current SYSLOG file generation has failed.
Action: It may be necessary to take into account any preceding K043 messages. Otherwise inform system service. | SMSG03 | ASU | Problem when writing the message buffer to the current SYSLOG file.
Action: The DMS error code in the preceding K043 message may explain the cause of the error. Otherwise inform system service. | STnnnn | ADSU | Error when processing the start of a process of a proxy container, where nnnn is the number indicating the error cause in the message "K049 Error nnnn during application startup".
Processes of the BeanConnect proxy container that are still active continue running. | WAITT1 WAITT2 | F | As for code CACHT1. | XATT02 | F | As for code CACHT1. | XFGE01 | F | As for code CACHT1. |
|
K065 | Net message: &PTRM/&PRNM/&BCAP/<RM &FIL1B &FIL2B Action: Depends on the values FIL1B and FIL2B. The inserts &FIL1B and &FIL2B have the following meaning: FIL1B | Meaning | X' F0' - X' FF' | Normal behavior. | other | See actions for FIL2B. |
FIL2B | Meaning | Actions | 00000008 | Invalid parameter. | Inform system service. | 00000014 | Connection letter too long. | Inform system service. |
FIL2B | Meaning | Actions | 00000030 | Internal error. | Inform system service. | 0400001C | Resource bottleneck. | Inform system service. | 04000020 | BeanConnect proxy container not signed on. | Inform system service. | 30000020 | Error signing on. | Inform system service. | other | Connection-specific events. | Normal behavior. |
|
K075 | Program exchange aborted by the task &PID; &CTYP &PROG &PVER Action: Inform system service. |
K078 | ffffffff yyyyyyyyy Meaning of the parameters: ffffffff | Contains a short code for the error that has occurred (see table below). | yyyyyyyyy | Specific, context-related error message. |
If an error code ffffffff occurs that is not described in the list below, inform system service. ffffffff | Reason | Actions | ALME | Memory bottleneck on application start. | Check memory requirement, tune operating system. | ATEXIT 00 - 04 | Process termination. | Information message. | DIAG 01 - 07 | Information about the process environment. | Information message. | ENV 00 - 04 | Information about the process environment. | Information message. | IPC 02 | Memory bottleneck when creating the IPC shared memory. | Tune system kernel parameter. | IPC 03 - 07 | Information about the dimension of the IPC shared memory. | Information message. | MEM 01 | Memory bottleneck when starting the application. Full text:
K078 MEM 01 in utmwork nn Bytes not available. | Check storage requirements; tune operating system. | MSG 01 - 02 | Information about the process environment. | Information message. | NET 01 | Information about the process environment. | Information message. | OSS 03 | Error while loading the OSS shared memories into the address space. | Check storage requirements; tune operating system. | PIPE 01 | Information about the process environment. | Information message. | SEM 01 | Error while creating a semaphore. A semaphore is not unique on the host. | Check the proxy container generation. The semaphore keys depend on the generated port number.
The used semaphore keys are written to the file <Proxy_home>/ (MAX SEMARRAY).
Change the first value in the brackets or you must generate the proxy container with another port number. | SIGNAL nn | Signal handling in utmwork process. | Information message. | SYSPROT 01 - 02 | Information about the process environment. | Information message | |
K104 | UTM-D TIMEOUT (&RCVDANNO): &LSES, &LPAP, &AGUS; old state: ( &OCVST, &OTAST ); action: &ACTION; new state: ( &NCVST, &NTAST ). Reason: Timeout during communication between the proxy container and the EIS partner. Action: Depends on the value of RCVDANNO. ACTION | Meaning | ASYNCH | Timeout during asynchronous communication: Either the association occupancy timer or the reply timer has expired. | STPROG | Timeout during outbound dialog communication without any impact on the transaction. | COMMIT RESET | Timeout during outbound/inbound communication: The transaction is either committed (COMMIT) or rolled back (RESET). |
RCVDANNO (Bytes 1-2) | Meaning | X'F331 | A timer has expired during inbound communication after the sending of a response to the EIS.
Action: Use the Management Console to increase the value of Transaction Communication Timer in the Timer Settings tab of the Edit Properties of Proxy property sheet. | X'F332' | A timer has expired during outbound communication after all the EIS partners involved in the distributed transaction have been requested to initiate termination of the transaction.
Action: Use the Management Console to check and, if necessary, increase the value for Reply Timer in the Edit Properties of an Outbound Service property sheet for all the outbound services involved in the transaction. | X'F333' | The ready timer has expired during inbound communication via OSI-TP.
Action: Use the Management Console to increase the value of Prepare to Commit Timer in the Timer Settings tab of the Edit Properties of Proxy property sheet. | X'F400' | The OSI-TP association occupancy timer for a dialog job has expired during outbound communication. | X'F520' | The OSI-TP association occupancy timer for an asynchronous job (internal timer of 60 seconds) has expired during outbound communication. | X'F522' | The timer which monitors reception of acknowledgment of an asynchronous message sent via an OSI-TP association during outbound communication has expired. | X'F534' | The response timer has expired during outbound communication for a dialog job.
Action: Use the Management Console to increase the value for Reply Timer in the outbound service's Edit Properties of an Outbound Service property sheet. |
|
K118 | Global transaction ID (length, data): (<HGTRID, >RID) atomic acion ID (length, data): (&AAIS, &AAID) This message will be outputted if a global OSI TP transaction will be rolled back. For Outbound communication the message contains the global part (GTRID) of the transaction id (XID) of the application server and the atomic action identifier (AAID) of the global OSI TP transaction, which will be used as global part of the transaction id of the utm application if the EIS partner has type UTM. |
K119 | OSI-TP error information: &OSLPAP, &USER, &TAC, &DIA1, &DIA2, &DIA3 The inserts &DIA1, &DIA2, &DIA3 contain the reasons for outputting message K119. Reason with openUTM: The dialog with the EIS partner was terminated. Reason with CICS: The dialog with the proxy component openUTM-LU62 Gateway was terminated. Action: See the table below. &DIA1 | &DIA2 | &DIA3 | Meaning | 01 | 06 | 02 | No free connection available.
Action: Increase the number of connections in the General tab of the Edit Properties of an EIS Partner property sheet in the Management Console. | 02 | 02 | 01 | Outbound communication: The outbound service is not known in the EIS.
Action: Harmonize the partner service name specified in the outbound service with the service name generated in the EIS. | 02 | 03 | 18 | Outbound communication: The EIS partner has rejected authentication with the specified security credentials.
Action: Check the configuration or programming. | 02 | 03 | 19 | Outbound communication: The EIS partner has rejected the OSI-TP dialog because the partner LPAP which represents the proxy container in the EIS partner is locked or is in QUIET state. | 02 | 03 | 21 | Outbound communication: Memory bottleneck at the EIS partner. | 02 | 03 | 22 | Outbound communication: The outbound service is not known in the EIS partner or is locked or there is no authorization.
Possible action: Harmonize the partner service name specified in the outbound service with the service name generated in the EIS. | 02 | 03 | 23 | Outbound communication: The outbound service is known in the EIS partner but cannot be called. | 02 | 03 | 24 | Outbound communication: The queue level for the asynchronous outbound service has been reached at the EIS partner. | 02 | 03 | 25 | Outbound communication: The dialog-based outbound service is configured as an asynchronous service in the EIS partner. | 03 | 03 | 18 | Inbound communication: The user employed by the EIS partner for the dialog is not configured in the proxy container or the employed password is false.
Action: Check the configuration. | 03 | 03 | 21 | Inbound communication: The proxy container storage area (page pool) is full.
Action: In the Management Console, increase the value of Pagepool in the Performance Settings tab in Proxy Container Storage Area Size in the Edit Properties of Proxy property sheet i | 04 | 02 | 00 01 | The EIS partner has terminated the dialog.
Action: See the messages in the EIS partner. | 09 09 | 03 03 | 21 31 | The proxy container storage area (page pool) is full.
Action: In the Management Console, increase the value of Pagepool in Proxy Container Storage Area Size in the Performance Settings tab of the Edit Properties of Proxy property sheet | 10 | 11 12 13 15 16 | xx xx xx xx xx | No free connection available
Action: In the Management Console, increase the number of connections (Connections) in the General tab of the Edit Properties of an EIS Partner property sheet. | 10 | 17 | xx | An inbound dialog process is active for every connection to the EIS partner and another inbound process is received on a connection that was closed and newly generated during this time.
Action: Increase the reply timer in the Edit Properties of an Outbound Service property sheet in the Management Console. The specified value must be greater than the reply timer in the EIS partner | other values | Inform system service. |
|
K124 | Error: &RCXAPTP at startup of XAP-TP occurred in phase: &PHAXAPTP Action: For RCXAPTP = 106: Possible cause: Work process could not be started because proxy is already shut down Otherwise: Inform system service. |
K128 | UTM-D job rejected: &CON/&PRNM/&BCAP/&LPAP &LSES &REA1 &RCDC &TAC Meaning of the inserts with openUTM: Insert | Meaning | &CON | OSI-CON name | &PRNM | Eight blanks | &BCAP | ACCESS-POINT name | <RM | OSI-LPAP name |
The insert &REA1 contains the reason that message K128 was output. &REA1 | Meaning | Action | X' 01' | Invalid service name called by an EIS using an OSI-TP connection. | If &RCDC=KM01:
Configure an inbound message endpoint and assign this service name to the inbound message endpoint or change the OSI-TP client.
Otherwise inform the system service. | X' 02' | Service name is generated with an error.
- Recipient tpsu title in TP-BEGIN-DIALOGUE-RI | Inform system service. | X' 03' | An asynchronous service is to be started, the service which is assigned to the message endpoint is configured as a dialog-orientated service.
- Receipt of a TP-END-DIALOGUE-RI protocol element | Check whether the OLTP message-driven bean implements the asynchronous interface and maybe enter the inbound message endpoint with the asynchronous service again.
Or change the OSI-TP client. | X' 04' | A dialog-orientated service is to be started, the service which is assigned to the message endpoint is configured as an asynchronous service. | Check whether the OLTP message-driven bean implements the dialog-orientated interface and maybe enter the inbound message endpoint with the dialog-orientated service again.
Or change the OSI-TP client. | X' 05' | An asynchronous service is to be started, but the message queue of the service has reached the generated threshold.
- The connection is cleared down. | Inform system service. |
|
K135 | UPIC message: &PTRM/&PRNM/&BCAP/<RM/&UPCREAS/&UPCSTAT/&UPCPROT/&UPVENC1/&UPPENC2 Action if UPCREAS = 0D:
Increase the proxy container storage area size in the Performance Settings tab of the Edit Properties of Proxy property sheet in the Management Console. Action if UPCREAS ≠0D: Inform system service. |
K139 | Switching SYSLOG failed! Still using file &FNAM Action: It may be possible to ascertain the reason for the error that occurred on switchover from the DMS error code in the preceding message K043. Otherwise inform system service. |
K147 | Sign on for &USRTYPE user &USER not successful &PTRm/&PRNM/&BCAP/<RM Reason: &REA7 Reason: Depends on the &USER value. &USER | Reason | BCURAxxx | Outbound communication in a cluster configuration or in multiple resource adapter mode.
If REA7=U3: Normal behavior
Otherwise: Problems during communication between the resource adapter and the proxy container | BCUxxxxx | Outbound communication: Problems during communication between the resource adapter and the proxy container. | BCADMIN | Administration: Problems communicating with the proxy container in the Management Console. | other | Inbound communication: Problems during communication between the EIS partner and the proxy container. |
Action: Depends on the &REA7 value. &REA7 | Meaning | U1 | Inbound: The USER that is used for the dialog by the EIS partner is not configured in the proxy container. See Configuring inbound communication .
Outbound: Internal error. Inform system service. | U3 | Inbound: You have tried to start more than one parallel dialog with the same user and without commit functionality.
Outbound: Internal error. Inform system service. | U4 | Inbound: The password used for the dialog by the EIS partner is not configured in the proxy container. See Configuring inbound communication .
Outbound: Internal error. Inform system service.
Administration: An incorrect password is specified in the Management Console for access to the proxy container. | U17 | The administrator has started termination of the proxy container. It is therefore not possible to start the dialog. | other | Inform system service. |
|
K152 | Heuristic report: &COND &MTYPE &OLPAP &USER <AC &AAIS &AAID Action: Depends on the &COND value. &COND | Meaning | MIX | Inbound: The application server and the EIS partner are not synchronized with respect to transaction security.
Possible database inconsistency. To coordinate this, manual contact to one of the involved databases is required.
Outbound: The EIS partner has detected a heuristic MIX. | HAZ | The application server has rolled back the transaction. The termination of this transaction (commit/rollback) is unknown in the EIS partner.
Possible database inconsistency. To coordinate this, manual contact to one of the involved databases is required. |
|
K160 | The &TACNTR. transaction of the &TCVG service was reset by &RBCAUSER (&RCCC/&RCDC); (pid: &TASK). If &TCVG = KDCGIOPU, there is an outbound communication process. For inbound communication &TCVG contains the service name that is assigned to the message endpoint in the Management Console. Action with openUTM: Normal behavior, see the process in the resource adapter or EIS partner. Action with CICS: Normal behavior, see the process in the resource adapter or proxy component openUTM-LU62 Gateway. |
K204 | XA (&TNSPID) Precommit requires global rollback; cause: &XATXT TA= &INTTAID Action: Inform system service if the value of the insert &XATXT is not equal to one of the following values. &XATXT | Meaning | XA_RBROLLBACK | Rollback for unspecified reason | XA_RBCOMMFAIL | Rollback due to an internal communication error in the Resource Manager | XA_RBDEADLOCK | Rollback due to a deadlock | XA_RBINTEGRITY | Rollback due to a resource inconsistency | XA_RBOTHER | Rollback for unspecified reason | XA_RBPROTO | Rollback due to an internal protocol error in the Resource Manager | XA_RBTIMEOUT | Rollback due to transaction period timeout | XA_RBTRANSIENT | Rollback due to a temporary error |
|
K210 | XA (&TNSPID) Return code: &XATXT Open RM &TEXT32, &INSTNUM Action: Inform system service. |
K211 | XA (&TNSPID) Return code: &XATXT Close RM &TEXT32, &INSTNUM Action: Inform system service. |
K212 | XA (&TNSPID) xa_start( &XAFLAG) - Return code &XATXT TA= &INTTAID Action: Inform system service. |
K213 | XA (&TNSPID) xa_end( &XAFLAG) - Return code &XATXT TA= &INTTAID Action: Inform system service. |
K214 | XA (&TNSPID) xa_commit() - Return code &XATXT TA= &INTTAID Cause: Normal behavior if no abnormal termination of the proxy container follows. Action: Inform system service on abnormal termination. |
K215 | XA (&TNSPID) xa_rollback() - Return code &XATXT TA= &INTTAID Cause: Normal behaviou if no abnormal termination of the proxy container follows. Action: Inform system service on abnormal termination. |
K216 | XA (&TNSPID) Return code &XATXT, recover PTC list, RM: &TEXT32,&INSTNUM Cause: Normal behavior if no abnormal termination of the proxy container follows. Action: Abnormal termination during the start-up phase may be caused by a faulty connection to the resource adapter (e.g. incorrect port number or invalid protocol between the proxy container and the resource adapter). The cause is described in more detail in the messages in the log files utmp.err.* and utmp.out.* as well as in the proxy container's logging file. If an incorrect port number has been assigned to the resource adapter then this can be set correctly using the Management Console. It is possible to restart the proxy container. If the BeanConnect proxy container and the resource adapter have different versions, the resource adapter clears the connection and the proxy container is therefore terminated while still in the start-up phase. The comment on the incorrect version designation is logged in resource adapter logging. If the cause of abnormal termination during the start-up phase cannot be identified as described above, please inform the system service.
|
K217 | XA (&TNSPID) xa_prepare() - Return code &XATXT TA= &INTTAID Cause: Normal behavior if no abnormal termination of the proxy container follows. Action: Inform system service on abnormal termination. |
K218 | XA (&TNSPID) xa_forget() - Return code &XATXT TA= &INTTAID Cause: Normal behavior if no abnormal termination of the proxy container follows. Action: Inform system service on abnormal termination. |
K220 | XA (&TNSPID) Error: xa_switch definition not found for specified RM: &TEXT32 Action: Inform system service. |
K221 | XA (&TNSPID) Error: Start parameters not found for defined RM: &TEXT32 Action: Inform system service. |
K222 | XA (&TNSPID) Error: Linked RM is not &XASPEC compatible &TEXT32 Action: Inform system service. |
K223 | XA (&TNSPID) Syntax error in start parameters Action: Inform system service. |
K224 | XA (&TNSPID) &XACALL - return code &XASTAT from RM instance &INSTNUM, &TEXT32 is not XA(CAE) compliant Action: Inform system service. |
K225 | XA (&TNSPID) recursive call: &XADBC1 - Error/signal in DB/XA connection for &XADBC2 Action: Inform system service. |
K230 | XA (&TNSPID) Int. error: &TEXT32 Action: Inform system service. |
K231 | XA (&TNSPID) Int. error: PETA not supported Action: Inform system service. |
K232 | XA (&TNSPID) Int. error: DBSTAT secondary opcode inconsistent Action: Inform system service. |
