Version 9.5 SP1
 —  Error Messages and Codes  —

Message Class 0074 - EntireX ACI - No request or Message Available

This message class is returned when no request or data/message is available for processing. However, no conversations are lost. It occurs only in SEND or RECEIVE operations in the following situations:

  1. The WAIT time specified in the ACI has elapsed in blocked operations.

  2. A non-blocked operation was issued and no request or data/message was available.

With clients in conversational mode, this response can be followed by a RECEIVE operation. We do not recommend retrying too often as the counterpart could be having problems, and so a loop is produced. When a new conversation is started with SEND and CONV-ID=NEW and this response is retrieved, the service requesting side (client) has a conversation, even if there is no server available. In this case, a RECEIVE or an EOC operation should follow. In non-conversational mode, the SEND operation can be retried, but ensure that no loop is programmed.

For servers retrieving this response is a normal situation when issuing a RECEIVE operation for incoming request/conversations. Usually the operation is retried, after reporting a "living message" in the server's log. We do not recommended waiting too long for a specific or old conversation, as the counterpart could be having problems, and servers should not be blocked too long by old conversations.

The messages have the format:

0074nnnn

where 0074 is the message class, and
nnnn is the message number in the range 0000 - 9999

Overview of Messages

00740009 | 00740074 | 00740300 | 00740301 | 00740345 | 00740346 | 00740347 | 00740399 | 00740480 | 00740481 | 00749460 | 00749461

00740009 Conversation Found - No Message
Explanation

The user polled for data/messages within an existing conversation (non-blocked RECEIVE with CONV-ID=n) and no data/message is available. However, the conversation still exists.

Action

This is an informational message. How the program continues depends on the application.


00740074 Wait Timeout Occurred
Explanation

The period specified by the WAIT field in the API has elapsed without any reply or request arriving to satisfy the Broker call. The conversation still exists and can continue.

Action

Check the following situations:

  1. In a RECEIVE for servers, this is an information message when not waiting for a specific conversation. No request is available for processing. The RECEIVE is normally issued again.

  2. When this occurs for a specific conversation, a RECEIVE can be issued to wait again for the data/message, or the conversation can be aborted with an EOC call.

  3. When this occurs in a client in non-conversational mode, the call can be retried.

  4. Check if the partner is working correctly.


00740300 Conversation found no units of work
Explanation

There is no unit of work available to be received in this conversation.

Action

This message is for diagnostic purposes only. Make sure that the sender sends and commits at least one unit of work in this conversation.


00740301 Conversation found end of unit of work
Explanation

The end of the unit of work was reached for this conversation prior to the last RECEIVE. Usually this means that an extra RECEIVE command was issued.

Action

This message is for diagnostic purposes only. Check ACI field UOWSTATUS to see if it indicates that the last RECEIVE for the UOW was processed. See UOWSTATUS under Broker ACI Fields.


00740345 Service MAX-UOWS Reached
Explanation

You are attempting to send a UOW to a service that already has queued to it the maximum number of UOWs allowed, as specified by the MAX-UOWS attribute.

Action

Increase the server's MAX-UOWS attribute or investigate why the server is not receiving and processing UOWs. If you increase the MAX-UOWS attribute, you may need to increase other attributes as well, for example NUM-CONVERSATION, NUM-LONG-BUFFER, NUM-SHORT-BUFFER.


00740346 Service Does Not Support UOW
Explanation

You are attempting to send a UOW to a service that does not accept UOWs, as indicated by MAX-UOWS=0 in the server's attribute definition.

Action

If the server is to handle UOWs, set its MAX-UOWS attribute to an appropriate non-zero value.


00740347 Max. Number of Messages per UOW Reached
Explanation

You are attempting to send a UOW that contains more messages than are allowed by the MAX-MESSAGES-IN-UOW attribute.

Action

If you increase the MAX-MESSAGES-IN-UOW attribute, you may also need to increase other attributes as well, for example NUM-LONG-BUFFER or NUM-SHORT-BUFFER.


00740399 Max messages per publication reached
Explanation

You are attempting to send a publication that contains more messages than are allowed by the MAX-MESSAGES-IN-PUBLICATION attribute.

Action

If you increase the MAX-MESSAGES-IN-PUBLICATION attribute, you may also need to increase other attributes as well, for example NUM-LONG-BUFFER or NUM-SHORT-BUFFER.


00740480 Publication found: end of data
Explanation

All messages for the current publication have been received: there is no more data

Action

Ensure messages belonging to publication have been processed and issue CONTROL_PUBLICATION command, OPTION=COMMIT.


00740481 Publication found: no data
Explanation

The user polled for data/messages within an existing publication (non-blocked RECEIVE with PUBLICATION-ID=n) and no data/message is available. However, the publication still exists.

Action

This is an informational message. How the program continues depends on the application.


00749460 POSITIVE CONFIRMATION RECEIVED
Explanation

CONFIRMATION=COA or COD was specified in the Directory Entry for this server, and a positive confirmation to a previous SEND has been received.


00749461 EXPIRATION REPORT RECEIVED
Explanation

EXPIRATION= specified in the Directory Entry for this server, and a message was sent, but has expired before being delivered to the server.


Top of page