ADACM* - ADATCP Messages

One of the parameters passed within the URL was incorrect.

Ensure that the URL includes valid values for all required elements: the API name (protocol), stack ID, and port number. Correct the URL and try again.

The port that was specified in the URL was not valid.

The port number can be 1-5 bytes; it cannot be zero (0) or greater than 65535.

Either the URL is already opened (ACTIVE) or already closed (CLOSED).

Ensure that the URL includes valid values for all required elements: the API name (protocol), stack ID, and port number. Correct the URL and try again.

The URL itself was not found.

Ensure that the URL includes valid values for all required elements: the API name (protocol), stack ID, and port number. Correct the URL and try again.

Either the URL was successfully closed or opened.

None. This message is for information only.

ADATCP cannot be started because the network is not active.

Check that the stack specified in the URL is active. If it is, contact your systems administrator.

No buffer space is available to ADATCP to allocate its control blocks.

Ensure that sufficient storage is available on the system.

An error caused TCP/IP or ADATCP to terminate.

This message is issued along with another message that explains the reason for the termination. Refer to the other message.

The TCP/IP stack specified in the URL is not installed or not active.

Check that the specified URL is the one intended. If so, either install the specified stack or start it.

The maximum number of socket descriptors has been reached: no more sockets can be created.

Increase the maximum number of sockets that can be created.

Unless this message is accompanied by an error message, TCP/IP has terminated normally.

If an error message accompanies this message, refer to that message. Otherwise, this message is for information only.

The stack specified in the URL is not valid: TCP/IP cannot initialize.

Ensure that the stack is available on the system and that it is active.

The TCP/IP name specified in the URL is not valid.

Check that the URL contains the correct stack name. If so, ensure that the stack is available on the system and that it is active.

The TCP/IP stack specified in the URL cannot be initialized.

Ensure that the TCP/IP stack specified is correct and that it is active. If it is correct and active, contact the systems administrator.

ADATCP is unable to allocate the necessary storage.

Ensure that adequate storage is available on the system.

The operating system specified in the URL is incorrect.

The only operating systems currently supported are OES, HPS, and Computer Associates' Unicenter TCPaccess Communications Server (ILK).

The TCP/IP stack specified in either the URL or the protocol that was used is invalid.

Check that the URL or protocol contains the correct stack name. If so, ensure that the stack is available on the system and that it is active.

The system is unable to create a new socket. This may be caused by an incorrect stack. If an error number accompanies this message, it will inform you if the problem is inadequate system resources (ENOBUFS) or access denied (EACCES).

Ensure that the correct stack is being used. If the problem is inadequate system resources, contact your systems administrator. Contact your security administrator for system access problems.

ADATCP was unable to bind the socket to the local system. Another application may be using the port specified in the URL.

Use the TSO NETSTAT command to check current use of the specified port. If something else is using the port, terminate ADATCP and change the port in the URL.

ADATCP is unable to accept connections from client applications. This may indicate a shortage of buffer space or that the maximum number of socket descriptors have already been created/opened.

Ensure that adequate buffer space is available to the system. If necessary, increase the maximum number of sockets available to the system.

ADATCP is unable to listen for new connections. This usually indicates that the system resources available to complete the call are inadequate. If an error number is supplied with this message, it will help to identify the problem.

If system resources are inadequate, contact your systems administrator.

An attempt to allow currently used local addresses to be bound failed. This may indicate inadequate system resources. If an error number is supplied with this message, it will help to identify the problem.

If system resources are inadequate, contact your systems administrator.

ADATCP was unable to give control of a socket to a different process. This error occurs only if there is a problem with the socket itself. If an error number is supplied with this message, it will help to identify the problem.

The system was unable to create a new thread. This indicates inadequate system resources or memory to create the thread.

Contact your systems administrator.

ADATCP attempted to close a socket that was being used by another thread in the same process. This occurs only when the system is terminating due to some other error.

Check the console for other messages.

ADATCP was unable to allocate storage. This may indicate that inadequate storage is available on the system.

Contact your systems administrator.

ADATCP cannot receive data from a client. This may indicate that the connection between ADATCP and the client has been severed during a transaction or that system resources are inadequate to complete the call. The error number supplied with this message will identify the problem.

Contact your systems administrator.

The process that send requests to and from Adabas was unable to take control of the socket that was passed to it by the listening task.

Check the error number and the return code that accompany this message.

The main request task is unable to set the cancel type for the thread that is currently running.

Check the error number and the return code that accompany this message.

ADATCP is unable to send data from a client. The error number issued with this message indicates whether the problem is a severed connection between ADATCP and the client or insufficient system resources to complete the call.

Check the error number issued with this message.

ADATCP attempted to close a socket while it was being used by another thread in the same process. This occurs if the system has tried to terminate due to another error.

Check for other messages issued to the console.

The number of connections has reached a predefined limit; no entries can be added to the user context table.

Increase the ADARUN NU parameter value to the required number of entries and restart ADATCP.