Version 8.2.5
 —  Messages and Codes  —

ADACM* - ADATCP Messages

Overview of Messages

ADACM007E | ADACM008E | ADACM009E | ADACM010E | ADACM011I | ADACM012E | ADACM013E | ADACM014E | ADACM015E | ADACM016E | ADACM017I | ADACM018E | ADACM019E | ADACM020E | ADACM021E | ADACM022E | ADACM023E | ADACM024E | ADACM025E | ADACM026E | ADACM027E | ADACM028E | ADACM029E | ADACM030E | ADACM031E | ADACM032E | ADACM034E | ADACM035E | ADACM036E | ADACM037E | ADACM038E | ADACM039E

ADACM007E PARM ERROR
Explanation

One of the parameters passed within the URL was incorrect.

Action

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.


ADACM008E INVALID VALUE IN PORT= PARAMETER
Explanation

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

Action

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


ADACM009E URL=url ALREADY {ACTIVE | CLOSED}
Explanation

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

Action

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.


ADACM010E URL=url NOT FOUND
Explanation

The URL itself was not found.

Action

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.


ADACM011I URL=url HAS BEEN {CLOSED | OPENED}
Explanation

Either the URL was successfully closed or opened.

Action

None. This message is for information only.


ADACM012E THE NETWORK IS DOWN
Explanation

ADATCP cannot be started because the network is not active.

Action

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


ADACM013E NO BUFFER SPACE IS AVAILABLE
Explanation

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

Action

Ensure that sufficient storage is available on the system.


ADACM014E THE LINK HAS BEEN SEVERED
Explanation

An error caused TCP/IP or ADATCP to terminate.

Action

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


ADACM015E TCP/IP IS NOT INSTALLED OR ACTIVE
Explanation

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

Action

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


ADACM016E THE SOCKET DESCRIPTOR TABLE IS FULL
Explanation

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

Action

Increase the maximum number of sockets that can be created.


ADACM017I TCP/IP HAS TERMINATED
Explanation

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

Action

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


ADACM018E THE API CANNOT LOCATE THE TCP/IP SPECIFIED
Explanation

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

Action

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


ADACM019E THE TCP/IP NAME SPECIFIED IS NOT VALID
Explanation

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

Action

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.


ADACM020E TCP/IP FAILED TO LOAD
Explanation

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

Action

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


ADACM021E UNABLE TO ALLOCATE STORAGE FOR SOCKETCB
Explanation

ADATCP is unable to allocate the necessary storage.

Action

Ensure that adequate storage is available on the system.


ADACM022E INVALID OPERATING SYSTEM FOR API=HPS
Explanation

The operating system specified in the URL is incorrect.

Action

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


ADACM023E UNABLE TO INITIALIZE TCP/IP INTERFACE
Explanation

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

Action

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.


ADACM024E UNABLE TO GET A SOCKET
Explanation

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).

Action

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.


ADACM025E UNABLE TO BIND SOCKET TO LOCAL SYSTEM
Explanation

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

Action

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.


ADACM026E UNABLE TO ACCEPT CONNECTIONS
Explanation

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.

Action

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


ADACM027E UNABLE TO LISTEN FOR NEW CONNECTIONS
Explanation

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.

Action

If system resources are inadequate, contact your systems administrator.


ADACM028E UNABLE TO SET SOCKOPT REUSEADDR OPTION
Explanation

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.

Action

If system resources are inadequate, contact your systems administrator.


ADACM029E UNABLE TO GIVESOCKET TO NEW THREAD
Explanation

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.


ADACM030E UNABLE TO CREATE A NEW THREAD
Explanation

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

Action

Contact your systems administrator.


ADACM031E UNABLE TO CLOSE THE REQUESTED SOCKET
Explanation

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.

Action

Check the console for other messages.


ADACM032E UNABLE TO MALLOC STORAGE
Explanation

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

Action

Contact your systems administrator.


ADACM034E UNABLE TO RECEIVE DATA
Explanation

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.

Action

Contact your systems administrator.


ADACM035E UNABLE TO TAKE THE SOCKET
Explanation

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.

Action

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


ADACM036E UNABLE TO SET THE CANCEL TYPE
Explanation

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

Action

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


ADACM037E UNABLE TO SEND DATA
Explanation

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.

Action

Check the error number issued with this message.


ADACM038E UNABLE TO CLOSE THE SOCKET
Explanation

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.

Action

Check for other messages issued to the console.


ADACM039E CONTEXT TABLE FULL
Explanation

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

Action

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


Top of page