List of messages

Messages output by TP1/Client are described in message number order.

KFCA02401-E (R)

environment definition error, variable=aa...aa, reason=bb...bb

There is a specification error in the client environment definition.

aa...aa: Name of the incorrect operand in the client environment definition

bb...bb

Reason

NO VALUE: No value is specified.

OUT OF RANGE: The specified value is out of range.

INVALID CHAR: The specified value includes an invalid character.

NET ENVIRONMENT: The specified value is inconsistent with the network environment.

UNMATCH LENG: The number of digits in the specified value is invalid.

S: Stops processing, or continues processing by using defaults.

O: Contact the TP1/Client system administrator.

Countermeasure:: Correct the definition error.

KFCA02402-E (R+E)

memory shortage, size=aa...aa, inf=bb...bb

Memory with the number of bytes shown at "size" cannot be allocated.

aa...aa: Number of bytes that should have been allocated

bb...bb: Maintenance information

S: Stops processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Re-estimate the memory requirement. When memory is sufficient, collect the error log and traces, and contact maintenance personnel.

KFCA02403-E (R)

aa...aa version error, TP1/Client(bb...bb):object(cc...cc)

Processing is impossible because the version of aa...aa OpenTP1 program is inconsistent with that of TP1/Client library linked to CUP.

aa...aa

Program whose version is inconsistent

NAM: NAM of TP1/Server Base

bb...bb: Version of TP1/Client library linked to CUP

cc...cc: Version of OpenTP1 program

S: Stops processing.

O: Contact the TP1/Client system administrator.

Countermeasure:

For bb...bb < cc...cc
Relink CUP.
For bb...bb > cc...cc
Check if TP1/Client is installed correctly.

KFCA02404-E (R)

parameter error, func=aa...aa, item=bb...bb

The function cannot be executed because of an argument specification error.

aa...aa: Name of the function in which the error occurred (If the _s version of the function was executed, the corresponding non-_s version function name might be output.)

bb...bb: Argument with an error

S: Returns the requested function as an error.

O: Contact the TP1/Client system administrator.

Countermeasure:: Correct the argument error.

KFCA02406-E (R)

error occurred in TP1/Client, reason=aa...aa, inf=bb...bb

An error occurred during internal processing of TP1/Client.

aa...aa

Reason for the error

MEMORY: Insufficient memory

RESOURCE: Resource shortage

NETWORK: Network failure

UNEXPECT: Unexpected error

NO SUCH SERVICE: An illegal request code for the server

TIMER: Unsuccessful timer setting

bb...bb: Maintenance information

S: The system stops processing.

O: Record the error log to which this message was output, and then contact the TP1/Client system administrator.

Countermeasure:: Examine and remove the cause of the error according to the output error log. Note that reason=UNEXPECT is also output when you specify a port number of the schedule service for an operand for which you must specify a port number of the name service. In this case, check the port number.

KFCA02407-E (R+E)

error occurred in TP1/Client, reason=aa...aa

An error occurred in TP1/Client.

aa...aa

Reason for the error

One of the following is displayed.

cltin not executed: dc_clt_cltin function has not been issued.

cltin already executed: dc_clt_cltin function has already been issued.

host name: Host name specification is incorrect.

TP1/Server not up: OpenTP1 is inactive at the target node.

S: Stops processing.

O: Check the error log to which this message was output, and examine and remove the cause of the error. Then restart CUP.

KFCA02410-E (R)

TP1/Server replied error, code=aa...aa, IPaddr=bbbbbbbb, port=cc...cc, inf=dd...dd

An error reply was received from TP1/Server Base.

aa...aa: Error code returned from TP1/Server Base

bbbbbbbb: Sender IP address (hexadecimal number)

cc...cc: Sender port number

dd...dd: Maintenance information

S: Performs one of the following actions:

Ends the processing that is being executed.
Ignores the error reply and waits for a reply message. If no reply message arrives after the maximum response wait time in the client environment definition expires, the system returns an error with DCRPCER_TIMED_OUT.
Switches the TP1/Server that is used as a gateway and continues processing, when Y is specified for DCHOSTCHANGE in the client environment definition.

O: Hand in the error log for this message to the TP1/Client system administrator.

Countermeasure:: Determine the sender process from the sender IP address and the sender port number. Check whether an error has occurred in TP1/Server.

KFCA02411-E (R)

invalid message received, IPaddr=aaaaaaaa, port=bb...bb, inf=cc...cc

A message that cannot be analyzed was received.

aaaaaaaa: Sender IP address (hexadecimal number)

bb...bb: Sender port number

cc...cc: Maintenance information

S: Ignores the received message and waits for the next message.

O: Contact the TP1/Client system administrator.

Countermeasure:: Determine the sender process from the sender IP address and port number, and check the network environment. This message also appears when a function receives a response message that the previous OpenTP1 function could not receive due to a timeout. In this case, ignore the message.

KFCA02412-W (R)

error-reply received, code=aa...aa, IPaddr=bb...bb, port=cc...cc, inf=dd...dd

An error response was received from TP1/Server.

aa...aa: Error code returned by TP1/Server

bb...bb: IP address of the sending source (in decimal dot notation)

cc...cc: Port number of the sending source

dd...dd: Maintenance information

S: Performs one of the following actions:

Ends the processing that is being executed.
Updates the cache information and retries communication.
Switches the TP1/Server that is used as a gateway and continues processing, when Y is specified for DCHOSTCHANGE in the client environment definition.

O: Record the error log containing this message and contact the TP1/Client system administrator.

Countermeasure:: Determine the sender process from the sender IP address and the sender port number. Check whether an error has occurred in TP1/Server.

KFCA02419-W (R)

error occurred in data compression process, group=aa...aa, service=bb...bb, reason=cc...cc

An error occurred during internal processing of data compression.

aa...aa: Name of the service group that is requested to perform service

bb...bb: Name of the requested service

cc...cc

Cause of the error

VERSION: Version mismatch

MEMORY: Insufficient memory

NOEFFECT: The data compression is ineffective.

UNEXPECT: Unexpected error

S: Requests the service without compressing the data.

O: If the cause of the error is version mismatch, check the version of TP1/Server Base that is requested to perform service and see if it can perform data compression (version 03-03 or later).: If the cause is insufficient memory, follow the instruction in the message that is output before this message.; If the cause is ineffective data compression, check if this message has been output elsewhere in the same CUP since the data becomes larger after compression. Then re-determine whether to use the data compression for each CUP.; If the cause is an unexpected error, contact the TP1/Client system administrator.

Countermeasure:: Examine the cause of the error. If necessary, contact maintenance personnel.

KFCA02420-E (R)

protocol error, IPaddr=aaaaaaaa, port=bb...bb, reason=cc...cc

Incorrect information was detected in the header of the TACT/KERNEL inter-process communication protocol.

aaaaaaaa: Sender IP address (hexadecimal number)

bb...bb: Sender port number

cc...cc

Reason

SIZE OVER: A message more than 12 bytes was received as the TACT header.

SIZE SHORT: A message less than 12 bytes was received as the TACT header.

INF2 ERROR: The contents of additional information 2 are incorrect.

S: Closes the connection and waits for the other system to re-establish a connection. Alternatively, cancels the processing that is being executed and returns the function with an error.

O: Contact the TP1/Client system administrator.

Countermeasure:

When this message is output, the following causes are likely:

An invalid message was received.
When cc....cc is SIZE SHORT, a FIN packet or a RESET packet was received.
When cc....cc is SIZE SHORT, a TACT header is divided when it was sent to the TCP buffer.

Determine the sender process from the sender IP address and port number, and check the network environment.

KFCA02421-E (R)

invalid size, received size=aa...aa, size in head=bb...bb, IPaddr=cccccccc, port=dd...dd

Processing is canceled because the length of the data that reports completion of reception is less than the data length in the header of the TACT/KERNEL inter-process communication protocol.

aa...aa: Received data length

bb...bb: Data length in the header

cccccccc: Sender IP address (hexadecimal number)

dd...dd: Sender port number

S: Cancels processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Determine the sender process from the sender IP address and the sender port number. Check whether an error has occurred in TP1/Server.

KFCA02431-E (R)

servicegroup list error, file=aa...aa:bb...bb, reason=cc...cc

The file specified with DCCLTSERVICEGROUPLIST in the client environment definition contains an error.

aa...aa: File specified with DCCLTSERVICEGROUPLIST in the client environment definition

bb...bb: Number of the line that contains an error

cc...cc: NO VALUE: No value is specified.; OUT OF RANGE: The value is out of the specifiable range.; INVALID CHAR: The value contains a character that cannot be specified.

S: Ignores the faulty line, and continues processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Correct the faulty line.

KFCA02444-E (R)

communication error, func=aa...aa, errno=bb...bb

A communication error occurred.

aa...aa: Socket interface function with an error

bb...bb: Error number

S: Stops processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Examine the cause of the error referring to the function name and error number.

KFCA02445-E (R)

host resolution failed, func=aa...aa, errno=bb...bb, data=cc...cc

Host resolution failed.

aa...aa: Name of a socket interface function in which an error occurred; Either gethostbyname or gethostbyaddr is output here.

bb...bb: Error number

cc...cc: Host name or IP address from which the host could not be resolved (in decimal dot notation)

S: The function either stops processing and returns an error, or ignores the error and continues processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Make sure that the specified host name or IP address is correct. If DNS is used for host name resolution, check whether there is an error on the network connected to the DNS server or on the DNS server itself.

KFCA02446-E (R)

communication error occurred while aa...aa function was being executed, func=bb...bb, errno=cc...cc, c-info=dd...dd:ee...ee, s-info=ff...ff:gg...gg

A communication error occurred.

aa...aa: Name of the executed function

bb...bb: Name of the socket interface function for which the error occurred

cc...cc: Error number

dd...dd: Local IP address (in decimal dot notation)

ee...ee: Local port

ff...ff: Remote IP address (in decimal dot notation)

gg...gg: Remote port

S: Cancels processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Determine the cause of the error from the information in this message and the applicable data on the server.

KFCA02447-E (R)

timeout occurred while aa...aa function was being executed, sts=bb...bb, time=cc...cc, c-info=dd...dd:ee...ee, s-info=ff...ff:gg...gg

A timeout occurred.

aa...aa: Name of the executed function

bb...bb: Wait status of the function before the timeout occurred:; CONNECT: The function was waiting for a response for connection establishment.; ACCEPT: The function was waiting for a connection establishment request.; RECV(T): The function was waiting for the TACT header to be received.; RECV(D): The function was waiting for data to be received.; RECV(D2): The function was waiting for data to be received.; RECV(D3): The function was waiting for data to be received.; RECV(M): The function was waiting for message information to be received.; RECV(R): The function was waiting for response-only data to be received.; RECVFROM: The function was waiting for broadcast data to be received.

cc...cc: Timeout value specified in the client environment definition or as an argument of the function (seconds)

dd...dd: Local IP address (in decimal dot notation)

ee...ee: Local port

ff...ff: Remote IP address (in decimal dot notation)

gg...gg: Remote port

S: Cancels processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Check whether the specified timeout value is appropriate. If the value is appropriate, server processing might have been delayed for a reason such as a line failure. Determine the cause of the error from the information in this message and the applicable data on the server.

KFCA02449-E (R)

communication error, func=aa...aa, errno=bb...bb, remote node addr=cc...cc, remote port=dd...dd

A communication error occurred.

aa...aa: Function name of the socket interface that caused the error.

bb...bb: Error number

cc...cc: Send destination IP address

dd...dd: Send destination port number

S: Stops processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Examine the cause of the error referring to the function name and error number.

KFCA02450-W (R)

The client-ID of a different thread has been specified. func=aa...aa, thread1=bb...bb, thread2=cc...cc

The client-ID of a different thread has been specified.
This message is output only once after execution of the dc_clt_cltin_s function.

aa...aa: Name of the client function

bb...bb: ID of the thread that started the client function

cc...cc: ID of the thread that acquired the client ID

S: Continues processing.

O: Record the error log containing this message and contact the TP1/Client system administrator.

Countermeasure:: The same client ID is used across threads. Correct the CUP to ensure that client IDs are specified correctly when functions are executed.

KFCA02451-W (R)

The function was executed twice.
func1=aa...aa, thread1=bb...bb, func2=cc...cc, thread2=dd...dd

A duplicate client functions was executed.
This message is output only once after execution of the dc_clt_cltin_s function.

aa...aa: Name of the client function for which duplication was detected

bb...bb: ID of the thread that started the function for which duplication was detected

cc...cc: Name of the client function already being executed

dd...dd: ID of the thread that started the function already being executed

S: Continues processing.

O: Record the error log containing this message and contact the TP1/Client system administrator.

Countermeasure:: The error occurred because client functions with the same client ID were executed concurrently. Correct the CUP to ensure that duplicate functions are not executed.

KFCA02460-I (E+S)

usage: aaaaaaa [bb pathname]

This message shows the format of the trace edit and output command. This message appears if the specification of the trace edit and output command is incorrect.

aaaaaaa: UAP trace edit and output command

bb: Option

TP1/Client/W: usage: cltdump [-u|-s|-m] [-n] [-f pathname]

TP1/Client/P: usage: cltdmp32 [/u|/s|/m] [/n] [/f pathname]

S: Stops processing.

O: Reenter the command in the correct format.

KFCA02461-E (E)

file(aa...aa)not found

The specified file was not found upon input of the trace edit and output command.

aa...aa: File name specified by the user

S: Stops processing.

O: Correct the file name and then reenter the trace edit and output command.

KFCA02462-E (E)

no file to edit: aa...aa

There is no trace file to edit and output.

aa...aa: Type of trace file to edit and output.; UAP: UAP trace; SOC: Socket trace; MDL: Module trace

S: Stops processing.

O: If the CUP run-time trace file has not been created, the client environment definition may have an error. Review the specification according to the string indicated in aa...aa:: If UAP is output, see the DCTRCUAP specification.; If SOC is output, see the DCTRCSOC specification.; If MDL is output, see the DCTRCMDL specification.; If TP1/Client/W is used, see the DCTRCPATH specification.; If the specification is incorrect, correct the error, and then re-execute the CUP.

KFCA02463-E (E)

error occurred, file=aa...aa

An error occurred while executing the trace edit and output command.

aa...aa: File with an error

S: Stops processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Examine the cause of the error. If necessary, contact maintenance personnel.

KFCA02466-I (R)

TP1/Server Base ready, hostname=aa...aa, port=bb...bb

The TP1/Server (host that the name service queries) to be used as a gateway is determined. Note that the gateway TP1/Server may change depending on the contents of the error.

aa...aa: Host name of the TP1/Server that is used as a gateway

bb...bb: Port number of the TP1/Server that is used as a gateway (port number of the name service)

KFCA02468-I (R)

TP1/Client changed connected TP1/Server Base, hostname=aa...aa, port=bb...bb

Because an error occurred during communication with the TP1/Server (host that the name service queries) used as a gateway, the gateway TP1/Server was changed.

aa...aa: Host name of the TP1/Server used as a gateway after switchover

bb...bb: Port number of the TP1/Server that is used as a gateway (port number of the name service) after switchover

KFCA02470-E (R)

the error commitment for transaction(aaaaaaaabbbbbbbb) occurred, return value=cc...cc

An attempt was made to execute the dc_rpc_close_s, dc_clt_cltout_s function without commit or rollback in unchained mode. TP1/Client then automatically performed commit in unchained mode and caused an error in synchronous point processing.

aaaaaaaa: OpenTP1 system node ID (eight letters)

bbbbbbbb: Global transaction number (eight hexadecimal characters)

cc...cc: Return value (4-digit positive number) for synchronous point processing

S: Continues processing.

O: Contact the TP1/Client system administrator.

Countermeasure:

Take action against a synchronous point processing error.
After issuing a request for commit or rollback in unchained mode, terminate the CUP.

KFCA02471-W (R)

Current status is outside a transaction. trngid=aa...aa, trnbid=bb...bb

The current transaction status is out of range. The connection to the transaction executing process has already been released because of an error. Therefore, the dc_trn_unchained_commit_s or dc_trn_unchained_rollback_s function returned a DCCLTER_OLTF_NOT_UP error.

aa...aa: Transaction global identifier of the transaction where an error occurred

bb...bb: Transaction branch identifier of the transaction branch where an error occurred

S: The executed function returns a DCCLTER_OLTF_NOT_UP error. Currently, TP1/Client is placed outside a transaction.

O: Contact the TP1/Client system administrator.

Countermeasure:: Find the cause of the error from the message output before this one, and correct the error. If the error was due to a timeout, review the definition and settings so that a timeout does not occur at the client before the server.; To restart the transaction, execute the dc_trn_begin_s function. Note that the previous transaction indicated by trngid and trnbid remains active until the transaction inquiry interval expires.

KFCA02472-E (R)

The function has been issued from an invalid context. func=aa...aa

The function indicated by func was called from incorrect context.
The connection to the transaction executing process has already been released because of an error. Therefore, the function indicated by func returned a DCCLTER_OLTF_NOT_UP or DCRPCER_OLTF_NOT_UP error.

aa...aa: Function name

S: The executed function returns a DCCLTER_OLTF_NOT_UP or DCRPCER_OLTF_NOT_UP error. TP1/Client remains inside a transaction.

O: Contact the TP1/Client system administrator.

Countermeasure:: Find the cause of the error from the message output before this one, and correct the error. If the error was due to a timeout, review the definition and settings so that a timeout does not occur at the client before the server.; To restart the transaction, execute the dc_trn_unchained_commit_s or dc_trn_unchained_rollback_s function, and then the dc_trn_begin_s function.; We recommend that you write a program so that the dc_trn_unchained_commit_s or dc_trn_unchained_rollback_s function is executed if an error occurs during transaction processing.

KFCA02480-I (R)

The permanent connection was established. IPaddr=aa...aa, port=bb...bb

Permanent connection has been established. The connection is established with a CUP executing process, a RAP-processing listener, or a DCCM3 logical terminal.

aa...aa: IP address of the destination of the established permanent connection

bb...bb: Port number of the destination of the established permanent connection

KFCA02481-I (R)

The permanent connection was cut off. IPaddr=aa...aa, port=bb...bb

Permanent connection has been disconnected. The connection is established with a CUP executing process, a RAP-processing listener, or a DCCM3 logical terminal.

aa...aa: IP address of the destination of the established permanent connection

bb...bb: Port number of the destination of the established permanent connection

KFCA02482-E(R)

communication error, func=aa...aa, errno=bb...bb, port=cc...cc

A communication error occurred.

aa...aa: Function name of the socket interface that incurred the error

bb...bb: Error number

cc...cc: Number of the port being used

S: Terminates processing.

O: Contact the TP1/Client system administrator.

Countermeasure:: Reference an error number to examine the cause of the error.

KFCA02485-E (R)

invalid message received while aa...aa function was being executed. expected message=bb...bb, received message=cc...cc, c-info=dd...dd:ee...ee, s-info=ff...ff:gg...gg, action=hh...hh

While the message assembly facility or message delivery confirmation facility was being used, a message with an invalid value set was received.

aa...aa: Name of the executed function

bb...bb: Expected message (hexadecimal characters) (If there is no information to be output, **** is output.)

cc...cc: Received message (hexadecimal characters)

dd...dd: Local IP address (decimal dot notation)

ee...ee: Local port

ff...ff: Remote IP address (decimal dot notation)

gg...gg: Remote port

hh...hh

System action

RETRY:: The system continues processing, and retries receive processing.

STOP:: The system cancels processing. The function returns an error.

O: Contact the TP1/Client system administrator.

Countermeasure:

Depending on the hh...hh value, take action as follows.

RETRY:: The system has retried receive processing because the message ID of the received message was invalid. Accordingly, the function might have now terminated normally after receiving a valid message. If the function has not terminated normally, see the message output after this one.

STOP:: The system has canceled processing because the length or segment information of the received message was incorrect. Review the settings of the remote system. If messages collided (the dc_clt_assem_send_s function returned a DCCLTER_COLLISION_MESSAGE error), try again if necessary.

KFCA02486-E (R)

receive buffer overflowed. argument length=aa...aa, received length=bb...bb, received message=cc...cc, c-info=dd...dd:ee...ee, s-info=ff...ff:gg...gg

When the message assembly facility or message delivery confirmation facility was being used, a message could not be received because the buffer area prepared by the CUP was too small.

aa...aa: Value of the recvleng argument for the dc_clt_assem_receive_s function (decimal number)

bb...bb: Length of the message to be received (decimal number)

cc...cc: Received message information (hexadecimal characters)

dd...dd: Local IP address (decimal dot notation)

ee...ee: Local port

ff...ff: Remote IP address (decimal dot notation)

gg...gg: Remote port

S: Terminates processing. The dc_clt_assem_receive_s function returns a DCCLTER_INF_TOO_BIG error. The connection with the remote system is released.

O: Record the error log containing this message and contact the TP1/Client system administrator.

Countermeasure: The message length specified in the function argument is less than the message length set in the received message information. Check whether the value specified in the recvleng argument of the dc_clt_assem_receive_s function is appropriate. Alternatively, review the UAP on the remote system.

10.3 List of messages