EQQIP00 - EQQIP20

EQQIP00E

THE FOLLOWING QUEUE ELEMENT TO OR FROM THE AGENT IS NOT VALID: REQUEST.

The TCP/IP communication task detected an incorrect queue element on its queue.

The element is discarded from the TCP/IP communication task queue. Normal processing continues.

Save the message log (EQQMLOG) and the current plan (EQQCPxDS), and contact IBM Software Support.

Contact your system programmer.

Review the scheduler message log data set, EQQMLOG.

EQQIP01I

THE COMMUNICATION WITH THE RAGENTS THROUGH TCP/IP ENDED.

The TCP/IP communication task ended either because the scheduler started task is shutting down or as a result of an operator modify command to terminate this task or a related task.

The scheduler processing continues.

None.

EQQIP02E

THE COMMUNICATION WITH THE RAGENTS THROUGH TCP/IP ENDED DUE TO PROCESSING ERRORS.

The TCP/IP communication task terminated because of processing errors.

The scheduler processing continues.

If you cannot determine the cause of the error, save a storage dump of the scheduler address space, retain a copy of the message log and the job-tracking data sets, and contact IBM Software Support.

Contact your system programmer.

Check the scheduler message log and the dump data sets for additional information.

EQQIP03E

THE COMMUNICATION WITH THE RAGENTS THROUGH TCP/IP TERMINATED DUE TO A PROCESSING FAILURE. THE TASK WILL BE RESTARTED LATER.

An error occurred either when processing the initialization statements or in the communication with the TCP/IP address space.

The TCP/IP communication task ends. If the connection with the TCP/IP address space is lost, the TCP/IP communication task is restarted automatically.

Correct the ROUTOPTS initialization statements and restart the product.

Contact your system programmer.

Review previous messages in the scheduler message log.

EQQIP04E

THE COMMUNICATION WITH THE RAGENTS THROUGH TCP/IP ABENDED WHILE PROCESSING THE FOLLOWING REQUEST: REQUEST.

The error could be due to any of the following:

The TCP/IP started task is not started.
The TCPIPJOBNAME keyword in the TCPOPTS statement does not define a correct TCP/IP started task name.

If the request type is any of INIT, BIND, GHID, or LSTN, the TCP/IP communication task is terminated. For any other request type, the TCP/IP communication task closes the session with the corresponding started task. The session is reestablished.

Correct the error and restart the TCP/IP task. If the error recurs, save the message log (EQQMLOG) and contact IBM Software Support.

EQQIP05I

THE CONTROLLER HAS ACCEPTED A CONNECTION REQUEST FROM AGENT, WITH ADDRESS AND PORT IPADDR PORT AND HOST NAME HOSTNAME.

The TCP/IP communication task successfully connected to the remote agent identified by the message variables.

None.

EQQIP06E

AN UNDEFINED AGENT WITH ADDRESS AND PORT IPADDR PORT AND HOST NAMEHOSTNAME ATTEMPTED TO CONNECT TO THE CONTROLLER. THE REQUEST IS NOT ACCEPTED.

An external agent, identified by the message variables, attempted to connect to the local TCP/IP communication task. The TCPIP keyword of the controller ROUTOPTS statement does not identify the remote partner correctly.

Normal processing continues.

Correct any inconsistency in the initialization statements and restart the involved started task.

Contact your system programmer.

EQQIP07W

REJECTED REQUEST FROM AGENT AT ADDRESS AND PORT IPADDR PORT AND HOST NAMEHOSTNAME BECAUSE THE CONTROLLER STILL CONSIDERS IT CONNECTED.

The TCP/IP communication task rejected a connection attempt from an external agent because another connection, with a destination having the same IP address, is already active. The new connection is rejected and the old one is reset.

The local TCP/IP communication task is ready to accept a new connection from the external agent involved.

Check that the next connection attempt from the external agent is established successfully. If the error recurs, save the message log (EQQMLOG) and contact IBM Software Support.

EQQIP08E

RAGENTS COMMUNICATION ERROR ERRNO RECEIVED BY TCP/IP.

The local TCP/IP experienced the error indicated by ERRNO. The error occurred during the communication handling with RAGENTS. The most common decimal values for ERRNO are:

1115: After the local communication task closure, you restarted the local communication task before TCP/IP completed the resource release process. This error number might also indicate a local address used by another application.
1128: The local communication task failed to connect with a remote communication task that detected EQQIP08E message with ERRNO = 1115.

A blank value in ERRNO might indicate an SSL error during the access to the key or password databases. In this case, EQQIP08E message is followed by EQQIP16I message indicating SSL error on context initialization.

The TCP/IP communication task attempts to recover the error. The system waits approximately for 1 minute before attempting an automatic restart. In case of ERRNO = 1128 received by the tracker, it retries every minute to reestablish the connection with the controller, until the controller is up and running.

For ERRNO = 1128 in the tracker EQQMLOG, check the controller EQQMLOG for an EQQIP08E message with ERRNO = 1115: if you find it, wait for the controller communication task restart. Otherwise, try to identify the origin of the problem using further messages in the EQQMLOG. In case of SSL error on context initialization, possible causes are:

The file system, containing the key or password databases, is not mounted.
Either the key or password databases, or both, do not exist.
The TCPOPTS statement contains an error in either the SSLKEYSTORE or SSLKEYSTOREPSW keywords, or both.
The product components that are to communicate with each other do not specify the same SSLLEVEL value.

If you correct an error, and the correction requires a change in any initialization statement used by the scheduler, restart the involved started task.

Look for EQQIP16I in the message log (EQQMLOG) for additional information. Use ERRNO and the additional information to identify the error type. For details about network configuration or TCP/IP customization errors, refer to the z/OS Communications Server publications. For the complete list of the ERRNO values, refer to the z/OS Communication Server IP and SNA Codes and z/OS UNIX System Services Messages and Codes.

EQQIP09W

A BROKEN COMMUNICATION OCCURRED WITH THE AGENT IDENTIFIED BY ADDRESS AND PORT IPADDR PORT AND HOST NAME HOSTNAME.

The TCP/IP communication task rejected a communication attempt with an external agent because the socket was closed. The connection is automatically retried.

The local TCP/IP communication task is retrying to communicate with the external agent.

Check that the next connection attempt to the external agent is established successfully. Look for additional information in the AGENT EQQMLOG. If the error recurs, save the message log (EQQMLOG) and contact IBM Software Support.

EQQIP10W

THE CONNECTION TO AGENT WITH ADDRESS AND PORT IPADDR PORT WILL BE RESET.

The TCP/IP communication task resets the connection with an external agent. It could be due to configuration changes, resulting in an error condition such as duplicated connection. The connection is automatically retried.

The local TCP/IP communication task is ready to accept a new connection from the involved external agent.

Verify that the next connection attempt to the external agent is established successfully. Check the message log (EQQMLOG) and look for other messages that explain the error. If the error recurs, save the message log and contact IBM Software Support.

EQQIP11I

THE CONTROLLER IS WAITING FOR RAGENTS REQUESTS ON PROT ADDRESS AND PORT IPADDR PORT.

The TCP/IP communication task is ready to process network requests with the PROT protocol (IPV4 or IPV6), IPADDR IP address and PORT port number. The previous EQQIP16I message shows the local host name and port number.

The scheduler processing continues.

None.

EQQIP121I

THE COMMUNICATION WITH THE CONTROLLER IS UP.

A session was established between the local TCP/IP communication task and the controller.

The TCP/IP communication task processing continues.

EQQIP13W

AGENT WITH ADDRESS AND PORT IPADDR PORT SEEMS NOT ACTIVE.

The TCP/IP communication task detected a timeout condition after a request to the remote agent identified by the message variables. The connection is automatically retried.

The local TCP/IP communication task is ready to accept a new connection from the involved external agent.

EQQIP14W

THE CONTROLLER SEEMS NOT ACTIVE.

The TCP/IP communication task detected a timeout condition after a request to the controller. The connection is automatically retried.

The local TCP/IP communication task is ready to accept a new connection from the controller.

Verify that the next connection attempt to the controller is established successfully. Check the message log (EQQMLOG) and look for other messages that explain the error. If the error recurs, save the message log and contact IBM Software Support.

EQQIP15E

AGENT COMMUNICATION ERROR ERRNO RECEIVED BY TCP/IP ON CONNECTION WITH ADDRESS AND PORT IPADDR PORT.

The connection between the local TCP/IP communication task and an external agent AGENT experienced the error indicated by ERRNO. The most common decimal values for ERRNO are:

0111

A condition of denied permission occurred.

1115

After the local communication task closure, you restarted the local communication task before TCP/IP completed the resource release process. This error number might also indicate a local address used by another application.

1116

The HOSTNAME keyword of the TCPOPTS statement might contain a typing error in the IP address specification.

1128

The connection failed because of one of the following causes:

A valid current plan is not defined.
The controller did not start properly.
The controller address or port for is wrong.
A firewall blocks the address or port.

The TCP/IP communication task attempts to recover the error. The system waits approximately for 1 minute before attempting an automatic restart.

If the current plan is missing, define a valid current plan.

Try to identify the origin of the problem using further messages in the EQQMLOG. In case of ERRNO = 0111, the most common causes of the error are:

Incorrect RACF definition of the OMVS segment for the user ID associated to the scheduler started task.
The port number used by the scheduler started task is included in the port reservation list. Use the NETSTAT PORTLIST TSO command to verify the current port reservation list.

If you correct an error, and the correction requires a change in any initialization statement used by the scheduler, restart the involved started task.

The controller might have started without a valid current plan, for example at first startup after installation or after a REFRESH function (option 9.5).

EQQIP16I

TCPIPMSG

This message contains additional information for a related EQQIP11I, EQQIP08E, EQQIP15E, or EQQIP18I message.

Processing continues.

Integrate this information with the related EQQIP11I, EQQIP08E, EQQIP15E, or EQQIP18I message information. In case of SSL error, the most common causes are listed in SSL errors.

EQQIP17I

THE CONTROLLER HAS REJECTED A CONNECTION REQUEST FROM AGENT WITH ADDRESS AND PORT IPADDR PORT BECAUSE THE CONTROLLER CANNOT ACCEPT SSL REQUEST TYPES.

The controller and a remote partner run with TCPOPTS statements specifying different values in the SSLLEVEL keyword.

The scheduler processing continues.

Specify the same SSLLEVEL value for the scheduler started tasks that are to communicate with each other. Restart the involved started task.

EQQIP18I

TRYING TO CONNECT TO THE CONTROLLER WITH HOST NAME AND PORT HOSTNAME PORT .

The TCP/IP communication task is opening a connection with the controller identified by HOSTNAME PORT. The following EQQIP16I message shows the local host name and port number.

The scheduler processing continues.

None.

EQQIP19W

A BROKEN COMMUNICATION OCCURRED WITH THE CONTROLLER.

The TCP/IP communication task rejected a communication attempt with the controller because the socket was closed. The connection is automatically retried.

The local TCP/IP communication task is retrying to communicate with the controller.

Check that the next connection attempt to the external agent is established successfully. Look for additional information in the controller EQQMLOG. If the error recurs, save the message log (EQQMLOG) and contact IBM Software Support.

EQQIP20W

THE CONNECTION TO THE CONTROLLER WILL BE RESET. IT IS AUTOMATICALLY RETRIED IN APPROXIMATELY 60 SECONDS.

The TCP/IP communication task resets the connection to the controller. It could be due to configuration changes, resulting in an error condition such as duplicated connection. The connection is automatically retried every 60 seconds.

The local TCP/IP communication task is ready to accept a new connection from the controller. The system waits approximately for 1 minute before attempting an automatic restart.