|
|
|
|
|
|
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.
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.
+ Discarded msg --- Src=g.q Target=g.q class=n type=n
A cross-group connection request between the listed groups failed.
User Action: None.
+ Message lost - protocol translation or UMA failure
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.
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:
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.
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.
The Journal Server did not complete its initialization process.
User Action: Check EVL and JRN server logs for errors.
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.
MessageQ detected an invalid recovery protocol value in the message header.
User Action: Contact BEA MessageQ support.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
An unexpected code path or condition occurred. The text of the message will provide further information.
User Action: Contact BEA support for more information.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
An error occurred while attempting to access the Process List.
User Action: Contact BEA MessageQ support.
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.
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.
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.
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.
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 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.
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.
MessageQ failed to extend the journal file.
User Action: Increase AREA_SIZE in group initialization file.
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.
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.
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.
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.
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.
The MRS Server did not complete its initialization process.
User Action: Check EVL and MRS server logs for errors.
The MRS Server encountered an invalid recovery protocol for the specified group.
User Action: Contact BEA MessageQ support.
The MRS Server encountered an invalid process state in the specified module.
User Action: Contact BEA MessageQ support.
The MRS Server encountered an invalid recovery protocol for the specified message.
User Action: Contact BEA MessageQ support.
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.
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.
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 BEA MessageQ support.
The MRS Server was unable to allocate virtual memory.
User Action: Increase the MRS servers page file quotas in
DMQ$SET_SERVER_QUOTAS.COM
The MRS Server was unable to allocate virtual memory.
User Action: Increase the MRS servers page file quota in
DMQ$SET_SERVER_QUOTAS.COM.
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.
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.
The MRS Server encountered an internal MRS error.
User Action: Contact BEA MessageQ support.
The MRS Server code not locate the message on the message list.
User Action: Contact BEA MessageQ support if the problem does not correct itself.
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.
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 BEA MessageQ support.
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.
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.
An attempt to reallocate a message buffer failed.
User Action: Contact BEA MessageQ support.
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.
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.
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.
Process entry is not in the process list. This is an unexpected error.
User Action: Contact BEA MessageQ support.
The MRS Server detected an internal PL index mismatch.
User Action: Contact BEA MessageQ support.
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.
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.
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.
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.
An attempt to reallocate a message buffer failed.
User Action: Contact BEA MessageQ support.
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.
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 BEA MessageQ support if the problem does not correct itself.
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.
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.
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.
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.
The MRS Server failed to broadcast the SAFD_START message to the specified group.
User Action: None. The MRS Server will retry again later.
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.
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.
An error occurred while attempting to access the Process List (PL).
User Action: Contact BEA MessageQ support.
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.
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.
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.
MessageQ detected an error when opening a SAF file.
User Action: Check disk quotas, open file limits, file system integrity, file protections, and ownership.
MessageQ detected an error when reading a SAF file.
User Action: Check disk quotas, open file limits, file system integrity, file protections, and ownership.
MessageQ has detected an incomplete record in the SAF file.
User Action: Check file system integrity.
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.
MessageQ detected an unexpected error.
User Action: Check page file quotas and contact BEA MessageQ support.
The MRS received an error status return code on a call to pams_set_timer.
User Action: Contact BEA MessageQ support.
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.
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.
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.
An unexpected error occurred in the MRS timer handling services.
User Action: Contact BEA MessageQ support.
+ 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
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.
DQF file information which usually coincides with an MRS error message.
User Action: None.
Reflects the AREA_SIZE and NUM_DQF_FILES in pages.
User Action: None.
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.
The FREE file engine is being restarted by the MRS server.
User Action: None.
Recovery protocol for group is not known. Assuming 1.0 recovery protocol.
User Action: None.
MRS tracing information.
User Action: None.
SAF or DQF journaling was disabled by either a SAF_SET_CLOSE or a DQF_SET_CLOSE request.
User Action: None.
User Action: None.
User Action: None.
User Action: None.
SAF or DQF journaling was enabled by either a SAF_SET_OPEN or a DQF_SET_OPEN request.
User Action: None.
A journal control message was refused.
User Action: None.
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 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.
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.
User Action: None.
The MRS server is attempting a handshake with the specified group's MRS server.
User Action: None.
User Action: None.
User Action: None.
Recovery protocol for message is not known. Assuming 1.0 recovery protocol.
User Action: None.
SAF file information which usually coincides with an MRS error message.
User Action: None.
Reflects the AREA_SIZE and NUM_SAF_FILES in pages.
User Action: None.
User Action: None.
User Action: None.
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.
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:
The SBS Server detected an Ethernet I/O error.
User Action: Check the hardware and network error counts on the Ethernet device.
The SBS Server is attempting to restart the protocol on an ethernet logical link after an automatic LAN shutdown.
User Action: None.
The SBS Server detected an Ethernet Error.
User Action: Check the hardware and network error counts on the Ethernet device.
The queuing capacity of the system has been exceeded.
User Action: The sender program should slow the message send rate.
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.
Received 0Xx, expected 0Xx
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.
The SBS Server cannot locate the group in the group table.
User Action: Contact BEA MessageQ support.
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.
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.
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.
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.
Distribution 'g.q'
source = 'g.q'
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.
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.
nlow = 'g.q'
nhigh = 'g.q'
nsource = 'g.q'
The SBS server detected an invalid distribution address.
User Action: Correct the application code.
The SBS Server detected an invalid Ethernet address.
User Action: Edit the group initialization file and correct the multicast assignments SBS section.
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.
The SBS Server detected an invalid Ethernet UCB control message.
User Action: Contact BEA MessageQ support.
nlow = 0xx
nhigh = 0xx
nsource = 'b.g'
The SBS server detected an invalid distribution group.
User Action: Correct the application code.
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.
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.
low = 'n'
high = 'n'
source = 'g.q'
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.
The SBS Server detected an invalid mot count in an SBS_CS_IMSG LOAD command.
User Action: Contact BEA MessageQ support.
reg_id = 'n' source = 'g.q'
The SBS Server cannot locate the specified registration ID in its database.
User Action: Modify the sender program to use the correct registration ID.
version = 'n'
source = 'g.q'
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.
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.
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.
SBS Server detected a message with an LINK_COMPLETE message with for invalid group number.
User Action: Contact BEA MessageQ support.
The SBS Server detected a message with a LINK_LOST message with for an invalid group number.
User Action: Contact BEA MessageQ support.
Received 0Xx, expected 0Xx
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.
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.
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.
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 BEA MessageQ support.
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.
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.
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.
MOT not assigned to the Ethernet channel.
User Action: Add the correct MOT definitions to the the group initialization file.
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 Server detected a message with an invalid source group number.
User Action: Contact BEA MessageQ support.
User Action: None.
User Action: None.
Received 0Xx, expected 0Xx
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 Server detected a message with an SBS_INIT_ACK message with an invalid source group number.
User Action: Contact BEA MessageQ support.
SBS Server detected a message with an SBS_INIT_ACK_E message with an invalid source group number.
User Action: Contact BEA MessageQ support.
SBS Server detected an SBS_INIT_E message with an invalid group number.
User Action: Contact BEA MessageQ support.
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|