|
|
|
|
|
|
Error Log Messages
This appendix provides the following error log information:
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:
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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The DECnet link to a remote COM Server aborted.
User Action: None.
The current DECnet link to a remote COM Server is inaccessible.
User Action: None.
An NCP command to disconnect the link was issued.
User Action: None.
The incoming message was larger than the internal buffer.
User Action: Compare the large buffer sizes of the two groups and adjust.
A DECnet link exit was detected.
User Action: None.
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.
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.
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.
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.
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.
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.
An existing notification request was received.
User Action: None.
An existing notification request was received.
User Action: None.
Process Cleanup list has duplicate entries.
User Action: Contact MessageQ support for more detail on this error.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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 the maximum number of outstanding process cleanup requests.
User Action: Reduce the number of processes requiring cleanup.
The number of requesters of process notification messages exceeds the number in the internal table.
User Action: Reduce the number of requesters.
The number of requesters of queue notification messages exceeds the number in the internal table.
User Action: Reduce the number of requesters.
+ discarded msg --- Src=g.q Target=g.q class=n type=n
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.
+ discarded msg --- Src=g.q Target=g.q class=n type=n
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.
The number of requesters of cross-group notification messages exceeds the number in the internal table.
User Action: Reduce the number of requesters.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
A connection attempt could not be made to the indicated group because the system name does not exist in the applicable network database.
User Action: Change the MessageQ initialization file, or add the entry to the network database to correct the condition.
+ discarded msg --- Src=g.q Target=g.q class=n type=n
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
While attempting to create the Group Name Table global section, MessageQ found that the table already exists.
User Action: None.
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.
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.
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.
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.
An incoming connection was rejected because a link to that group already existed and is owned by another link driver.
User Action: None.
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.
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.
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.
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.
An invalid Queue Notification deregistration request message was received.
User Action: Recheck the request message for validity using script message tracing.
MessageQ detected an invalid setting of the logical DMQ$BUS_GROUP.
User Action: Correct as necessary.
An invalid queue list request message was received.
User Action: Recheck the request message for validity using script message tracing.
A queue notification registration request message was received that was invalid.
User Action: Recheck the request message for validity using script message tracing.
+ discarded msg - Src=g.q Target=g.q class=n type=n
The indicated server received a message of a class and type that it does not recognize.
User Action: Correct as necessary.
Local group number is out of range.
User Action: Correct as necessary.
A non local process attempted to attach a temporary secondary queue.
User Action: Correct as necessary.
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.
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.
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.
The link driver has terminated execution.
User Action: Examine the previous messages, and the log file, for more information concerning the action.
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.
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
A non local load complete message was received.
User Action: Correct as necessary.
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.
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.
Identifies the system and transport address of the link driver starting up.
User Action: None.
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.
Maximum DECnet system name is 6 characters.
User Action: Modify the group initialization file and restart the group.
The format of the DMQ$SET_GBLSEC_PROT logical name is invalid.
User Action: Correct as necessary.
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.
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.
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.
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.
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.
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.
+ discarded msg --- Src=g.q Target=g.q class=n type=n
MessageQ could not deliver the message to its destination queue. The UMA will be taken.
User Action: Correct as necessary.
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.
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.
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.
+ discarded msg --- Src=g.q Target=g.q class=n type=n
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.
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.
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.
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.
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.
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.
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.
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.
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.
The connection attempt was rejected because a request for group ownership transfer was denied by the server at the indicated address.
User Action: None.
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.
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).
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.
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.
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.
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.
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.
The connection request received from the indicated system was rejected because the connection is already in progress.
User Action: None.
The connection request received from the indicated system was rejected because the connection is currently in progress.
User Action: None.
The connection request received from the indicated system was rejected because the connection is still in progress.
User Action: None.
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.
A connection request was received from the indicated system for a group that is already connected (possibly to a different transport).
User Action: None.
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.
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.
The connect request is ignored because either the link driver, the network, or the system is shutting down.
User Action: Correct as necessary.
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.
The connection request received from the indicated system was rejected due to a different transport currently owning the group.
User Action: None.
The connection request received from the indicated system was rejected because the read link is currently in transition.
User Action: None.
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.
A connection attempt was received from a system running a MessageQ release that is incompatible with the link driver.
User Action: None.
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.
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:.
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.
A connect attempt to the indicated group was not possible or not supported.
User Action: None.
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.
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.
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.
The specified server has been spawned by the COM server.
User Action: None.
The link driver or server specified has successfully started running.
User Action: None.
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.
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 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.
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.
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.
The transport address does not match the address in the xgroup entry table and XGROUP_VERIFY is YES.
User Action: Correct as necessary.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
+ discarded msg - Src=g.q Target=g.q class=n type=n
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.
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.