Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	e-docs.beasys.com   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
MessageQ Doc Home   |   Configuration Guide for OpenVMS   |   Previous Topic   |   Next Topic   |   Contents   |   Index

Error Log Messages

 

This appendix provides the following error log information:

• COM Server and Link Driver error log messages

• MRS and Journal Server error log messages

• SBS Server error log messages

COM Server and Link Driver Error Log Messages

This section lists and describes COM Server and Link driver error log messages. Use the following Key to understand conventions used in this section:

Key:

• g = Group ID decimal value

• q = Queue number decimal value

• n = A numeric value

• x = Hexadecimal value

• s = Character string value

• Italic text represents information that can vary in log messages.

Accepting connect from system system_name (as alias alias_name n.n.n.n) for group g (group_name)

Explanation: Informational.
A connect request from a system identifying itself as system_name has been received, but that system name does not exist in the MessageQ initialization file and/or the local network database. However, a different system name (alias_name) was located and it uses the same network address as system_name. The Link Driver assumes that one name is an alias for the other, and that they both refer to the same system.

The message indicates that the connection will be accepted, but under the name alias_name instead; to match existing definitions in the MessageQ initialization file and enforce consistency. All further console messages referring to this connection will display the alias_name system name, as will the MessageQ Monitor program.

User Action: If aliases are being used and both names refer to the same system, no action is necessary.

If the indicated system names system_name and alias_name do not refer to the same system, this indicates there are two systems on your network with the same network address, or with inconsistent network databases. You'll need to correct this situation and update the MessageQ initialization file if necessary.

Accepting connect from system system_name for groupg (group_name)

Explanation: Informational.
The server is accepting a network connection from another server with the indicated group ID. This message appears when a group connection requires two data links, and indicates that the inbound link is up.

User Action: None.

Accepted connect from system system_name for group g (group_name)

Explanation: Informational.
The server has accepted a network connection from another server with the indicated group ID, and the group connection is now available for use.
User Action: None.

An error occurred while freeing messages for process q PID (pid)

Explanation: Error.
The server, while attempting to clean up a process's queues, detected an error.
User Action: Contact MessageQ support with a description of the problem.

Attempt to double define group g into the RT

Explanation: Warning.
While loading a Routing Table entry, MessageQ found the same group definition in the Cross-Group Connection Table. Group entries can be created by the MessageQ Loader utility or by an unsolicited connection.
User Action: Determine the preferred style of connection to the group and remove the other entry.

Bad DECnet connect IOSB status for link to group g (group_name) on system system_name

Explanation: Warning.
An error was returned by DECnet when attempting to connect to another servers group.
User Action: Examine the error and determine if the cause of the error is due to a local DECnet error, remote system error, or a configuration error.

Bad PAMS_SET_TIMER return status for X-Group auto reconnect

Explanation: Warning.
MessageQ detected an error while attempting to set a wake-up timer for automatic cross-group reconnection.
User Action: Examine the failure status posted on the next line to determine if failure is due to a process quota problem.

Bad PAMS_SET_TIMER return status for X-group connect

Explanation: Warning.
MessageQ detected an error while attempting to set a timer for canceling the current cross-group reconnection cycle.
User Action: Examine the failure status posted on the next line to determine if failure is due to a process quota problem.

Bad PAMS_SET_TIMER return status for X-group connect to group g

Explanation: Warning.
MessageQ detected an error while attempting to set a wake-up timer for a specific cross-group reconnect attempt.
User Action: Examine the failure status posted on the next line to determine if failure is due to a process quota problem.

Bad PAMS_SET_TIMER return status for X-Group link protocol

Explanation: Error.
An error occurred when trying to declare an internal protocol timer. If recoverable, the link driver will attempt to continue.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Bad status from LIB$ASN_WITH_MBX in XDECNET

Explanation: Warning.
MessageQ detected an error while attempting to either initiate or complete a DECnet connection.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Bad XDECNET_POST_OOB_READ call

Explanation: Warning.
MessageQ detected an error while attempting to post a read $QIO to a DECnet Mailbox channel.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Bad XDECNET_POST_OOB_READ call for self

Explanation: Warning.
MessageQ detected an error while attempting to post a read $QIO to the main DECnet Mailbox channel.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Changing outbound for group g (group_name) to match inbound

Explanation: Warning.
An incoming connection request was received while an outbound connect was being performed to a different system or transport. The current outbound attempt will be dropped in favor of completing the incoming connection request.
User Action: None.

Connection for group g (group_name) to system system_name is down

Explanation: Warning.
All links to the indicated group are down.
User Action: Examine the previous messages for the indicated group and system for more information concerning the action.

Could not locate transport address (port number)

Explanation: Error.
The TCP/IP port number was omitted from the MessageQ initialization file definition for the local group.
User Action: The file must be corrected, or the transport will not be available for use.

DECnet communications lost to message queue group g (group_name)

Explanation: Warning.
The DECnet link to a remote COM Server aborted.
User Action: None.

DECnet communications lost to message queue group g (group_name) --- file not accessible

Explanation: Warning.
The current DECnet link to a remote COM Server is inaccessible.
User Action: None.

DECnet communications lost, 3rd party, to message queue group g (group_name)

Explanation: Warning.
An NCP command to disconnect the link was issued.
User Action: None.

DECnet data overrun from message queue group g (group_name)

Explanation: Warning.
The incoming message was larger than the internal buffer.
User Action: Compare the large buffer sizes of the two groups and adjust.

DECnet link exit to message queue group g (group_name)

Explanation: Warning.
A DECnet link exit was detected.
User Action: None.

DECnet path lost to message queue group g (group_name)

Explanation: Warning.
The DECnet path was lost to the remote group. This condition might be caused by a failure of the communication hardware.
User Action: Repair as necessary.

Detected DECnet network shutdown

Explanation: Warning.
A DECnet network shutdown is causing the MessageQ network object to be deleted.
User Action: None. The COM Server will automatically recreate the DECnet object soon after the network is restarted.

Dropped link to group g (group_name)

Explanation: Warning.
A DECnet link event caused a link to a group to be dropped.
User Action: Examine the failure status on the next line to determine if it is a quota or configuration problem.

Dropped link to group g (group_name) due to LLS buffer pool exhaustion

Explanation: Warning.
When attempting to queue a message received from another group, MessageQ found the buffer pool empty.
User Action: Increase the number of buffers in the buffer pool, decrease the receive byte quota for the queues, or change to a delivery mode that will pace the data across the link.

Dropped link to group g (group_name)

Explanation: Warning.
The link to the indicated group is being dropped due to an unusable condition.
User Action: Examine the previous messages for the indicated group for more information concerning the action.

Dropped link to remote logical group g which is incompatible with expected group g (group_name)

Explanation: Error.
While connecting to another group, the group was configured with a different group ID than what was stored in its own table.
User Action: Change the entries in the Cross-Group Connection Table in the group initialization file as necessary.

Duplicate process notification request from g.q discarded

Explanation: Warning.
An existing notification request was received.
User Action: None.

Duplicate queue notification request from g.q

Explanation: Warning.
An existing notification request was received.
User Action: None.

Duplicate Queue number passed to ENQ_PROCESS_LOCK_ASK routine = q

Explanation: Error.
Process Cleanup list has duplicate entries.
User Action: Contact MessageQ support for more detail on this error.

ENQ failed for "lock_name"

Explanation: Warning.
While attempting to create a MessageQ process lock to assist in queue cleanup, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

ENQ failed for DMQCS_GRP_LOCK of group g

Explanation: Error.
While attempting to obtain a MessageQ group lock, an error was detected.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

ENQ for "lock_name" not previously locked by process, releasing lock

Explanation: Warning.
While performing a PAMS_ATTACH_Q, a process exited before the COM Server could complete the attachment.
User Action: This problem could be related to processor load, process priorities, or the COM Server logging too many events.

ERROR --- No available temporary queues

Explanation: Error.
When attempting to allocate a temporary queue, MessageQ found the pool of available queues empty.
User Action: Increase the number of temporary queues by lowering the FIRST_TEMP_QUEUE value defined in the group initialization file.

Error converting protocol for group g (group_name)

Explanation: Error.
An unexpected error occurred while performing internal protocol conversions. The link to the group will be dropped.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Error during QIO xgroup send - grp:g

Explanation: Error.
The indicated QIO to the group shown failed to complete with an unexpected error. The connection to the group will be dropped.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Error while posting X-group rcv QIO for group g - channel #n

Explanation: Error.
The attempt to post the indicated QIO to the group and channel shown failed with an unexpected error. The connection to the group will be dropped.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Error from X410_POST_READ_OOB_CHAN QIO for group g --- channel #n

Explanation: Warning.
While attempting to post a DECnet $QIO read operation to a link's mailbox channel, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Error returned from X200_POST_CONNECT_REQUEST QIO

Explanation: Warning.
MessageQ detected an error while attempting to connect to a remote group.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Error while posting X-group rcv QIO for group g --- channel #n Dropped connection to group g

Explanation: Warning.
While attempting to post a DECnet $QIO read operation, MessageQ detected an error.
User Action: Examine the accompanying error status and determine if it is due to the inaccessibility of the remote group.

Exceeded max number of outstanding queue cleanup requests - request q dropped.

Explanation: Warning.
Exceeded the maximum number of outstanding process cleanup requests.
User Action: Reduce the number of processes requiring cleanup.

Exceeded process notification table --- request from g.q discarded

Explanation: Warning.
The number of requesters of process notification messages exceeds the number in the internal table.
User Action: Reduce the number of requesters.

Exceeded queue notification table --- request from g.q

Explanation: Warning.
The number of requesters of queue notification messages exceeds the number in the internal table.
User Action: Reduce the number of requesters.

Exceeded routing visit count - UMA taken
+ discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Error.
MessageQ could not deliver the message to its destination queue because the routing visit count has been exceeded. The UMA was taken.
User Action: Recheck routing table and correct as necessary.

Exceeded write quota on link
+ discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Error.
MessageQ could not deliver the message because the group buffer pool has been exceeded.
User Action: Increase the xgroup buffer pool in the X-Group section of the group initialization file.

Exceeded X-Group notification table --- request from g.q discarded

Explanation: Warning.
The number of requesters of cross-group notification messages exceeds the number in the internal table.
User Action: Reduce the number of requesters.

Failed on DMQCS_XDN_GET_READ_BUFFER

Explanation: Fatal.
Failed when attempting to read xgroup DECnet buffer.
User Action: Examine the failure status on the next line to determine the cause of the failure.

Failed on $CRELNM of termination mailbox lnm

Explanation: Error.
An error occurred while attempting to create the termination mailbox logical name DMQ$TERMINATION_MBX.
User Action: Examine the failure status on the next line to determine the cause of the failure.

Failed on $GETDVIW of temporary mailbox for Server spawning

Explanation: Error.
An error occurred while attempting to access mailbox channel.
User Action: Examine the failure status on the next line to determine the cause of the failure.

Failed on LIB$GET_VM_PAGE for DECnet MBX

Explanation: Fatal.
When attempting to acquire a DECnet mailbox buffer, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Failed on LIB$GET_VM_PAGE for DECnet abort link driver

Explanation: Error.
When attempting to acquire a transport control block buffer, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Failed on LIB$GET_VM_PAGE for DECnet TCB buffer

Explanation: Fatal.
When attempting to acquire a DECnet transport control block buffer, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Failed on LIB$GET_VM_PAGE for DECnet LCB

Explanation: Fatal.
When attempting to acquire a DECnet LCB buffer, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Failed on LIB$SPAWN of Server server_name

Explanation: Error.
An error occurred while attempting to spawn a server process.
User Action: Examine the failure status on the next line to determine the cause of the failure.

Failed on SYS$GETJPIW call for DMQ queue g.q

Explanation: Warning.
MessageQ detected an error while attempting to perform a SYS$GETJPIW service. This message is in conjunction with validating a requester's privileges.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Failed on searching rights list for "username" for DMQ queue g.q

Explanation: Warning.
MessageQ detected an error while attempting to validate a privileged request to the COM Server.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Failed on termination mbx SYS$QIO

Explanation: Error.
An error occurred while attempting to post a mailbox read.
User Action: Examine the failure status on the next line to determine the cause of the failure.

Failed to accept connect request from system system_name for group g

Explanation: Warning.
MessageQ detected an error while attempting to accept a connection from another group.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or if it is related to processor load.

Failed to accept connect request from system system_name for group g (group_name)

Explanation: Warning.
MessageQ detected an error while attempting to accept a connection from another group. Asterisks (****) for the group name indicate that the group was not previously loaded in the Cross-Group Connection Table.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or if it is related to processor load.

Failed to allocate GROUP entry during connect from group g --- Link dropped

Explanation: Warning.
While processing an incoming connect request for a previously unknown group, MessageQ detected an error during the allocation of an entry in the Cross-Group Connection Table.
User Action: Determine whether you need to increase the size of the Cross-Group Connection Table to accommodate the number of groups on the bus, or increase memory quotas.

Failed to allocate local buffer for I/O to group g (group_name)

Explanation: Error.
The link driver was unable to allocate buffer memory for performing I/O to the indicated group. The link to the group will be dropped.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Failed to allocate group entry during connect from group g - Link dropped to system system_name

Explanation: Error.
MessageQ failed to allocate a group entry structure.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Failed to allocate msg buffer for sending X-Group msg to group g (group_name)

Explanation: Error.
MessageQ failed to allocate a message buffer.
User Action: Examine the failure status posted on the next line to determine if it is due to the MessageQ buffer pool exhaustion.

Failed to allocate msg buffer for group notify msg.

Explanation: Warning.
While attempting to deliver a group notify message, MessageQ failed to allocate a message buffer.
User Action: Examine the failure status posted on the next line to determine if it is due to the MessageQ buffer pool exhaustion.

Failed to allocate msg buffer for notify msg

Explanation: Warning.
While attempting to deliver a process notify message, MessageQ detected an error in the message allocation routine.
User Action: Examine the failure status posted on the next line to determine if it is due to the MessageQ buffer pool exhaustion.

Failed to connect group g (group_name) to system system_name - System name is unknown

Explanation: Error.
A connection attempt could not be made to the indicated group because the system name does not exist in the applicable network database. And, if either a non-existent DNS server is configured or a non-existent system name is specified in the initialization file, this error may be reported and may cause other links of this LinkDriver to fail.
User Action: Change the MessageQ initialization file, add the entry to the network database to correct the condition, or check whether the DNS server is configured correctly.

Failed to convert outgoing message
+ discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Error.
MessageQ could not convert the outgoing xgroup message. The specified delivery mode and UMA combination are not support by the receiving group.

User Action: Correct as necessary.

Failed to create temporary mailbox for Server spawning

Explanation: Error.
An error occurred while attempting to create the termination mailbox required for server spawning.
User Action: Examine the failure status on the next line to determine the cause of the failure.

Failed to create termination mailbox read buffer

Explanation: Error.
An error occurred while attempting allocate space for the termination mailbox read buffer.
User Action: Examine the failure status on the next line to determine the cause of the failure.

Failed to map global section --- program exiting

Explanation: Fatal.
The link driver could not start due to being unable to connect to the internal global memory sections.
User Action: Contact MessageQ support with a description of the error.

Failed to create MessageQ DECnet object --- DECnet DISABLED

Explanation: Error.
While attempting to create the MessageQ DECnet named object, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem, DECnet failure, or system resource problem.

Failed to create n DECnet x-group queue heads n pagelets.

Explanation: Fatal.
When attempting to create the DECnet cross-group write list heads, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Failed to create DECnet x-group write tokens

Explanation: Fatal.
When attempting to create cross-group write tokens, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Failed to create DECnet x-group write tokens free list

Explanation: Fatal.
When attempting to create cross-group write tokens free list, MessageQ detected an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

Failed to create Event Logger MBX

Explanation: Error.
A failure occurred when attempting to create the Event Logger mailbox.
User action: Examine the failure status posted to determine why the mailbox could not be created.

Failed to create n entry RT Notify Table

Explanation: Error.
MessageQ detected an error while attempting to create the Routing Table data structure.
User Action: Examine the failure status on the next line to determine if it is a quota or configuration problem.

Failed to create n entry Queue Notify table

Explanation: Error.
MessageQ detected an error while attempting to create the Queue Notify Table data structure.
User Action: Examine the failure status on the next line to determine if it is a quota or configuration problem.

Failed to find group entry during connect from group g

Explanation: Warning.
An attempt to locate or add a new entry to the Cross-Group Connection Table resulted in an error.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

** Failed to init the print stream **

Explanation: Fatal.
An error occurred while MessageQ attempted to initialize the output streams.
User Action: Examine the failure status on the next line to determine if it is a quota or configuration problem.

Failed to initialize DECnet communication

Explanation: Error.
An error occurred while MessageQ attempted to initialize DECnet communication.
User Action: Examine the failure status on the next line to determine if it is a configuration problem.

Failed to load NT into TCB for group g (group_name), table entry = group_index, NT = cur_nt

Explanation: Error.
MessageQ detected an error while attempting to load the NT structure into the Transport Control Block.
User Action: Examine the failure status posted on the next line to determine the source of the problem.

Failed to send group notify msg to g.q

Explanation: Warning.
MessageQ detected an error while attempting to queue a notification message.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Failed to send notify msg to g.q

Explanation: Warning.
MessageQ detected an error while attempting to queue a notification message.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Failed to send PAMS request CHKPT_FILE_RESP msg to g.q

Explanation: Warning.
MessageQ detected an error while attempting to queue a CHKPT_FILE_RESP messages.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Failed to send PAMS request NAK msg to g.q

Explanation: Warning.
MessageQ detected an error while attempting to send an internal server NAK message. notification message.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Failed to send queue notify msg to g.q

Explanation: Warning.
MessageQ detected an error while attempting to queue a notification message.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Failed to send RT update notify msg to g.q

Explanation: Warning.
MessageQ detected an error while attempting to queue a notification message.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Failed to start network listener

Explanation: Informational.
The link driver could not start because the transport listener failed (most probably because the network is not running).
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Failed to startup the MessageQ Event Logger - Exiting

Explanation: Fatal.
The attempt to start the Event Logger failed.
User Action: Examine the failure status on the next line to determine if it is a quota or configuration problem.

Failed to startup the server_name

Explanation: Error.
The attempt to create the indicated MessageQ link driver or server process failed.
User Action: Examine the failure status on the next line to determine if it is a quota or configuration problem.

Failed to translate rights ID "rights_id" for DMQ queue g.q

Explanation: Warning.
MessageQ detected an error while performing a SYS$ASCTOID to validate a requester's privileges.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Failed to wakeup process to complete the queue attach --- PID: "pid"

Explanation: Error.
The COM Server was unable to queue an AST to a process in order to attach the process to a queue.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Fatal error while creating GNT

Explanation: Fatal.
MessageQ detected an error during the creation of the Group Name Table global section.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Fatal error while creating Large LLS Pool

Explanation: Fatal.
MessageQ detected an error during the creation of the large Link List Section or buffer pool global section.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Fatal error while creating MCS

Explanation: Fatal.
MessageQ detected an error during the creation of the message control global section.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Fatal error while creating MRQ Section

Explanation: Fatal.
MessageQ detected an error during the creation of the Multi-reader Queue Global Section.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Fatal error while creating Medium LLS Pool

Explanation: Fatal.
MessageQ detected an error during the creation of the medium Linked List Section or buffer pool global section.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Fatal error while creating Small LLS Pool

Explanation: Fatal.
MessageQ detected an error during the creation of the small Linked List Section or buffer pool global section.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

GNT already exists --- Reinitializing

Explanation: Error.
While attempting to create the Group Name Table global section, MessageQ found that the table already exists.
User Action: None.

Group g (group_name) OUTBOUND link to system system_name is not responding

Explanation: Error.
A communications handshaking or protocol error has occurred on the connection to the indicated group. The remote group is not responding. The group connection will be dropped.
User Action: If the problem persists, contact MessageQ support with a description of the error.

Ignored connect confirm from system system_name group g due to security match failure

Explanation: Error.
XGROUP_VERIFY has been enabled and the connection confirmation does not match the information found in the Cross-Group Connection Table.
User Action: Correct as necessary.

Ignoring connect request from system system_name - group g is in link management transition

Explanation: Warning.
The connection request received from the indicated system cannot be processed because the group was caught during in an internal state transition.
User Action: Reattempting the connection, possibly at a later time, should succeed. Repeated occurrences of this warning for the same group may indicate an internal problem which will only get corrected by restarting that group. Contact MessageQ support under this condition.

Ignoring connection for group g (group_name) from system system_name --- link already established

Explanation: Warning.
An incoming connection for a group was received from a system different than the one that it is currently connected to. This is an indication of two groups having the same group number on the same bus.
User Action: Change the group number of system that is the duplicate.

Ignoring connection from system system_name for group g group_name --- connection already on another transport

Explanation: Warning.
An incoming connection was rejected because a link to that group already existed and is owned by another link driver.
User Action: None.

Ignoring LD_REQUEST_ACCEPTED msg from g.q --- cannot locate link

Explanation: Warning.
A valid group ownership "REQUEST ACCEPTED" message from the server at the indicated address was received, but there was no such request outstanding.
User Action: Isolated occurrences of this message can be ignored if there are reasons to suspect that the network became inaccessible, or there were connection collisions, just before the message was received.

Ignoring LD_REQUEST_ACCEPTED msg from g.q --- unexpected error

Explanation: Error.
An attempt to process a "REQUEST ACCEPTED" response to an ownership transfer failed due to an unexpected error. The group may no longer accept connects.
User Action: Examine the status posted on the next line to determine the error condition encountered, and the corrective action required.

Ignoring LD_REQUEST_DENIED msg from g.q --- cannot locate link

Explanation: Warning.
A valid group ownership "REQUEST DENIED" message from the server at the indicated address was received, but there was no such request outstanding.
User Action: Isolated occurrences of this message can be ignored if there are reasons to suspect that the network became inaccessible, or there were connection collisions just before the message was received. Repeated occurrences of this message may indicated a problem. Under this condition, contact MessageQ support.

Ignoring LD_REQUEST_DENIED msg from g.q --- unexpected error

Explanation: Error.
An attempt to process a "REQUEST DENIED" response to an ownership transfer failed due to an unexpected error. The group may no longer accept connects.
User Action: Examine the status posted on the next line to determine the error condition encountered and the corrective action required.

Invalid disable queue notification request from g.q

Explanation: Warning.
An invalid Queue Notification deregistration request message was received.
User Action: Recheck the request message for validity using script message tracing.

Invalid DMQ$BUS_GROUP = "s"

Explanation: Fatal.
MessageQ detected an invalid setting of the logical DMQ$BUS_GROUP.
User Action: Correct as necessary.

Invalid queue list request from g.q

Explanation: Warning.
An invalid queue list request message was received.
User Action: Recheck the request message for validity using script message tracing.

Invalid Queue Notification Request from g.q

Explanation: Warning.
A queue notification registration request message was received that was invalid.
User Action: Recheck the request message for validity using script message tracing.

Invalid msg targeted to server_name
+ discarded msg - Src=g.q Target=g.q class=n type=n

Explanation: Warning.
The indicated server received a message of a class and type that it does not recognize.
User Action: Correct as necessary.

Invalid X-Group number g specified for self

Explanation: Fatal.
Local group number is out of range.
User Action: Correct as necessary.

Invalid X-Group request to declare a temporary SQ - Source=g.q

Explanation: Warning.
A non local process attempted to attach a temporary secondary queue.
User Action: Correct as necessary.

Invalid undeclare SQ request --- SQ #q Source=g.q

Explanation: Error.
A request was made to detach a secondary queue from a process that was invalid, did not own the queue, or it was not a secondary queue.
User Action: Correct as necessary.

Large buffer size is too small, adjusting large buffer size to n

Explanation: Warning.
The Large buffer size provided in the group initialization file is too small. It must be larger than both the small and medium buffers.
User Action: Increase the size of the large buffers in the group initialization file.

Large LLS Pool already exists --- two DMQ COM Servers running

Explanation: Fatal.
While attempting to create the large linked list section (LLS), MessageQ found that the section already exists. This error means that one or more processes have not unmapped the global sections so that the system can delete them. This error could be caused by a process in the debugger, or the user mode ASTs might be disabled.
User Action: Search for processes that are still attached to MessageQ and cause them to exit. You can search for processes using DMQ$EXE.DMQ$SCAN_SYSTEM_FOR_DMQ.COM.

Link Driver has terminated

Explanation: Warning.
The link driver has terminated execution.
User Action: Examine the previous messages, and the log file, for more information concerning the action.

Link Management request from g.q rejected

Explanation: Error.
A Link Management request message, generated by a user program, was received either from an nonprivileged user or from another group.
User Action: Investigate proper authorization of request.

Listener is down - network not currently accessible

Explanation: Error.
The transport listener cannot declare itself due to the network being inaccessible. The transport is no longer available for use in group connections.
User Action: Bringing the network up again will automatically cause the link driver to restart itself and all connections.

Load complete message received from g.q --- Ignored

Explanation: Warning.
A non local load complete message was received.
User Action: Correct as necessary.

Local host address lookup failed

Explanation: Fatal.
The link driver cannot execute because it cannot find its own system address in the applicable network database.
User Action: Examine the network database, and the MessageQ initialization file.

Local host name lookup failed

Explanation: Fatal.
The link driver failed to located the local host name in the network database.
User Action: Examine the network database, and the MessageQ initialization file.

Local system is system_name, transport addr s

Explanation: Informational.
Identifies the system and transport address of the link driver starting up.
User Action: None.

Local system system_name is not listed for this group g under this transport

Explanation: Fatal.
The specified system name is not listed for this group under this transport in the groups initialization file.
User Action: Update the group initialization file and restart the group.

Local system name is too long

Explanation: Fatal.
Maximum DECnet system name is 6 characters.
User Action: Modify the group initialization file and restart the group.

Logical DMQ$SET_GBLSEC_PROT value "s" is invalid

Explanation: Fatal.
The format of the DMQ$SET_GBLSEC_PROT logical name is invalid.
User Action: Correct as necessary.

** LOW BUFFER WARNING --- LARGE FREE LIST --- TOTAL:n CURR:n WARN:n **

Explanation: Warning.
The number of large free buffers available has reached the warning level.
User Action: You might need to adjust send rate, total number of large buffers available, or receive byte quota on the message queues.

** LOW BUFFER WARNING --- MEDIUM FREE LIST --- TOTAL:n CURR:n WARN:n **

Explanation: Warning.
The number of medium free buffers available has reached the warning level.
User Action: You might need to adjust send rate, total number of medium buffers available, or receive byte quota on the message queues.

** LOW BUFFER WARNING --- SMALL FREE LIST --- TOTAL:n CURR:n WARN:n **

Explanation: Warning.
The number of small free buffers available has reached the warning level.
User Action: You might need to adjust send rate, total number of small buffers available, or receive byte quota on the message queues.

MCS already exists --- two DMQ COM Servers running

Explanation: Fatal.
While attempting to create the message control section (MCS), MessageQ found it to already exist. This error means that one or more processes have not unmapped the global sections so that the systems can delete them. This error could be caused by a process in the debugger or because the user mode ASTs are disabled.
User Action: Search for processes that are still attached to MessageQ and cause them to exit. You can search for processes using DMQ$EXE.DMQ$SCAN_SYSTEM_FOR_DMQ.COM.

Medium buffer size is too small, adjusting medium buffer size to n

Explanation: Warning.
The medium buffer size provided in the group initialization file is too small. It must be larger than the small buffer size.
User Action: Increase the size of the medium buffers in the group initialization file.

Medium LLS Pool already exists --- two DMQ COM Servers running

Explanation: Fatal.
While attempting to create the medium linked list section (LLS), MessageQ found that it already exists. This error means that one or more processes have not unmapped the global sections so that the system can delete them. This error could be caused by a process in the debugger, or because the user mode ASTs are disabled.
User Action: Search for processes that are still attached to MessageQ and cause them to exit. You can search for processes using DMQ$EXE.DMQ$SCAN_SYSTEM_FOR_DMQ.COM.

Message lost (undeliverable)
+ discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Error.
MessageQ could not deliver the message to its destination queue. The UMA will be taken.
User Action: Correct as necessary.

Message received from bus returned error

Explanation: Error.
An attempt to receive a message from the MessageQ message bus returned an unexpected error.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Msg from system system_name is larger than negotiated maximum for group g (group_name)

Explanation: Error.
A message was received from the indicated system that exceeds the maximum size supported for the group. The connection to the group will be dropped. This message indicates a mismatched configuration between the two groups, or an attempt to use link management services on a group that has a message length maximum below the minimum requirements.
User Action: Change the group configuration to support a size maximum large enough to handle the message.

MONITOR terminate requests are disabled

Explanation: Warning.
A user attempted to shut down the COM Server by using the "Kill COM Server" MONITOR command. This command has been explicitly disabled by setting the ACCEPT_KILL_CMD to No in the Profile section of the group initialization file.
User Action: Correct as necessary.

Msg lost (bad target address)
+ discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Error.
MessageQ could not deliver the message to its destination queue because the destination queue could not be found. The UMA will be taken.
User Action: Correct as necessary.

Network listener has been restarted

Explanation: Informational.
The link driver has automatically recovered from previously being unable to declare its listener (most probably due to the network being inaccessible).
User Action: None.

Network listener is down!

Explanation: Error.
The transport listener cannot declare itself due to an unknown error condition. The transport is no longer available for use in group connections.
User Action: Examine the error status posted on the next line to determine the network problem. Correcting the problem and bringing the network up again will automatically cause the link driver to restart itself and all connections.

Network is down - all links will be dropped

Explanation: Error.
The network has become inaccessible and all existing connections to groups are being dropped. The link driver will retry connections if the network becomes accessible again.
User Action: Restart the network.

Network protocol error occurred for message queue group g (group_name)

Explanation: Error.
A DECnet protocol error occurred on the specified link to the remote group.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

No available temporary queues - Unable to allocate temp SQ - Source=g.q

Explanation: Warning.
While attempting to allocate a temporary secondary queue to a process, MessageQ found the pool of available queues to be empty.
User Action: Increase the number of temporary queues by lowering the FIRST_TEMP_QUEUE value in the groups initialization file.

No available temporary queues --- Unable to allocate queue --- Source=g.q

Explanation: Warning.
While attempting to allocate a temporary queue to a process, MessageQ found the pool of available queues to be empty.
User Action: Increase the number of temporary queues by lowering the FIRST_TEMP_QUEUE value in the groups initialization file.

No memory for buffer for message queue group g (group_name)

Explanation: Error.
An error was detected by DECnet software while attempting to create buffers for use by the specified link.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.

Protocol error on OUTBOUND link for group g (group_name) to system system_name

Explanation: Error.
A communications handshaking or protocol error has occurred on the connection to the indicated group. The group connection will be dropped.
User Action: If the problem persists, contact MessageQ support with a description of the error.

Rejected connect attempt to/for group g - Ownership transfer denied by g.q

Explanation: Warning.
The connection attempt was rejected because a request for group ownership transfer was denied by the server at the indicated address.
User Action: None.

Rejected connect request for group g - system could not be determined

Explanation: Error.
The connection request cannot be accepted because the remote system could not be determined. This may indicate an error in the MessageQ initialization file, or that the system is not listed in the appropriate network database.
User Action: Examine and correct the MessageQ initialization file(s) or network database.

Rejected connect request for group g from system system_name (system_address) - address disagrees with network database

Explanation: Error.
A connection attempt was received from a system whose name and address do not match the information in the applicable network database. The connection request will be rejected.
User Action: Check that the system names and addresses in the network database agree with each other, and with the MessageQ initialization file(s).

Rejected connect request for group g from system system_name - outbound attempt failed

Explanation: Error.
An outbound connection attempt to the indicated system and group failed due to an unknown error condition.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Rejected connect request for group g from system system_name (system_address) - system not found in network database

Explanation: Warning.
A connection attempt was received from a system that does not exist in the applicable network database.
User Action: The MessageQ initialization file(s) may be in error, or the system may need to be added in the network database.

Rejected connect request from system system_name due to security match failure (group unknown)

Explanation: Error.
XGROUP_VERIFY has been enabled and the connect request does not match the information found in the Cross-Group Connection Table.
User Action: Correct as necessary.

Rejected connect request from system system_name due to wrong bus

Explanation: Error.
The connection attempt was rejected because it came from a different MessageQ bus.
User Action: Correct the environment so that the group connections are for the same bus.

Rejected connect request from system system_name group g due to security match failure

Explanation: Error.
XGROUP_VERIFY has been enabled and the connect request does not match the information found in the Cross-Group Connection Table.
User Action: Correct as necessary.

Rejected connect request from system system_name for group g (group_name) - Connection already in progress by b.g

Explanation: Warning.
The connection request received from the indicated system was rejected because the connection is already in progress.
User Action: None.

Rejected connect request from system system_name for group g (group_name) - connection currently in progress

Explanation: Warning.
The connection request received from the indicated system was rejected because the connection is currently in progress.
User Action: None.

Rejected connect request from system system_name for group g (group_name) - connection still in progress

Explanation: Warning.
The connection request received from the indicated system was rejected because the connection is still in progress.
User Action: None.

Rejected connect request from system system_name group g - Group disabled

Explanation: Warning.
An incoming connect request was denied because connections are currently disabled. This can be due to the group being disabled on startup or by way of a Link Management message disconnecting the link.
User Action: When ready to allow links to this group, send a Link Management message to enable connections.

Rejected connect request from system system_name for group g (group_name) - group is already connected

Explanation: Warning.
A connection request was received from the indicated system for a group that is already connected (possibly to a different transport).
User Action: None.

Rejected connect request from system system_name for group g (group_name) - group is disabled

Explanation: Warning.
An incoming connect request was denied because connections are currently disabled. This can be due to the group being disabled on startup or by way of a Link Management message disconnecting the link.
User Action: When ready to allow links to this group, send a Link Management message to enable connections.

Rejected connect request from system system_name (system_address) - Improper Protocol response received

Explanation: Error.
A connection attempt from the indicated system was rejected because of a communications protocol failure. This may indicate a non-linkdriver program (perhaps a non-MessageQ program), or an incompatible MessageQ system is attempting the connection.
User Action: Investigate the system and program attempting the connection.

Rejected connect request from system system_name for group g group_name -Link Driver or network is shutting down

Explanation: Error.
The connect request is ignored because either the link driver, the network, or the system is shutting down.
User Action: Correct as necessary.

Rejected connect request from system system_name for group g (group_name) - Link is currently in transition

Explanation: Warning.
The connection request from the indicated system was rejected because an interruptable link transition was already in progress for that group.
User Action: Reattempting the connection, possibly at a later time, should succeed. Repeated occurrences of this warning for the same group may indicate an internal problem which will only get corrected by restarting that group. Contact MessageQ support under this condition.

Rejected connect request from system system_name for group g (group_name) - Lost conflict resolution

Explanation: Warning.
The connection request received from the indicated system was rejected due to a different transport currently owning the group.
User Action: None.

Rejected connect request from system system_name for group g (group_name) - read link is currently in transition

Explanation: Warning.
The connection request received from the indicated system was rejected because the read link is currently in transition.
User Action: None.

Rejected connect request from system system_name for group g (group_name) - write link is currently in transition

Explanation: Warning.
The connection request received from the indicated system was rejected because we own this group, and there's already an outbound, and that outbound is currently shutting down.
User Action: None.

Rejected connect request from system system_name (system_address) - protocol not supported

Explanation: Error.
A connection attempt was received from a system running a MessageQ release that is incompatible with the link driver.
User Action: None.

Remote system not listed for this group/transport

Explanation: Error.
The connection request is rejected because the remote group is not listed for this group or transport and XGROUP_VERIFY is YES.
User Action: Correct as necessary.

Server_name has exited

Explanation: Warning.
The indicated link driver or server process has terminated.
User Action: Determine the reason for the termination by examining the link driver or server log files in DMQ$LOG:.

Skipping connect to group g (group_name) - Failed to send external ownership request to b.g

Explanation: Error.
A connection to the indicated group could not be attempted because of a failure to send an external ownership request to the specified group.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Skipping connect to group g (group_name) - No outbounds possible or allowed

Explanation: Informational.
A connect attempt to the indicated group was not possible or not supported.
User Action: None.

Skipping connect to group g (group_name) - System address cannot be determined

Explanation: Informational.
A connection cannot be attempted to the indicated group because the system address could not be determined. This may indicate an error in the MessageQ initialization file, or that the named system is not listed in the appropriate network database.
User Action: Examine and correct the MessageQ initialization file(s) or network database.

Skipping connect to group g (group_name) - unexpected error encountered

Explanation: Error.
A connection to the indicated group could not be attempted due to an unexpected error condition.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

Small LLS Pool already exists --- two DMQ COM Servers running

Explanation: Fatal.
While attempting to create the small Linked List Section, MessageQ found them to already exist. This means that one or more processes have not unmapped the global sections so that the system can delete them. This may be due to a process in the debugger or because the user mode ASTs are disabled.
User Action: Search for processes that are still attached to MessageQ and cause them to exit. You can search for processes using DMQ$EXE.DMQ$SCAN_SYSTEM_FOR_DMQ.COM.

Starting server_name

Explanation: Informational.
The specified server has been spawned by the COM server.
User Action: None.

Server_name Initialized

Explanation: Informational.
The link driver or server specified has successfully started running.
User Action: None.

SYS$CRELNM failed to create logical_name in lnm tbl table_name

Explanation: Warning.
The call to SYS$CRELNM returned a failure while attempting to create the logical name in the specified table.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

SYS$CRELNM failed to create DMQ$VERSION

Explanation: Warning.
The call to SYS$CRELNM returned a failure while attempting to create the DMQ$VERSION logical name.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.

This linkdriver is already running --- exiting

Explanation: Error.
This link driver is already running, or previously terminated abnormally, and cannot be restarted.
User Action: If it is not an accidental attempt to run two copies of the same link driver, you must restart the group to clear the condition.

This transport is not listed for this group g

Explanation: Fatal.
The link driver cannot execute because the applicable transport does not appear in any of the systems listed for the local group.
User Action: The MessageQ group initialization file will need to be corrected; otherwise, the transport will not be available for use.

Timed out waiting for link driver(s) to start

Explanation: Error.
One or more Link Drivers failed to initialization within the timeout period.
User Action: Determine the cause by checking the link drivers log file to see if there was a startup failure or messaging error. It also could be due to system load which can be determined by comparing time-stamp on the link driver "Startup completed" message and this error in the COM Server log file.
The timeout period for server startup can be modified by providing a server startup time parameter to the DMQ$STARTUP.COM command line.

Transport address doesn't match xgroup entry

Explanation: Error.
The transport address does not match the address in the xgroup entry table and XGROUP_VERIFY is YES.
User Action: Correct as necessary.

Transport address is already in use by another process

Explanation: Fatal.
The transport listener cannot declare itself because the transport address (port number), as defined in the MessageQ initialization file for the local group, is already being used by another process.
User Action: Free up the address, or change the MessageQ initialization file(s) to use a different transport address.

Transport not supported by group

Explanation: Error.
The connection request is rejected because the specified transport is not supported by this group and XGROUP_VERIFY is YES.
User Action: Correct as necessary.

TP PROTOCOL ERROR: invalid substate n on INBOUND link to group g (group_name)

Explanation: Error.
A communications handshaking or protocol error has occurred on the connection to the indicated group. The group connection will be dropped.
User Action: If the problem persists, contact MessageQ support with a description of the error.

TP PROTOCOL ERROR: invalid substate n on OUTBOUND link to group g (group_name)

Explanation: Error.
A communications handshaking or protocol error has occurred on the connection to the indicated group. The group connection will be dropped.
User Action: If the problem persists, contact MessageQ support with a description of the error.

Unable to deassign DECnet data I/O channel for group g in XDECNET

Explanation: Warning.
MessageQ detected an error when attempting to deassign an I/O channel for a remote group.
User Action: Verify whether an earlier link error is causing this problem.

Unable to deassign DECnet OOB channel for group g in XDECNET

Explanation: Warning.
MessageQ detected an error when attempting to deassign a DECnet OOB channel for a remote group.
User Action: Verify whether an earlier link error is causing this problem.

Unable to declare temporary SQ --- Source=g.q

Explanation: Warning.
An error was detected while attempting to attach a temporary secondary queue.
User Action: Examine the failure status posted on the next line to determine the cause of the problem.

Unable to locate DECnet TCB for group g

Explanation: Error.
MessageQ was unable to locate a DECnet entry for the group in the transport control block.
User Action: Make sure DECnet is specified for the group in the group initialization file.

Unable to locate local group definition --- Cross-group disabled

Explanation: Error.
MessageQ was unable to locate the entry in the cross-group table that defines the local group. This is required to be present when cross-group support has been enabled.
User Action: Edit the group initialization file (DMQ$INIT.TXT) and either define the local group in the cross-group table or disable cross-group support.

Unable to return link management response to g.q

Explanation: Warning.
MessageQ detected an error while attempting to send a link management response message.
User Action: Examine the failure status posted on the next line to determine the cause of the problem.

Unable to return list of groups to g.q

Explanation: Warning.
MessageQ detected an error while attempting to send a group list message.
User Action: Examine the failure status posted on the next line to determine the cause of the problem.

Unable to return list of processes to g.q

Explanation: Warning.
MessageQ detected an error while attempting to send a process list message.
User Action: Examine the failure status posted on the next line to determine the cause of the problem.

Unable to return list of queues to g.q

Explanation: Warning.
MessageQ detected an error while attempting to send a queue list message.
User Action: Examine the failure status posted on the next line to determine the cause of the problem.

Unable to return queue notify disable response to g.q

Explanation: Warning.
MessageQ detected an error while attempting to send a queue notify disable response message.
User Action: Examine the failure status posted on the next line to determine the cause of the problem.

Unable to send link arbitration msg for group g to g.q

Explanation: Error.
An attempt to respond to a request for transfer of group ownership failed.
User Action: Examine the status posted on the next line to determine the error condition encountered and the corrective action required.

Unable to send message to target - exceeded x-group buffer maximum
+ discarded msg - Src=g.q Target=g.q class=n type=n

Explanation: Error.
An attempt was made to send a message that is larger than the receiving groups GROUP_MAX_MESSAGE_SIZE.
User Action: Increase the receiving groups GROUP_MAX_MESSAGE_SIZE in the groups initialization file.

Unblock msg lost (buffer allocation failed)

Explanation: Warning.
An attempt to send an unblock message failed because a buffer could not be allocated. No more memory.
User Action: Increase page file quotas for the server and restart group.

XGroup not enabled --- program exiting

Explanation: Fatal.
The ENABLE_XGROUP parameter in the group initialization file is set to NO.
User Action: Set the ENABLE_XGROUP parameter in the group initialization file to YES. Restart the group.

X-Group write failed to group g (group_name)
+ Discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Warning.
A cross-group connection request between the listed groups failed.
User Action: None.

X-Group write failed to group g (group_name)
+ Message lost - protocol translation or UMA failure

Explanation: Error.
An attempt to send a x-group message to a remote system failed due to an unknown error condition, and the message cannot be recovered.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.

X-Group write pool overflow for group g

Explanation: Warning.
One or more programs have generated message traffic to a remote message queuing group at a rate faster than can be sent. This traffic eventually results in cross-group buffer pool overflowing and therefore requires the Undeliverable Message Action (UMA) to be taken.
User Action: Change the delivery mode to one that will inherently cause pacing, increase the cross-group buffer pool so that it can absorb the temporary burst of messages, or embed a pacing protocol in the application dialogue.

Additional Information on Link Drivers Error Status Reporting

The DECnet and TCP/IP Link Drivers share a common error status reporting translation routine. For example, SS$_REJECT would be logged, however the actual error is transport dependent: MSG$_REJECT for DECnet, and ECONNREFUSED for TCP link drivers. Refer to the table below and further to the documentation reference for additional information.

Displayed Status	TCP/IP	DECnet
SS$_REJECT	ECONNREFUSED - Connection refused No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host.	MSG$_REJECT - Connect Reject The object at remote host was not available or has actively rejected the connection.
SS$_UNREACHABLE	EHOSTUNREACH - No route to host ENETUNREACH - Network is unreachable A socket operation was attempted to an unreachable host or network.	MSG$_NODEINACC - Node has become inaccessible
SS$_TIMEOUT	ETIMEDOUT - Connection timed out. A "connect()" request failed because the connected party did not properly respond after a period of time. (The timeout period is dependent on the communication protocol.)	MSG$_TIMEOUT - Connect timeout
SS$_ABORT	(Not Used)	MSG$_ABORT - Partner aborted link
SS$_SHUT	ESHUTDOWN - Can't send after socket shutdown ENETDOWN - Network is down A socket operation encountered a dead network.	MSG$_NETSHUT - Network shutting down

Reference DEC TCP/IP Services for OpenVMS System Service and C Socket Programming Table 6-1: errno Values for further error message details for TCP/IP. Reference DECnet for OpenVMS Networking Manual Chapter 8 for further error message details for DECnet.

MRS Server Error Log Messages

This section lists and describes MRS Server error log messages. Use the following Key to understand conventions used in this section:

Key:

• g = Group ID decimal value

• q = Queue number decimal value

• n = A numeric value

• x = Hexadecimal value

• s = Character string value

• Italic text represents information that can vary in log messages.

JRN_E_DLJ_FILES, NUM_DLJ_AREAS quota exceeded

Explanation: Error.
An error occurred while the Journal server was attempting to create a new DLJ file. The maximum number of DLJ files has been reached.
User Action: Increase NUM_DLJ_AREAS in group initialization file or increase AREA_SIZE to decrease the number of files required.

JRN_E_PCJ_FILES, NUM_PCJ_AREAS quota exceeded

Explanation: Error
An error occurred while the Journal server was attempting to create a new PCJ file. The maximum number of PCJ files has been reached.
User Action: Increase NUM_PCJ_AREAS in group initialization file or increase AREA_SIZE to decrease the number of files required.

JRN_E_INIT, JRN Server did not initialize properly

Explanation: Error.
The Journal Server did not complete its initialization process.
User Action: Check EVL and JRN server logs for errors.

JRN_E_INVDIPRP, Invalid recovery protocol:n for msg (x,x) with DIP:delivery_mode

Explanation: Error.
The MRS Server will reject messages that are targeted to a 1.0 recovery protocol group if the specified delivery mode is not supported by the receiving group. Example, DM_CONF delivery mode is only supported by version 3.x and up, but is not supported by version 2.1 groups.
User Action: Either upgrade the receiving group to a current version of the MessageQ software, or modified the delivery mode in the application code.

JRN_E_INVRP, Invalid recovery protocol:n for msg (x,x)

Explanation: Error.
MessageQ detected an invalid recovery protocol value in the message header.
User Action: Contact Oracle MessageQ support.

JRN_E_JRNCLS, Error closing Journal file filename

Explanation: Error
An error occurred while the Journal Server was closing a journal file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

JRN_E_JRNERR, Unexpected error in Journal file filename, status=n

Explanation: Error.
An unexpected error was encountered by the Journal Server in accessing the journal file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

JRN_E_JRNMSGTOOBIG, Journal record is too large for Journal file

Explanation: Error.
Message is too large to fit into the journal file.
User Action: Increase the AREA_SIZE in the MRS section of the group initialization file.

JRN_E_JRNOPN, Error opening Journal file filename

Explanation: Error
An error occurred while the Journal Server was attempting to open a journal file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

JRN_E_JRNTRUNC, Incomplete Journal record detected filename

Explanation: Error
The Journal Server detected an incomplete journal record in the specified file.
User Action: Check the file system and PCJ/DLJ files for disk errors. Use the Manger Utility to dump the contents of the journal file for analysis.

JRN_E_JRNWR, Error writing Journal file filename

Explanation: Error.
MessageQ detected an error when writing to the journal file.
User Action: Check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_AM_D, Attempt to add duplicate msg (x,x) to ML

Explanation: Error.
The MRS Server attempted to add a message to the MRS message list (ML) that was already in the ML. MRS will remove the original message from the ML and the DQF and replace it with the new message.
User Action: None.

MRS_E_AM_S, Message data base full. Increase page file quota.

Explanation: Error.
The MRS Server attempted to add a message to the MRS message list that was full. MRS failed to expand the message list.
User Action: Increase the page file quota for the MRS server in the DMQ$SET_SERVER_LOGICALS.COM file.

MRS_E_AP_S, Queue list full. Increase NUM_QUEUES and page file quota.

Explanation: Error.
The MRS Server attempted to add a queue to the MRS queue list that was full. MRS failed to expand the queue list.
User Action: Increase page file quota for MRS server in the
DMQ$SET_SERVER_LOGICALS.COM file and increase the NUM_QUEUES parameter in the group initialization file (DMQ$INIT.TXT).

MRS_E_BADJRNP, g.q sent invalid confirm mode: n

Explanation: Error.
Invalid parameter passed into the pams_confirm_msg force journal field. Valid values are PDEL_DEFAULT_JRN, PDEL_FORCE_JRN and PDEL_NO_JRN
User Action: Recheck application code and documentation.

MRS_E_BADLOGIC, UNEXPECTED ERROR error_text

Explanation: Error.
An unexpected code path or condition occurred. The text of the message will provide further information.
User Action: Contact Oracle support for more information.

MRS_E_CIOERR, C I/O error_text : file: filename

Explanation: Error.
An error was returned by C language I/O support. The text of the message will provide further information.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_CNF_P, Attempt by b.g to confirm unk. msg (x,x)

Explanation: Error.
The message sequence number parameter supplied to the pams_confirm_msg function call is not in the MRS Server message list. Message has either already been confirmed or the message sequence number is invalid.
User Action: Correct the programming error in the application program that calls pams_confirm_msg.

MRS_E_CHKPTREQFAIL, Checkpoint file operation request failed

Explanation: Error.
A failure occurred while attempting to open the checkpoint file.
User Action: Check other error messages logged. The checkpoint file is probably locked by another user.

MRS_E_CHN, %RMS-F-CHN, Assign channel system service request failed

Explanation: Error.
MessageQ detected an error when attempting to create a journal file. No more I/O channels available.
User Action: Check the system channel count and increase the size of the journal files to decrease the number of dynamic file creations.

MRS_E_CLEANONCLOSE, Journal cleanup on close enabled by logical DMQ$MRS_CLEANUP_ON_CLOSE

Explanation: Informational.
Journal file cleanup (DQF and SAF) on close has been enabled. This allows empty DQF or SAF files to be deleted on closure if they are empty.
User Action: None.

MRS_E_DELDUP, Failed to remove stale msg (x,x) from filename

Explanation: Error.
MessageQ detected an error while attempting to delete a duplicate message from the DQF.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DEQ, Error removing msg (x,x) from DQF

Explanation: Error.
MessageQ detected an error while deleting a message from the DQF.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DQF_ALLOC, Error allocating space for DQF list

Explanation: Fatal.
An attempt to allocate virtual memory by the MRS Server failed. This failure prevented the MRS Server from starting.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_DQFBYPASS, I/O Error caused beeps of DQF file: filename

Explanation: Error.
An I/O error while attempting to access the DQF file has resulted in the file being bypassed. Normally a bypassed DQF file will be renamed with the extension .DERR.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DQFCLS, Error closing DQF file filename

Explanation: Error
An error occurred while MRS was closing a DQF file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DQFDEL, Error deleting DQF file filename, status=x

Explanation: Error.
An error occurred while MRS was attempting to delete an empty DQF file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DQFERR, Unexpected error in DQF file filename

Explanation: Error.
An unexpected error was encountered by MRS in accessing the DQF file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DQF_FILES, DQF_FILES quota exceeded

Explanation: Error
An error occurred while MRS was attempting to create a new DQF file. The maximum number of DQF files has been reached.
User Action: Increase NUM_DQF_AREAS in group initialization file or increase AREA_SIZE to decrease the number of files required.

MRS_E_DQFIDXERR, Unexpected error building DQF list

Explanation: Error
An error occurred while attempting to access the Process List.
User Action: Contact Oracle MessageQ support.

MRS_E_DQFIODEL, IO error prevents use of DQF file filename

Explanation: Error
An error occurred while MRS was attempting a file operation on the DQF file. The file has been renamed with extension .DERR.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DQFMSGDEL, Error Deleting message from DQF file filename

Explanation: Error.
MessageQ detected an error while deleting a message from the DQF.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DQFMSGTOOBIG, DQF message is too large for DQF file filename

Explanation: Error.
Message is too large to fit into the specified DQF file.
User Action: Increase the AREA_SIZE in the MRS section of the group initialization file.

MRS_E_DQFOPN, Error opening DQF file filename, status= n

Explanation: Error
An error occurred while MRS was attempting to open a DQF file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DQFRD, Error reading DQF file filename

Explanation: Error
An error occurred while MRS was attempting to read a DQF file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_DQFTRUNC, Incomplete DQF record detected filename

Explanation: Error
MRS detected an incomplete DQF record. Either a write error resulted in the messages failure to make it to disk, or a delete error resulted in the failure to completely remove the message from disk.
User Action: Check the file system and DQF files for disk errors. Use the Manger Utility to dump the contents of the DQF file for analysis.

MRS_E_DQFW, DQF write error

Explanation: Error.
MessageQ detected an error while writing a message to the DQF.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_EXTENDERR, Journal file filename could not be extended, default AREA_SIZE is too small.

Explanation: Error.
MessageQ failed to extend the journal file.
User Action: Increase AREA_SIZE in group initialization file.

MRS_E_FREE_ALLOC, Error allocating space for FREE file list

Explanation: Fatal.
An attempt to allocate virtual memory by the MRS Server failed. This failure prevented the MRS Server from starting.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_FREECLS, Error closing FREE file

Explanation: Error.
An error occurred while MRS was closing a FREE file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_FREECREATE, Error creating FREE file filename, status=n

Explanation: Error.
An error occurred while attempting to create a FREE file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_FREEDEL, Error deleting FREE file filename, status=n

Explanation: Error.
MessageQ detected an error while attempting to delete a FREE file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_FREE_FILES, FREE_FILES quota exceeded

Explanation: Error.
An error occurred while MRS was attempting to create a new FREE file. The maximum number of FREE files has been reached.
User Action: Increase NUM_DQF_AREAS in group initialization file or increase AREA_SIZE to decrease the number of files required. The number of FREE files is based on the number of DQF files.

MRS_E_INIT, MRS did not initialize properly

Explanation: Error.
The MRS Server did not complete its initialization process.
User Action: Check EVL and MRS server logs for errors.

MRS_E_INVGRP, Invalid recovery protocol:n for group: g

Explanation: Error.
The MRS Server encountered an invalid recovery protocol for the specified group.
User Action: Contact Oracle MessageQ support.

MRS_E_INVPS, Invalid process state in module module_name process_state

Explanation: Error.
The MRS Server encountered an invalid process state in the specified module.
User Action: Contact Oracle MessageQ support.

MRS_E_INVRP, Invalid recovery protocol:n for msg (x,x)

Explanation: Error.
The MRS Server encountered an invalid recovery protocol for the specified message.
User Action: Contact Oracle MessageQ support.

MRS_E_JRNFAIL, Error fetching (x,x) from DQF prior to PCJ

Explanation: Error.
An I/O error occurred while MessageQ was retrieving a message from the DQF in response to a pams_confirm_msg call.
User Action: Check disk quotas. Check the file system and DQF files for disk errors.

MRS_E_LATECONF, Late confirm from b.g for (x,x); value x

Explanation: Error.
This messages is only seen on MRS servers that are talking 1.0 recovery protocol. It is an indication that the MRS server received and ENQ_STATUS_MSG for a message that was no longer on the ML. This is an indication that the user timed out before the message was successfully enqueued to the target MRS server.
User Action: Increase the timeout parameter to pams_put_msg.

MRS_E_LRGBUFTOOSMALL, Message in filename is larger (n bytes) than the LARGE buffer size configured for this group (n bytes)

Explanation: Error.
The MRS Server is attempting to process a message that is too large for the internal buffer sizes. This may occur if some large messages were stored in a journal file and then the maximum group message sizes were lowered and the group restarted. MRS cannot process the messages that are stored in the journal file because they are too large for the current buffer.
User Action: Increase the GROUP_MAX_MESSAGE_SIZE in the group initialization file and restart the group. If that does not fix the problem then contact Oracle MessageQ support.

MRS_E_MALLOC, Memory allocation failed

Explanation: Error.
The MRS Server was unable to allocate virtual memory.
User Action: Increase the MRS servers page file quotas in
DMQ$SET_SERVER_QUOTAS.COM

MRS_F_MALLOC, Memory allocation failed

Explanation: Fatal.
The MRS Server was unable to allocate virtual memory.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_ML_ADD, Could not add message to ML list

Explanation: Error.
MessageQ was unable to add messages to the message list.
User Action: This message will be accompanied by other error messages that will indicate the specific resource allocation failure.

MRS_E_ML_ALLOC, ML memory alloc failed

Explanation: Fatal.
An attempt to allocate virtual memory by the MRS Server failed. This failure prevented the MRS server from starting.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_MLAGE, Msg (x,x) to b.g stuck on ML

Explanation: Error.
The MRS Server encountered an internal MRS error.
User Action: Contact Oracle MessageQ support.

MRS_E_MLNF, Message (x,x) not ML

Explanation: Error.
The MRS Server code not locate the message on the message list.
User Action: Contact Oracle MessageQ support if the problem does not correct itself.

MRS_E_MSGERR, Cant send msg (x,x) b.g to b.g, len:n

Explanation: Error.
The MRS Server encountered an error while attempting to send a message. The text of message will indicate the error. If the error is PAMS_REMQUEFAIL, the queuing resources of the group were exceeded or insufficient global memory buffers were found to contain a particular message request.
User Action: Increase the buffer pool space for the group or modify the sender program to manage message flow control.

MRS_E_MSGTOOBIG, Message exceeds maximum allowed size

Explanation: Error.
The MRS Server is attempting to process a message that is too large for the internal buffer sizes. This may occur if some large messages were stored in a journal file and then the maximum group message sizes were lowered and the group restarted. MRS cannot process the messages that are stored in the journal file because they are too large for the current buffer.
User Action: Increase the GROUP_MAX_MESSAGE_SIZE in the group initialization file and restart the group. If that does not fix the problem then contact Oracle MessageQ support.

MRS_E_NOMEM, Memory allocation failure during file I/O

Explanation: Error.
An attempt to allocate virtual memory by the MRS Server failed.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_NORETAIN, Message not retained in holdaside buffer

Explanation: Error.
An error prevented the allocation of an internal buffer to hold the message aside for a timed retry.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_NTA, MRS notify alloc failed

Explanation: Error.
An attempt to reallocate a message buffer failed.
User Action: Contact Oracle MessageQ support.

MRS_E_PAMS_SEND, Error sending msg to (b.g) class:n type:n

Explanation: Error.
The MRS Server encountered an error while attempting to send a message. The text of message will indicate the specific error. If the error is PAMS_REMQUEFAIL, the queuing capacity of the group was exceeded or insufficient global memory buffers were found to contain a particular message request..
User Action: Increase the buffer pool space or modify the sender program to manage message flow control.

MRS_E_PCJFAIL, Error writing (x,x) to PCJ

Explanation: Error.
Message failed to be written to the PCJ file.
User Action: Verify that the Journal Server is running. Check EVL and JRN server logs for errors. Verify that ENABLE_JRN parameter is set to YES in the group initialization file.

MRS_E_PL_ALLOC, PL memory alloc failed

Explanation: Fatal.
An attempt to allocate virtual memory by the MRS Server failed. This failure prevented the MRS Server from starting.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_PLEV, PL entry vanished

Explanation: Error.
Process entry is not in the process list. This is an unexpected error.
User Action: Contact Oracle MessageQ support.

MRS_E_PL_MISMATCH, Unexpected PL_idx for b.g found: n, expected:n

Explanation: Error.
The MRS Server detected an internal PL index mismatch.
User Action: Contact Oracle MessageQ support.

MRS_E_RB_ALLOC, Ring Buffer memory alloc failed

Explanation: Error.
An attempt to allocate virtual memory by the MRS Server failed.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_RCV, PAMS receive error

Explanation: Error.
The MRS Server encountered an error while attempting to read a message from the MRS server queue. If the error is PAMS__EXHAUSTBLKS, the queuing capacity of the group has been exceeded.
User Action: Increase the MRS servers pool quotas and check the MRS servers page file quotas in DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_RDQFD, Error posting READ_DQF_D for b.g

Explanation: Error.
The MRS Server failed to post the READ_DQF_D message for the specified group.
User Action: None. The MRS Server will retry again later.

MRS_E_RENAME, Failed to rename file from filename to filename

Explanation: Error.
The MRS failed to rename a journal file. This is a C I/O error.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_RMA, MRS reply alloc failed

Explanation: Error.
An attempt to reallocate a message buffer failed.
User Action: Contact Oracle MessageQ support.

MRS_E_RMS, File system error: error_text

Explanation: Error.
An RMS I/O call returned an error. The text of the message will provide further information.
User Action: Depending upon text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_RSLOW, s restart activity timeout for b.g

Explanation: Error.
A timeout occurred while attempting to restart either DQF or SAF processing. May be caused be a slow network link or large traffic volume.
User Action: Contact Oracle MessageQ support if the problem does not correct itself.

MRS_E_SAF_ALLOC, Error allocating space for SAF list

Explanation: Fatal.
An attempt to allocate virtual memory by the MRS Server failed. This failure prevented the MRS Server from starting.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_SAFBYPASS, I/O Error caused beeps of SAF file: filename

Explanation: Error.
An error occurred while the MRS Server was processing a SAF file. The file was renamed with the extension .SERR and bypassed.
User Action: Check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_SAFCLS, Error closing SAF file filename

Explanation: Error
An error occurred while MRS was closing a SAF file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_SAFDEL, Error deleting SAF file filename, status=n

Explanation: Error.
An error occurred while MRS was attempting to delete an empty SAF file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_SAFD_S, Error broadcasting SAFD_START for b.g

Explanation: Error.
The MRS Server failed to broadcast the SAFD_START message to the specified group.
User Action: None. The MRS Server will retry again later.

MRS_E_SAFERR, Unexpected error in SAF file filename

Explanation: Error.
MessageQ encountered a severe error when reading the specified SAF file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_SAF_FILES, SAF_FILES quota exceeded

Explanation: Error
An error occurred while MRS was attempting to create a new SAF file. The maximum number of SAF files has been reached.
User Action: Increase NUM_SAF_AREAS in group initialization file or increase AREA_SIZE to decrease the number of files required.

MRS_E_SAFIDXERR, Unexpected error building SAF list

Explanation: Error
An error occurred while attempting to access the Process List (PL).
User Action: Contact Oracle MessageQ support.

MRS_E_SAFIODEL, IO error prevents use of SAF file filename

Explanation: Error.
An error occurred while MRS was attempting a file operation on the SAF file. The file has been renamed with extension .SERR.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_SAFMSGDEL, Error Deleting message from SAF file filename

Explanation: Error.
MessageQ detected an error while deleting a message from the SAF.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_SAFMSGTOOBIG, SAF message is too large for SAF file filename

Explanation: Error.
Message is too large to fit into the specified SAF file.
User Action: Increase the AREA_SIZE in the MRS section of the group initialization file.

MRS_E_SAFOPN, Error opening SAF file filename, status= n

Explanation: Error.
MessageQ detected an error when opening a SAF file.
User Action: Check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_SAFRD, Error reading SAF file filename

Explanation: Error.
MessageQ detected an error when reading a SAF file.
User Action: Check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_SAFTRUNC, Incomplete SAF record detected filename

Explanation: Error.
MessageQ has detected an incomplete record in the SAF file.
User Action: Check file system integrity.

MRS_E_SAFWR, Error writing SAF file filename

Explanation: Error.
MessageQ detected an error when writing to the SAF file.
User Action: Check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_SLIST, Unexpected error in list handling

Explanation: Error.
MessageQ detected an unexpected error.
User Action: Check page file quotas and contact Oracle MessageQ support.

MRS_E_SPR_S, Error posting PAMS timer

Explanation: Error.
The MRS received an error status return code on a call to pams_set_timer.
User Action: Contact Oracle MessageQ support.

MRS_E_SYNCCREATE, Error creating Journal file filename, status=n

Explanation: Error.
An error occurred while attempting to create a Journal file.
User Action: Depending upon the text of message, check disk quotas, open file limits, file system integrity, file protections, and ownership.

MRS_E_TIMERFAIL, Error occurred while queuing a timer

Explanation: Error.
MessageQ detected an error when queuing a timer.
User Action: Increase the ASTLM or TQELM quota for the MRS Server process in DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_TL_ALLOC, Error allocating space for TL list

Explanation: Fatal.
An attempt to allocate virtual memory by the MRS Server failed. This failure prevented the MRS Server from starting.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.

MRS_E_TMOERR, Unexpected condition in timeout handling

Explanation: Error.
An unexpected error occurred in the MRS timer handling services.
User Action: Contact Oracle MessageQ support.

MRS_E_UNKMSG, Received an Unknown MRS msg
+ Discarded msg - Src=b.g Tgt=b.g Class=n Type=n + Org-Src=b.g Org-Tgt=b.g Size=n Seq=x:x

Explanation: Error.
An unexpected message was received by the MRS Server, which usually indicates an application program error. A program might have attempted a dialogue with the MRS Server.
User Action: Determine the source of the message and modify the application program.

MRS_I_DQFFILE, file:filename start:start_record end:end_record

Explanation: Informational.
DQF file information which usually coincides with an MRS error message.
User Action: None.

MRS_I_DQFSIZE, Max DQF areas:n, maximum size:n pages

Explanation: Informational.
Reflects the AREA_SIZE and NUM_DQF_FILES in pages.
User Action: None.

MRS_I_FREEENGOFF, Shutting off FREE file engine

Explanation: Informational.
All DMQ$MRS: devices are full or there are no more I/O channels available. Shutting off FREE file engine.
User Action: Free disk space on DMQ$MRS devices, or add another device to the DMQ$MRS list, or increase system channel count, or drain the existing journal files to free space.

MRS_I_FREEENGON, Restarting FREE file engine

Explanation: Informational.
The FREE file engine is being restarted by the MRS server.
User Action: None.

MRS_I_GRP_NONE, Assuming default 1.0 recovery protocol for group:g

Explanation: Informational.
Recovery protocol for group is not known. Assuming 1.0 recovery protocol.
User Action: None.

MRS_I_INFO, information_text

Explanation: Informational.
MRS tracing information.
User Action: None.

MRS_I_JRNCLOSED, s journaling disabled for queue (b.g)

Explanation: Informational.
SAF or DQF journaling was disabled by either a SAF_SET_CLOSE or a DQF_SET_CLOSE request.
User Action: None.

MRS_I_JRNDISBYLOG, s journaling disabled by logical logical_name

Explanation: Informational.
User Action: None.

MRS_I_JRNDISBYMSG, s journaling disabled by message message_type, from (b.g)

Explanation: Informational.
User Action: None.

MRS_I_JRNENABYMSG, s journaling enabled by message message_type, from (b.g)

Explanation: Informational.
User Action: None.

MRS_I_JRNOPENED, s journaling enabled for queue (b.g)

Explanation: Informational.
SAF or DQF journaling was enabled by either a SAF_SET_OPEN or a DQF_SET_OPEN request.
User Action: None.

MRS_I_JRNSETREFUSED, message_type message from (b.g) is refused

Explanation: Informational.
A journal control message was refused.
User Action: None.

MRS_I_ML_EXPAND, NUM_MESSAGES expanded to n entries

Explanation: Informational.
The message list, called the ML, has been expanded in order to handle a peak load that is greater than its current size.
User Action: Although this is an informational message, a user may wish to set the initial message list size large enough to store peak requirements and for efficient MRS Server operation. This can be controlled by the NUM_MESSAGES parameter in the group initialization file (DMQ$INIT.TXT). Set it to at least the peak value reported by log event.

MRS_I_MLSIZE, Space allotted for n queues, n messages

Explanation: Informational.
MRS Server is reporting the allocated message list size which is based on the number of queues and number of messages as specified in the group initialization file.
User Action: None.

MRS_I_PL_EXPAND, NUM_QUEUES expanded to n entries

Explanation: Informational.
The queue list, called the PL, has been expanded in order to handle a peak load that is greater than its current size.
User Action: Although this is an informational message, a user may wish to set the initial queue list size large enough to store peak requirements and for efficient MRS Server operation. This can be controlled by the NUM_QUEUES parameter in the group initialization file (DMQ$INIT.TXT). Set it to at least the peak value reported by log event.

MRS_I_RESTART, Group:g Placed on restart list from state= server_state

Explanation: Informational.
User Action: None.

MRS_I_RESTARTING, Attempting to restart group:g

Explanation: Informational.
The MRS server is attempting a handshake with the specified group's MRS server.
User Action: None.

MRS_I_RESTART_OFF, Removing group:g from restart list to state=server_state

Explanation: Informational.
User Action: None.

MRS_I_RP, Group:g Using recovery protocol:n

Explanation: Informational.
User Action: None.

MRS_I_RP_NONE, Assuming default 1.0 recovery protocol for msg (x,x)

Explanation: Informational.
Recovery protocol for message is not known. Assuming 1.0 recovery protocol.
User Action: None.

MRS_I_SAFFILE, file:filename start:start_record end:end_record

Explanation: Informational.
SAF file information which usually coincides with an MRS error message.
User Action: None.

MRS_I_SAFSIZE, Max SAF areas:n, maximum size:n pages

Explanation: Informational.
Reflects the AREA_SIZE and NUM_SAF_FILES in pages.
User Action: None.

MRS_I_STACK, MRS Server initialized

Explanation: Informational.
User Action: None.

MRS_I_START, MRS Server version Starting

Explanation: Informational.
User Action: None.

MRS_I_TOPO_EXPAND, MRS expanded group topology to n groups

Explanation: Informational.
The group topology list, called the TOPO, has been expanded in order to handle a peak load that is greater than its current size (the default is 128 groups).
User Action: None.

MRS_I_XGRPJRNCTRL, XGRP_JRN_CTRL is set to NO

Explanation: Informational.
A journal control request message was received from a remote group and was rejected because XGRP_JRN_CTRL in the MRS section of the group initialization file is set to NO.
User Action: To allow journal control messages from remote groups set the XGRP_JRN_CTRL parameter in the MRS section of the group initialization file to YES.

SBS Error Log Messages

This section lists and describes SBS Server error log messages. Use the following Key to understand conventions used in this section:

Key:

• g = group ID decimal value

• q = queue number decimal value

• n = numeric value

• x = hexadecimal value

• s = string

E_IO_ERROR: on channel (g.q), iosb[0]:0Xx, iosb[1]:0Xx

Explanation: Error.
The SBS Server detected an Ethernet I/O error.
User Action: Check the hardware and network error counts on the Ethernet device.

E_IO_RESTART: on channel (g.q), restart code:n

Explanation: Informational.
The SBS Server is attempting to restart the protocol on an ethernet logical link after an automatic LAN shutdown.
User Action: None.

Ethernet Error:%s on channel:(g.q)

Explanation: Error.
The SBS Server detected an Ethernet Error.
User Action: Check the hardware and network error counts on the Ethernet device.

Ethernet MOT Declaration n --- Received sequence gap on Channel n from Group g Received 0Xx Expected 0Xx

Explanation: Warning.
The queuing capacity of the system has been exceeded.
User Action: The sender program should slow the message send rate.

Ethernet received sequence gap on channel n from group n Received 0Xx Expected 0Xx

Explanation: Warning.
The SBS Server detected an Ethernet sequence gap.
User Action: The queuing capacity of the system has been exceeded. The sender program should slow the message send rate.

Ethernet MOT Declaration n - Received sequence gap on channel n from group g
Received 0Xx, expected 0Xx

Explanation: Warning.
The SBS Server detected a sequence gap in the MOT declaration.
User Action: The queuing capacity of the system has been exceeded. The sender program should slow the message send rate.

Group record not found for group: n

Explanation: Warning.
The SBS Server cannot locate the group in the group table.
User Action: Contact Oracle MessageQ support.

*** Failed to initialize SBS Server ***

Explanation: Fatal.
The SBS Server was not able to initialize.
User Action: Check the SBS Server and EVL log files for related errors. Also check the SBS Server's page file quotas.

Failure to locate Registration AVAIL target_q 'g.q' Distribution_Q 'g.q'

Explanation: Warning.
The SBS Server cannot locate the specified AVAIL registration in its database.
User Action: Modify the sender program to use the correct information in the AVAIL_DEREG message.

Failure to locate Registration in SBS_DEREG_BY_ID reg_id = 'n' source = 'g.q'

Explanation: Warning.
The SBS Server cannot locate the specified SBS registration ID in its database.
User Action: Modify the sender program to use the correct registration ID.

Failure to locate Registration SBS_DEREG MOT 'n' dist_q:g.q source:g.q

Explanation: Warning.
The SBS Server cannot locate the specified SBS registration ID in its database.
User Action: Modify the sender program to use the correct registration ID.

Failure to locate Registration SBS_DEREGISTER MOT 'n'
Distribution 'g.q'
source = 'g.q'

Explanation: Warning.
The SBS Server cannot locate the specified SBS registration ID in its database.
User Action: Modify the sender program to use the correct registration ID.

Invalid CLASS = 'n' target = SBS_SERVER type = 'n' source = 'g.q'

Explanation: Warning.
Usually occurs when the application program attempts a dialogue with SBS Server and uses the incorrect message class field.
User Action: Modify the sender application program.

Invalid distribution in MOT_REG_EZ
nlow = 'g.q'
nhigh = 'g.q'
nsource = 'g.q'

Explanation: Warning.
The SBS server detected an invalid distribution address.
User Action: Correct the application code.

Invalid Ethernet Address Specified 's' for channel = 'n'

Explanation: Fatal.
The SBS Server detected an invalid Ethernet address.
User Action: Edit the group initialization file and correct the multicast assignments SBS section.

Invalid Ethernet Protocol Specified 's' for channel = 'n'

Explanation: Fatal.
The SBS Server detected an invalid Ethernet control channel protocol.
User Action: Edit the group initialization file and correct the control channel protocol assignments in SBS section.

Invalid ethernet ucb start msg length

Explanation: Error.
The SBS Server detected an invalid Ethernet UCB control message.
User Action: Contact Oracle MessageQ support.

Invalid group in distribution in MOT_REG_EZ
nlow = 0xx
nhigh = 0xx
nsource = 'b.g'

Explanation: Warning.
The SBS server detected an invalid distribution group.
User Action: Correct the application code.

Invalid MOT Address = 'n' from 'g.q'

Explanation: Warning.
The application program used an invalid Multipoint Outbound Target (MOT) address.
User Action: Modify the sender program to use a broadcast address within the legal MOT range.

Invalid MOT Address range request from 'g.q'

Explanation: Warning.
The SBS Server detected an invalid MOT range in an SBSE_STATUS_REQ message.
User Action: Modify the application program to use a valid MOT range.

Invalid MOT Range in MOT_REG_EZ
low = 'n'
high = 'n'
source = 'g.q'

Explanation: Warning.
The SBS Server detected an invalid MOT range in a MOT_REG_EZ message.
User Action: Modify the sender program to use a broadcast address within the legal MOT range.

Invalid mot_count:%d in SBS_CS_IMSG command. LOAD ignored

Explanation: Warning.
The SBS Server detected an invalid mot count in an SBS_CS_IMSG LOAD command.
User Action: Contact Oracle MessageQ support.

Invalid registration in SBS_DEREG_BY_ID
reg_id = 'n' source = 'g.q'

Explanation: Warning.
The SBS Server cannot locate the specified registration ID in its database.
User Action: Modify the sender program to use the correct registration ID.

Invalid version number in message_type message
version = 'n'
source = 'g.q'

Explanation: Warning.
The SBS Server detected an invalid message version number in the specified message.
User Action: Modify the sender program to use the correct message version number.

Invalid version number n in message_type

Explanation: Warning.
The SBS Server detected an invalid version number in the specified message.
User Action: Modify the application program to use the correct message version number.

Invalid version number in Event Registration Msg ver=n tgt=g.q

Explanation: Warning.
The SBS Server detected an invalid message version number in the specified message.
User Action: Modify the sender program to use the correct message version number.

LINK_COMPLETE msg from g.q has invalid group g, largest group is g - Message Ignored

Explanation: Warning.
SBS Server detected a message with an LINK_COMPLETE message with for invalid group number.
User Action: Contact Oracle MessageQ support.

LINK_LOST message, from g.q, with invalid group g, largest group is g - Message Ignored

Explanation: Warning.
The SBS Server detected a message with a LINK_LOST message with for an invalid group number.
User Action: Contact Oracle MessageQ support.

MOT Declaration n --- Received sequence gap from group g
Received 0Xx, expected 0Xx

Explanation: Warning.
The SBS Server detected a sequence gap in the MOT declaration.
User Action: The queuing capacity of the system has been exceeded. The sender program should slow the message send rate.

PAMS_FREE_LMSG Failed

Explanation: Warning.
The SBS Server failed to free an internal message buffer.
User Action: Check page file quotas and other system parameters. Look for other errors in the EVL or SBS log that may give a better indication of the source of the problem.

PAMS__MSGUNDEL to group 'g'

Explanation: Warning.
A message was returned to the SBS server because it could not be delivered to the target queue.
User Action: Check cross group links to the specified group and check to see if the SBS Server is still running on specified group.

PAMS_RCV_LMSGW Failed in Main loop

Explanation: Warning or Fatal.
The SBS Server received an error status when attempting to read a message from the SBS Server queue. If the error status was PAMS__BADLOGIC or PAMS__PAMSDOWN then the error is Fatal and the SBS Server will shutdown; otherwise, SBS Server will keep trying.
User Action: Check server and EVL log files for soure of problem. If the problem cannot be determined then contact Oracle MessageQ support.

Received out of range DNA mot:n from:(g.q)

Explanation: Warning.
The SBS Server detected a DNA MOT that was out of range.
User Action: Modify the sender program or increase the MOT range in the group initialization file.

Rexmit request to group g [MOT n; ;seq n;length n;hdr:n]

Explanation: Warning.
A MSG_TYPE_SBSE_REXMIT_REQ message was returned to the SBS server because it could not be delivered to the target groups SBS server.
User Action: Check cross group links to the specified group and check to see if the SBS Server is still running on specified group.

SBS Ethernet MOT 'n' BROADCAST rejected --- no channel ---

Explanation: Error.
The MOT is not assigned to the Ethernet channel and DMQ$ETH_MOT_ONLY logical name = YES
User Action: Add the correct MOT definitions to the the group initialization file.

SBS Ethernet MOT 'n' no Ethernet channel assigned

Explanation: Warning.
MOT not assigned to the Ethernet channel.
User Action: Add the correct MOT definitions to the the group initialization file.

SBS Ethernet MOT 'n' REGISTRATION refused --- no channel ---

Explanation: Warning.
MOT not assigned to the Ethernet channel and DMQ$ETH_MOT_ONLY logical name = YES
User Action: Add the correct MOT definitions to the the group initialization file.

SBS received message with invalid group 'g' largest group:g source:g.q - Message Ignored

Explanation: Warning.
SBS Server detected a message with an invalid source group number.
User Action: Contact Oracle MessageQ support.

SBS Server Initialized

Explanation: Informational.
User Action: None.

SBS Server (version.endian) Starting

Explanation: Informational.
User Action: None.

SBS Received sequence gap from group g
Received 0Xx, expected 0Xx

Explanation: Warning.
The SBS Server detected a sequence gap.
User Action: The queuing capacity of the system has been exceeded. The sender program should slow the message send rate.

SBS_INIT_ACK received message with invalid group 'g' largest group is 'g' source = 'g.q'

Explanation: Warning.
SBS Server detected a message with an SBS_INIT_ACK message with an invalid source group number.
User Action: Contact Oracle MessageQ support.

SBS_INIT_ACK_E received message with invalid group 'g' largest group is 'g' source = 'g.q'

Explanation: Warning.
SBS Server detected a message with an SBS_INIT_ACK_E message with an invalid source group number.
User Action: Contact Oracle MessageQ support.

SBS_INIT_E received message from g.q with invalid group g

Explanation: Warning.
SBS Server detected an SBS_INIT_E message with an invalid group number.
User Action: Contact Oracle MessageQ support.

 

Copyright © 2000 Oracle Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.