Messages related to transfer processing and framed message analysis (1001 to 2000)

Transfer of the file ID (%s) started between the send service (%s) on the send host (%s) and the receive service (%s) on the receive host (%s). The ID assigned for each transfer is displayed in the transfer serial ID (%s).

--

Transfer of the file ID (%s) between the send service (%s) on the send host (%s) and the receive service (%s) on the receive host (%s) ended successfully. The ID assigned for each transfer is displayed in the transfer serial ID (%s).

--

Transfer of the file ID (%s) between the send service (%s) on the send host (%s) and the receive service (%s) on the receive host (%s) will be stopped. The ID assigned for each transfer is displayed in the transfer serial ID (%s).

Check the messages output before and after this message, remove the cause of the error, and retry the transfer.

Transfer of the file ID (%s) between the send service (%s) on the send host (%s) and the receive service (%s) on the receive host (%s) was interrupted by another host. The ID assigned for each transfer is displayed in the transfer serial ID (%s).

In the Transfer Status Watch window of HULFT-HUB Manager, identify the HULFT-HUB Server program in which an error occurred, check the trace logs, remove the cause of the error, and then retry the transfer.

A processing request was received from the communication destination that is not supported by HULFT-HUB Server.

Check your network environment.

HULFT-HUB Server could not connect to the connection-destination host name (%s) and connection-destination service name (%s). HULFT-HUB Server retries connection as many times as specified for the Connect Retry Count (SocketRetryMax) at the Connect Retry Interval (SocketRetryInterval). A multiplex level over or connection error might have occurred in the connection-destination host.

--

HULFT-HUB Server retried connection as many times as specified for the Connect Retry Count (SocketRetryMax) at the Connect Retry Interval (SocketRetryInterval), but could not connect to the connection destination host name (%s) and connection destination service name (%s). A multiplex level over or connection error might have occurred in the connection-destination host.

Check the trace logs of the connection-destination host, and remove the cause of the error. If the cause of the error is multiple level over in the connection-destination host, increase the values for the Connect Retry Interval (SocketRetryInterval) and Connect Retry Count (SocketRetryMax), or wait a while, and then retry the transfer.

An attempt to encrypt a framed message failed.

This is an internal problem of HULFT-HUB Server. Collect the error information, and contact the Support Center.

An attempt to decrypt a framed message failed.

This is an internal problem of HULFT-HUB Server. Collect the error information, and contact the Support Center.

An attempt to generate a framed message failed.

A possible cause is a restriction imposed by the operating system, such as shortage of system memory. Check the environment.

Relay of Request Acknowledge of the service type (%s) between the requestor service (%s) on the requestor host (%s) and the request destination service (%s) on the request destination host (%s) started. The ID assigned for each Request Acknowledge is displayed in the transfer serial ID (%s).

--

Relay of Request Acknowledge of the service type (%s) between the requestor service (%s) on the requestor host (%s) and the request destination service (%s) on the request destination host (%s) ended successfully. The ID assigned for each Request Acknowledge is displayed in the transfer serial ID (%s).

--

Request Acknowledge of the service type (%s) that was relayed between the requestor service (%s) on the requestor host (%s) and the request destination service (%s) on the request destination host (%s) will be stopped. The ID assigned for each Request Acknowledge is displayed in the transfer serial ID (%s).

Check the messages output before and after this message, remove the cause of the error, and retry the Request Acknowledge.

Request Acknowledge of the service type (%s) that was relayed between the requestor service (%s) on the requestor host (%s) and the request destination service (%s) on the request destination host (%s) was interrupted by another HULFT-HUB Server. The ID assigned for each Request Acknowledge is displayed in the transfer serial ID (%s).

Check the trace logs of the HULFT-HUB Server on the path, and remove the cause of the error. Identify the target HULFT-HUB Server based on the information of the requester host name (%s) and requester service name (%s).

The Send Request processing ended abnormally due to the setting of 'Handling of the Send Request when undelivered data does not exist'.

--

The relay of the request from HULFT-HUB Manager to the destination host name (%s) was acknowledged via the connection-source host name (%s) and connection-source service name (%s). In the transfer serial ID (%s), the ID assigned for each managed connection is displayed.

--

The relay of the request, from HULFT-HUB Manager to the destination host name (%s), which was received via the connection-source host name (%s) and connection-source service name (%s), ended. In the transfer serial ID (%s), the ID assigned for each managed connection is displayed.

--

The relay of the request, from HULFT-HUB Manager to the destination host name (%s), that was received via the connection-source host name (%s) and connection-source service name (%s), was interrupted. In the transfer serial ID (%s), the ID assigned for each managed connection is displayed.

Check the messages output before and after this message, remove the cause of the error, and log in from HULFT-HUB Manager again.

The relay of the request, from HULFT-HUB Manager to the destination host name (%s), which was received via the connection-source host name (%s) and connection-source service name (%s), was interrupted by another HULFT-HUB Server. In the transfer serial ID (%s), the ID assigned for each managed connection is displayed.

Check the trace logs of the HULFT-HUB Server on the path, and remove the cause of the error. Identify the target HULFT-HUB Server based on the information of the connection-source host name (%s) and connection-source service name (%s).

An attempt to generate a transfer processing thread failed.

A possible cause is a restriction imposed by the operating system, such as shortage of system memory. Remove the cause that is indicated by the reason.

HULFT-HUB Server disconnected the connection due to the access by a client (host name: %s, service name: %s) that is not a Registered Client.

Identify the requestor based on the host name and the service name, and register the requestor in the Registered Client Information if necessary. If it is an invalid requestor, contact the network administrator of your environment.

HULFT-HUB Server disconnected due to the access by HULFT-HUB Server that is not the Neighboring Server.

Identify the requestor based on the host name and the service name, and register the requestor in the Registered Client Information if necessary. If it is an invalid requestor, contact the network administrator of your environment.

The transfer cannot be performed because this server is an alternative server.

On the Management screen of HULFT-HUB Manager, check the Structure Diagram to see the server status.

HULFT-HUB does not support clients whose version is 4 or lower.

Upgrade the client on the sending side.

HULFT-HUB does not support clients whose version is 4 or lower.

Upgrade the client on the receiving side.

An attempt to generate a transfer serial ID failed.

Possible causes are an abnormality in the socket or a restriction imposed by the operating system. Check the environment.

HULFT-HUB Server disconnected the connection because the file transfer that is indicated by the transfer serial ID or the connection request of the Request Acknowledge was received several times.

Use the Transfer Status Watch Details screen of HULFT-HUB Manager or trace logs to check whether there is a definition that goes through this HULFT-HUB Server several times, and modify the routing information if necessary.

HULFT-HUB Server could not allocate enough memory for receiving framed messages. The memory size necessary for receiving framed messages is displayed in the framed message length (%d). The allocated memory size is displayed in the framed message buffer size (%d).

This problem might occur when the load on the system is temporarily high. Wait for a while, and then try again.

HULFT-HUB Server could not allocate enough memory for creating a framed message. The memory size necessary for creating a framed message is displayed in the framed message length (%d). The allocated memory size is displayed in the framed message buffer size (%d).

This problem might occur when the load on the system is temporarily high. Wait for a while, and then try again.

Inconsistency occurred in the management information of HULFT-HUB Server.

HULFT-HUB Server is in an unstable state. On the Transfer Information screen of HULFT-HUB Manager, re-register the Transfer definition.

HULFT-HUB Server will stop the transfer because the route to the receive host (%s) was not determined due to either of the following reasons:

1. The route to the receive host has not been registered in the Routing Management Information.

2. The Receive Port No. registered in the host information of a client on the sending side is different from the Receive Port No. registered in the registered client information.

Take either of the following measures to resolve the problem:

1. In the Management Screen of HULFT-HUB Manager, on the Route Settings tab of the relevant HULFT-HUB Server, register the route to the receive host.

2. The management information might have become inconsistent between HULFT-HUB Server and the client. Check the management information, and correct the Receive Port No. in the host information on the client on the sending side, or the host information on the client on the sending side that is managed by HULFT-HUB Server.

The send host name and the send service name for multicasting of the file ID is not registered in the Transfer Information.

On the Transfer Information screen of HULFT-HUB Manager, register the Transfer definition, and then retry the transfer request.

The Relay daemon acknowledged a transfer request, but the transfer type of the send host name (%s), send service name (%s), and file ID (%s) is not 'Relay'. An invalid transfer type is displayed in the transfer type (%d).

Use the Transfer Information Screen, the Collecting and Distributing System Management Information window, and Management Information Parameter Generation utility of HULFT-HUB Manager to check the transfer definition.

The Relay daemon (hubrlyd) acknowledged a transfer request for the send host name, the send service name, and the file ID, but the transfer destination cannot be determined.

On the Transfer Information screen of HULFT-HUB Manager, register the Transfer definition, and then retry the transfer request.

The transfer type (%s) specified in the Transfer Information is invalid.

Check your network environment.

Multicasting will stop due to one of the following reasons:

1. An error occurred in multicasting processing of this HULFT-HUB Server.

2. An error was reported from another HULFT-HUB Server or client.

3. Transfer from a client was cancelled.

This message is output when the When Multicasting is Unsuccessful (MulticastError) is set to 'Stop Immediately' in the Transfer Conditions or the System Environment Settings.

Check the messages output before and after this message, and remove the cause of the error. If you want to continue multicasting to other transfer destinations even when an error occurs, set the When Multicasting is Unsuccessful (MulticastError) to 'Continue' in the Transfer Conditions or the System Environment Settings. For details about how to specify the setting, see the description in the Relay/Multicasting Settings information or System Environment Settings of the server in the HULFT-HUB Manager online help.

An internal protocol error occurred.

This is an internal problem of HULFT-HUB Server. Collect the error information, and contact the Support Center.

A no-communications timeout occurred with the connection source host. For the timer value (%d), the value of one of the following is set depending on the connection type:

1. The Socket Timeout (SocketTimer) in the System Environment Settings of the local host

2. The Socket Timeout (SocketTimer) in the System Environment Settings of the connection source server

3. The Socket Timeout (or Socket Read Timeout) of the client on the sending side

For details about the connection type and the value to be set, see the description of the no-communications monitor in the HULFT-HUB Manual.

Check the value that is set for the timer value, and take one of the following measures to resolve the problem:

1. Change the value of the Socket Timeout (SocketTimer) in the System Environment Settings of the local host.

2. Change the value of the The Socket Timeout (SocketTimer) in the System Environment Settings of the connection source server.

3. Change the value of The Socket Timeout (or Socket Read Timeout) of the client on the sending side.

A no-communications timeout occurred with the connection destination host. For the timer value (%d), the value of one of the following is set depending on the connection type:

1. The Socket Timeout (SocketTimer) in the System Environment Settings of the local host

2. System Environment Settings Socket Timeout (SocketTimer) of the connection-destination server

3. The Socket Timeout (or Socket Read Timeout) of the client on the sending side

For details about the connection type and the value to be set, see the description of the no-communications monitor in the HULFT-HUB Manual.

Check the value that is set for the timer value, and take one of the following measures to resolve the problem:

1. Change the value of the Socket Timeout (SocketTimer) in the System Environment Settings of the local host.

2. Change the value of the Socket Timeout (SocketTimer) in the System Environment Settings of the connection destination server.

3. Change the value of the Socket Timeout (or the Socket Read Timeout) of the client on the sending side.

The Transfer Destination Host Information is invalid.

HULFT-HUB Server is in an unstable state. On the Transfer Information screen of HULFT-HUB Manager, re-register the Transfer definition.

HULFT-HUB Server will wait for subsequent information because the information read from the connection-source host was incomplete. The number of read bytes is displayed in the length (%d).

Check your network environment.

HULFT-HUB Server discarded the communication because a timeout occurred while the connection-source information was incomplete.

Check your network environment.

A function that cannot be used with the version of the communication target is specified.

Check whether the setting for the file ID, the format ID, or the multi format ID is 9 bytes or more.

HULFT-HUB Server interrupted multicasting because, under the setting where accumulation is not performed on the multicasting server, the Compression Preference cannot be changed for each host on the receiving side during transfer.

Change to either of the following settings:

• Accumulating on the multicasting server.

• Specifying a compression preference that can be used by all hosts on the receiving side.

Failed to execute the FIPS AES power-up self-test.

Check the error code.

Transfer Conditions are not defined for the transfer of Send host name (%s), Send service name: (%s), File ID: (%s), Receive host name (%s), and Receive service name(%s). The following items will be transferred by using the values in the System Environment Settings:

• Connect Retry Count

• Connect Retry Interval

• Socket Timeout

• When Multicasting is Unsuccessful (for Multicasting only)

• Criterion for Unsuccessful Multicasting (for Multicasting only)

--

HULFT-HUB Server used 'unknown' for the Business Group ID and performed transfer because the File ID (%s) was not registered in the Send Management Information of the Send host name (%s).

The management information might have become inconsistent between HULFT-HUB Server and the client. In the Management Screen of HULFT-HUB Manager, collect the Management Information for the Send Host Name (%s).

HULFT-HUB Server will use the protocol for version 8 because this HULFT-HUB Server program does not support HULFT whose version is 9 or higher.

--

The process was replaced because the transfer count of the daemon (%s) reached the maximum (%d).

--

A connection with the connection destination host or the connection source host that is indicated by the Host Name and the Service Name was disconnected.

Check whether HULFT-HUB Server or the client that is indicated by the Host Name and the Service Name is running. If it is running, check the messages that are output before and after this message, and the Transfer Log or the trace log of the host that is indicated by the Host Name and the Service Name.

HULFT-HUB Server canceled new transfer processing because the Relay/Multicasting/Deliver processing reached the value of the System Environment Settings Transfer Processing Multiplex Level (TransRlyMax).

If you want simultaneous transfer, change the value of the System Environment Settings Transfer Processing Multiplex Level (TransRlyMax).

An error notification or a cancellation notification was received from %s. For details about error codes, see "Detail Code" in the "Error Codes and Messages" of each client.

Check the Error Description of the client, and remove the cause of the error.

HULFT-HUB Server canceled new Request Acknowledge processing because the Request Acknowledge processing reached the value of the System Environment Settings Request Acknowledge Processing Multiplex Level (ReqRlyMax).

If you want simultaneous Request Acknowledge processing, change the value of the System Environment Settings Request Acknowledge Processing Multiplex Level (ReqRlyMax).

HULFT-HUB Server canceled a new Manager Relay processing because the Manager Relay processing reached the value of the System Environment Settings Manager Relay Multiplex Level (MgrRlyMax).

If you want simultaneous Manager Relay processing, change the value of the System Environment Settings Manager Relay Multiplex Level (MgrRlyMax).

In accordance with the delivery instruction, the Delivery Daemon started the Deliver processing.

--

The Delivery Daemon ended the Deliver processing successfully.

--

HULFT-HUB Server canceled the Deliver processing because an error occurred in the Deliver processing.

Remove the cause of the error, and then retry the delivery.

The Delivery Daemon received a Deliver Request.

--

HULFT-HUB Server will perform transfer by using a different method from the transfer mode set by HULFT. The change affects the transfer speed and the time until an error is detected. However, it does not affect the reliability of the transfer data.

If necessary, change to a transfer type in which change of the Framed Message Transfer Type does not occur.

For details about the framed message transfer type and transfer mode, see the HULFT-HUB Manual and the Administration Manual for the client.

HULFT-HUB Server cannot perform transfer correctly because the HUB client on the receiving side does not use the same data verification algorithm.

Set the same data verification algorithm, and then retry transfer.

HULFT-HUB Server was disconnected from a client after the connection request. This message might be displayed when the client detects inconsistency in the version with HUB Server.

Check the versions of HULFT-HUB supported by clients, and upgrade HULFT-HUB if necessary.

The server version that is held by the Neighboring Server is inconsistent with the actual version.

Use HULFT-HUB Manager to check the version information, and redraw the connection line if there is inconsistency.

This message is output when the accumulated data to be delivered from the HUB server cannot be sent because of the Waiting for Reinstatement of Client, Waiting to be Delivered, or Exceeded the Receive Process Multiplex Level status.

Check the reason why the delivery does not start. If necessary, send the leading accumulated data, or reinstate the client.

The file was transferred with DEFLATE compression or no compression, because the receiving host does not support the compression type specified on the sending host.

If you want to compress the transfer data, on the sending host specify a compression preference that can be used by the receiving host.

The file was transferred with DEFLATE compression or no compression, because the receiving host does not support the compression type specified on the sending host.

An error occurred during transfer processing.

Remove the cause of the error, and then retry the transfer.

An error occurred during the Delivery processing.

Remove the cause of the error, and then retry the delivery.

The relevant HUB Server could not acknowledge the transfer request.

Remove the cause of the error, and then retry the transfer.

An error occurred during the processing to check the management targets.

Remove the cause of the error, and then retry.

This is the encryption logic used for communication of the relevant session.

--

The processing could not be executed because the Cipher Option (%s) was not installed.

Remove the cause of the error, and then retry the transfer.

The value %c is returned because the type of Kanji Character Code cannot be identified even though 'Auto' is specified for 'EBCDIC Set' of transfer information.

Set a value for 'EBCDIC Set' or specify the receiving side for code conversion.

The connection to a host with a different Forced Strong Key mode from that of the client on the sending side was interrupted.

You cannot connect to a client for which the Forced Strong Key mode is different.

The encryption processing is not possible because the Forced Strong Key mode and the length of the cypher key in the management information do not match.

If the Forced Strong Key mode is enabled, set a cypher key of which the length is 64 bytes.

If the Forced Strong Key mode is disabled, set a cypher key of which the length is 0 bytes or from 8 to 20 bytes.

File transfer has been interrupted because there is an error in the settings for code conversion in the Send Management Information.

Save correct settings to the management information in accordance with messages appearing when you attempt to apply settings on the Transfer Information screen.