BEA MessageQ Installation and Configuration Guide for OpenVMS

BEA MessageQ
Installation and Configuration Guide for OpenVMS

Previous | Contents

D.2 Logical Names

Table D-2 lists the MessageQ logical names. The second column in the table refers to whether the logical names are dynamically translated when a program attaches its first queue.

Table D-2 MessageQ Logical Names
Logical Name Dynamic Description
DMQ$ACCESS¹ . Directory specification of MessageQ access control files.
DMQ$BLOCKING_CONFIRM¹ . Controls whether or not the PAMS_CONFIRM_MSG routine waits for a response from the recovery system.
DMQ$CHKPT_FILE¹ . File specification of a file that counts the number of times the COM Server has been booted. Generates unique sequence numbers.
DMQ$BUS_GROUP¹ Y Contains the current bus ID and group ID.
DMQ$DCL_NUMBER³ Y Base ten number that overrides the queue number submitted to PAMS_ATTACH_Q.
DMQ$DEBUG³ Y Controls the built-in MessageQ debug code:
ERROR = Display only error messages.
TRACE = Trace module calls.
ALL = Display both trace and error messages.
DMQ$DEBUG_MEMORY³ Y Enables tracing of global memory structures. For troubleshooting purposes only.
DMQ$DEBUG_SELECT³ Y Enables trace dumping of the selection list. For troubleshooting purposes only.
DMQ$DEFAULT_SEND_TMO³ Y Overrides the timeout value for the pams_put_msg service.
DMQ$DISABLE_FORCEX³ Y Controls whether the COM Server forces all processes that are attached to the COM Server to exit along with it. The default is NO.
YES = COM Server does not perform the forced exit.
DMQ$DISABLE_SYSOUT³ Y Controls whether MessageQ logs events to SYS$OUTPUT.
YES = Printing disabled.
DMQ$DISK¹ . Device specification of the disk where MessageQ is installed.
DMQ$DOC¹ . Directory specification of MessageQ documentation.
DMQ$DNS_DIRECTORY³ . Default DNS namespace and specification used by various MessageQ routines.
DMQ$ENTRYRTL¹ . File specification of the installed MessageQ run-time library DMQ$ENTRYRTLV nn.EXE.
DMQ$ERROUT² Y Device specification of the alternate MessageQ console device. If not specified, MessageQ messages are printed on the system console.
DMQ$EXAMPLES¹ . Directory specification of MessageQ example programs.
DMQ$EXE¹ . Directory specification of MessageQ executable modules.
DMQ$EXECRTL¹ . File specification of the installed EXEC mode MessageQ routines in EXECRTLV nn.EXE.
DMQ$EXIT_PURGE³ Y Controls the purging of pending LLS messages when the process exits.
NO = do not purge messages.
DMQ$GMT_OFFSET³ Y The time difference in hours between local system time and Greenwich Mean Time (GMT). The value of this logical name must be set for TCP/IP network communications.
DMQ$GROUP_SYNCHRONIZE 4 . Enables automatic synchronized cluster group failover. Setting this to NO will require that failover be managed by the user. The default is YES.
DMQ$HEADERS³ Y Controls the printing of MessageQ message headers on the user's terminal.
YES = print message headers.
DMQ$INIT_FILE¹ . File specification of the MessageQ initialization file.
DMQ$LIB¹ . Directory specification of the
MessageQ libraries.
DMQ$LOG¹ . Directory specification of the
MessageQ user area.
DMQ$MRS¹ . Directory specification for the MRS data files.
DMQ$MRS_CHECK_ML 5 . Enables MRS validation scan of the internal MRS message list. For troubleshooting purposes only.
DMQ$MRS_CHECK_PL 5 . Enables MRS validation scan of the internal MRS process list. For troubleshooting purposes only.
DMQ$MRS_CHUNK_SIZE 4 . Controls the journaling chunk size for DQF and SAF journals.
DMQ$MRS_CLEANUP_ON_CLOSE 5 . Enables MRS to delete a DQF or SAF journal file on close if the file is empty.
DMQ$MRS_DISABLE_JOURNALING 4 . Disables all journaling. This logical is processed by the COM Server only. Default is NO.
DMQ$MRS_DQF_CONTROL 5 . Disables operation of DQF files unless explicitly requested by a control message.
DMQ$MRS_FREE_FILE_MAX 4 . Limits the number of FREE files that the MRS Server may create during recoverable messaging. The default value is calculated by the MRS Server based on the NUM_DQF_AREAS and NUM_SAF_AREAS (DMQ$INIT.TXT). Cannot be smaller than DMQ$MRS_FREE_FILE_MIN.
DMQ$MRS_FREE_FILE_MIN 4 . Controls the minimum number of FREE files that the MRS Server may use during recoverable messaging. The default value is 10. To turn the Free File Engine OFF, set it to 0.
DMQ$MRS_READ_AHEAD_DEPTH 5 . Controls the read ahead buffer depth. This value can be tuned to increase MRS read I/O performance. The default value is 4. It is not recommended that this value be changed.
DMQ$MRS_RING_DEPTH 5 . Controls the depth of the confirmation ring buffer. The default value is 10.
DMQ$MRS_SAF_CONTROL 5 . Disables operation of SAF files unless explicitly requested by a control message.
DMQ$MRS_SERVER_CHECK_TIMER 5 . Internal time which MRS uses to check the state of adjacent MRS servers. Value is in tenths of seconds with with a valid range of 30 to 3000 seconds (5 minutes). Default is 600 (1 minute).
DMQ$MRS_TRACE_PL 5 . Enables MRS tracing of the internal MRS process list. For troubleshooting purposes only.
DMQ$MRS_TRACE_STATE 5 . Enables MRS tracing of internal MRS state changes. For troubleshooting purposes only.
DMQ$MSGSHR¹ . File specification of the MessageQ message table.
DMQ$OBJECT_CACHE_SIZE³ Y Sets the maximum number of queue names that be stored the PAMS_LOCATE_Q process cache. Valid setting are 20 to 32000. The default value is 128.
DMQ$POOL_CHK_WARNING_INTERVAL 4 . Controls the number of seconds between low buffer pool warning messages. The default is 120 seconds.
DMQ$OPCOM_TARGET² Y Redirects console event logging to OPCOM. See Chapter 13 for a full description.
DMQ$GROUP_OUTPUT³ Y Sets output direction to any of the following file output streams: console, EVL_LOG, USER_LOG, SYSOUT, or SYSERR.
DMQ$PROCESS_OUTPUT³ Y Sets output direction to any of the following file output streams: console, EVL_LOG, USER_LOG, SYSOUT, or SYSERR.
DMQ$TRACE_OUTPUT³ Y Sets output direction to any of the following file output streams: console, EVL_LOG, USER_LOG, SYSOUT, or SYSERR.
DMQ$QTRANSFER_MAX_PROCS 5 . Defines the number of concurrent streams the Qtransfer Server can handle at one time. The default is 5.
DMQ$ROOT¹ . The root directory name of the
MessageQ software being used (for example, DMQVnn).
DMQ$SBS_ETH_MOT_ONLY 5 . Allows only Ethernet broadcasting via the SBS server when set to YES.
The default is NO.
DMQ$SBS_MAX_ASM_Q 5 . Overrides the default number of SBS assembly queues.
The default is 10.
DMQ$SBS_MAX_MSG_SIZE 5 . Overrides the default size of the SBS assembly queue. Can not exceed 32000.
DMQ$SBSE_REXMIT_TIMEOUT 5 . Overrides the default retransmission timer.
The default is 30 seconds.
DMQ$SBSE_mmmm_MAX_HB 5 . Overrides the maximum heartbeat interval for the specified MOT mmmm defined in the group initialization file.
DMQ$SBSE_mmmm_POLL_INT 5 . Overrides the polling interval for the specified MOT mmmm defined in the group initialization file.
DMQ$SCRIPT³ Y Controls script processing. This logical should provide the file specification for the script file. If the script file cannot be found then the user will be prompted for one. A value of 'N' will disable scripts.
DMQ$SYMBOLS³ Y Specifies the type-class file to be loaded for script processing. The default is DMQ$USER:P_TYPECL.H.
DMQ$SET_GBLSEC_PROT² . Overrides the protection mask on the MessageQ global sections.
DMQ$SERVER_TRACE³ Controls the tracing of MessageQ Server-specific information.
YES = Trace on.
This logical generates many trace lines for each message in the server log file.
DMQ$SPAWN_SERVERS² . Suppresses the start of MessageQ servers when it is set to NO.
DMQ$VERIFY_ON³ Y Enables verification of global sections in the DMQ$LLS_VERIFY utility. The default is NO.
DMQ$PRIMARY_DECNET_LD² . Controls which DECnet link driver is the primary driver. The default is 'V2'. Setting this logical to 'V3' will force the DECNETV3 driver to be the primary DECnet link driver and the DECNETV2 (COM Server) driver to be the secondary DECnet link driver.
DMQ$TCPIP_CON_ABORT
DMQ$DECNET_CON_ABORT 5 		. Controls the connection abort timer.
When a link connection is being established, at the beginning of the protocol handshake, the connect abort timer is started. The timer is canceled when the link is successfully established.
The default value is 90 seconds.
DMQ$TCPIP_LD_NAME 5 . Override the default hostname returned by a call to gethostname(). This logical name can be used to define an alternate interface for the linkdriver activity.
DMQLD_TRACE_LEVEL 5 . Defines and overrides the value for LD tracing. This value is a bit mask which is defined as follows:
1 = skinny trace, I/O completions, message processing
2 = dump data from each I/O
4 = full tracing of all routines
DMQLD_PING_TIMEOUT 5 . Defines how long, in seconds, we wait to hear from a V4 group as a result of a ping request.
The default is set to 90 seconds.
DMQLD_PING_INTERVAL 5 . Defines the interval between pings.
The default value is 30 seconds.
DMQLD_MAX_DATAIO_LEN 5 . Defines the maximum number of bytes that will be used on a single write to the link.
The default value is 65534 bytes.
DMQLD_TCP_UNREACH_RETRY 5 . In the case where we have a TCP stack which reports a warning for NETUNREACH or HOSTUNREACH, we offer a retry for the I/O operation. The retry value can be from 1 to 60 attempts.
The default value is 0, NOT to retry.

NOTE: BEA recommends this retry feature be avoided and the customer focus placed on the repair of the network that is generating these up/down transitions between hosts.
DMQLD_TCP_UNREACH_DELAY 5 . Used in conjunction with the DMQLD_TCP_UNREACH_RETRY to vary the delay between retry attempts. This value is not used if DMQLD_TCP_UNREACH_RETRY is not enabled.
The default value is 60 seconds.

¹Set by DMQ$BOOT.COM.
²Optionally set by DMQ$BOOT.COM.
³Optionally set by user at DCL level.
4Set by DMQ$SET_SERVER_LOGICALS.COM.
5Optionally set by DMQ$SET_SERVER_LOGICALS.COM.

Appendix E
Error Log Messages

This appendix provides the following error log information:

E.1 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:

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

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

The message indicates that the connection will be accepted, but under the name "alias_name" instead; to match existing definitions in the MessageQ initialization file and enforce consistency. All further console messages referring to this connection will display the "alias_name" system name, as will the MessageQ Monitor program(s).
User Action: If aliases are being used and both names refer to the same system, no action is necessary.
:

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

Accepting connect from system system_name for group g (group_name)

Explanation: Informational.
The server is accepting a network connection from another server with the indicated group ID. This message appears when a group connection requires two data links, and indicates that the inbound link is up.
User Action: None.
Accepted connect from system system_name for group g (group_name)

Explanation: Informational.
The server has accepted a network connection from another server with the indicated group ID, and the group connection is now available for use.
User Action: None.
An error occurred while freeing messages for process q PID (pid)

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

Explanation: Warning.
While loading a Routing Table entry, MessageQ found the same group definition in the Cross-Group Connection Table. Group entries can be created by the MessageQ Loader utility or by an unsolicited connection.
User Action: Determine the preferred style of connection to the group and remove the other entry.
Bad DECnet connect IOSB status for link to group g (group_name) on system system_name

Explanation: Warning.
An error was returned by DECnet when attempting to connect to another servers group.
User Action: Examine the error and determine if the cause of the error is due to a local DECnet error, remote system error, or a configuration error.
Bad PAMS_SET_TIMER return status for X-Group auto reconnect

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

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

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

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

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

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

Explanation: Warning.
MessageQ detected an error while attempting to post a read $QIO to the main DECnet Mailbox channel.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.
Changing outbound for group g (group_name) to match inbound

Explanation: Warning.
An incoming connection request was received while an outbound connect was being performed to a different system or transport. The current outbound attempt will be dropped in favor of completing the incoming connection request.
User Action: None.
Connection for group g (group_name) to system system_name is down

Explanation: Warning.
All links to the indicated group are down.
User Action: Examine the previous messages for the indicated group and system for more information concerning the action.
Could not locate transport address (port number)

Explanation: Error.
The TCP/IP port number was omitted from the MessageQ initialization file definition for the local group.
User Action: The file must be corrected, or the transport will not be available for use.
DECnet communications lost to message queue group g (group_name)

Explanation: Warning.
The DECnet link to a remote COM Server aborted.
User Action: None.
DECnet communications lost to message queue group g (group_name) --- file not accessible

Explanation: Warning.
The current DECnet link to a remote COM Server is inaccessible.
User Action: None.
DECnet communications lost, 3rd party, to message queue group g (group_name)

Explanation: Warning.
An NCP command to disconnect the link was issued.
User Action: None.
DECnet data overrun from message queue group g (group_name)

Explanation: Warning.
The incoming message was larger than the internal buffer.
User Action: Compare the large buffer sizes of the two groups and adjust.
DECnet link exit to message queue group g (group_name)

Explanation: Warning.
A DECnet link exit was detected.
User Action: None.
DECnet path lost to message queue group g (group_name)

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

Explanation: Warning.
A DECnet network shutdown is causing the MessageQ network object to be deleted.
User Action: None. The COM Server will automatically re-create the DECnet object soon after the network is restarted.
Dropped link to group g (group_name)

Explanation: Warning.
A DECnet link event caused a link to a group to be dropped.
User Action: Examine the failure status on the next line to determine if it is a quota or configuration problem.
Dropped link to group g (group_name) due to LLS buffer pool exhaustion

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

Explanation: Warning.
The link to the indicated group is being dropped due to an unusable condition.
User Action: Examine the previous messages for the indicated group for more information concerning the action.
Dropped link to remote logical group g which is incompatible with expected group g (group_name)

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

Explanation: Warning.
An existing notification request was received.
User Action: None.
Duplicate queue notification request from g.q

Explanation: Warning.
An existing notification request was received.
User Action: None.
Duplicate Queue number passed to ENQ_PROCESS_LOCK_ASK routine = q

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

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

Explanation: Error.
While attempting to obtain a MessageQ group lock, an error was detected.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.
ENQ for "lock_name" not previously locked by process, releasing lock

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

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

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

Explanation: Error.
The indicated QIO to the group shown failed to complete with an unexpected error. The connection to the group will be dropped.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.
Error while posting X-group rcv QIO for group g - channel #n

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

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

Explanation: Warning.
MessageQ detected an error while attempting to connect to a remote group.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.
Error while posting X-group rcv QIO for group g --- channel #n Dropped connection to group g

Explanation: Warning.
While attempting to post a DECnet $QIO read operation, MessageQ detected an error.
User Action: Examine the accompanying error status and determine if it is due to the inaccessibility of the remote group.
Exceeded max number of outstanding queue cleanup requests - request q dropped.

Explanation: Warning.
Exceeded the maximum number of outstanding process cleanup requests.
User Action: Reduce the number of processes requiring cleanup.
Exceeded process notification table --- request from g.q discarded

Explanation: Warning.
The number of requesters of process notification messages exceeds the number in the internal table.
User Action: Reduce the number of requesters.
Exceeded queue notification table --- request from g.q

Explanation: Warning.
The number of requesters of queue notification messages exceeds the number in the internal table.
User Action: Reduce the number of requesters.
Exceeded routing visit count - UMA taken
+ discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Error.
MessageQ could not deliver the message to its destination queue because the routing visit count has been exceeded. The UMA was taken.
User Action: Recheck routing table and correct as necessary.
Exceeded write quota on link
+ discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Error.
MessageQ could not deliver the message because the group buffer pool has been exceeded.
User Action: Increase the xgroup buffer pool in the X-Group section of the group initialization file.
Exceeded X-Group notification table --- request from g.q discarded

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

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

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

Explanation: Error.
An error occurred while attempting to access mailbox channel.
User Action: Examine the failure status on the next line to determine the cause of the failure.
Failed on LIB$GET_VM_PAGE for DECnet MBX

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

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

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

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

Explanation: Error.
An error occurred while attempting to spawn a server process.
User Action: Examine the failure status on the next line to determine the cause of the failure.
Failed on SYS$GETJPIW call for DMQ queue g.q

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

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

Explanation: Error.
An error occurred while attempting to post a mailbox read.
User Action: Examine the failure status on the next line to determine the cause of the failure.
Failed to accept connect request from system system_name for group g

Explanation: Warning.
MessageQ detected an error while attempting to accept a connection from another group.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or if it is related to processor load.
Failed to accept connect request from system system_name for group g (group_name)

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

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

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

Explanation: Error.
MessageQ failed to allocate a group entry structure.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem.
Failed to allocate msg buffer for sending X-Group msg to group g (group_name)

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

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

Explanation: Warning.
While attempting to deliver a process notify message, MessageQ detected an error in the message allocation routine.
User Action: Examine the failure status posted on the next line to determine if it is due to the MessageQ buffer pool exhaustion.
Failed to connect group g (group_name) to system system_name - System name is unknown

Explanation: Error.
A connection attempt could not be made to the indicated group because the system name does not exist in the applicable network database.
User Action: Change the MessageQ initialization file, or add the entry to the network database to correct the condition.
Failed to convert outgoing message
+ discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Error.
MessageQ could not convert the outgoing xgroup message. The specified delivery mode and UMA combination are not support by the receiving group.
User Action: Correct as necessary.
Failed to create temporary mailbox for Server spawning

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

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

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

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

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

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

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

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

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

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

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

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

Explanation: Error.
An error occurred while MessageQ attempted to initialize DECnet communication.
User Action: Examine the failure status on the next line to determine if it is a configuration problem.
Failed to load NT into TCB for group g (group_name), table entry = group_index, NT = cur_nt

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

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

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

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

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

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

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

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

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

Explanation: Error.
The attempt to create the indicated MessageQ link driver or server process failed.
User Action: Examine the failure status on the next line to determine if it is a quota or configuration problem.
Failed to translate rights ID "rights_id" for DMQ queue g.q

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

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

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

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

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

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

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

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

Explanation: Error.
While attempting to create the Group Name Table global section, MessageQ found that the table already exists.
User Action: None.
Group g (group_name) OUTBOUND link to system system_name is not responding

Explanation: Error.
A communications handshaking or protocol error has occurred on the connection to the indicated group. The remote group is not responding. The group connection will be dropped.
User Action: If the problem persists, contact MessageQ support with a description of the error.
Ignored connect confirm from system system_name group g due to security match failure

Explanation: Error.
XGROUP_VERIFY has been enabled and the connection confirmation does not match the information found in the Cross-Group Connection Table.
User Action: Correct as necessary.
Ignoring connect request from system system_name - group g is in link management transition

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

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

Explanation: Warning.
An incoming connection was rejected because a link to that group already existed and is owned by another link driver.
User Action: None.
Ignoring LD_REQUEST_ACCEPTED msg from g.q --- cannot locate link

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

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

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

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

Explanation: Warning.
An invalid Queue Notification deregistration request message was received.
User Action: Recheck the request message for validity using script message tracing.
Invalid DMQ$BUS_GROUP = "s"

Explanation: Fatal.
MessageQ detected an invalid setting of the logical DMQ$BUS_GROUP.
User Action: Correct as necessary.
Invalid queue list request from g.q

Explanation: Warning.
An invalid queue list request message was received.
User Action: Recheck the request message for validity using script message tracing.
Invalid Queue Notification Request from g.q

Explanation: Warning.
A queue notification registration request message was received that was invalid.
User Action: Recheck the request message for validity using script message tracing.
Invalid msg targeted to server_name
+ discarded msg - Src=g.q Target=g.q class=n type=n

Explanation: Warning.
The indicated server received a message of a class and type that it does not recognize.
User Action: Correct as necessary.
Invalid X-Group number g specified for self

Explanation: Fatal.
Local group number is out of range.
User Action: Correct as necessary.
Invalid X-Group request to declare a temporary SQ - Source=g.q

Explanation: Warning.
A non local process attempted to attach a temporary secondary queue.
User Action: Correct as necessary.
Invalid undeclare SQ request --- SQ #q Source=g.q

Explanation: Error.
A request was made to detach a secondary queue from a process that was invalid, did not own the queue, or it was not a secondary queue.
User Action: Correct as necessary.
Large buffer size is too small, adjusting large buffer size to n

Explanation: Warning.
The Large buffer size provided in the group initialization file is too small. It must be larger than both the small and medium buffers.
User Action: Increase the size of the large buffers in the group initialization file.
Large LLS Pool already exists --- two DMQ COM Servers running.

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

Explanation: Warning.
The link driver has terminated execution.
User Action: Examine the previous messages, and the log file, for more information concerning the action.
Link Management request from g.q rejected

Explanation: Error.
A Link Management request message, generated by a user program, was received either from an nonprivileged user or from another group.
User Action: Investigate proper authorization of request.
Listener is down - network not currently accessible

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

Explanation: Warning.
A non local load complete message was received.
User Action: Correct as necessary.
Local host address lookup failed

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

Explanation: Fatal.
The link driver failed to located the local host name in the network database.
User Action: Examine the network database, and the MessageQ initialization file.
Local system is system_name, transport addr s

Explanation: Informational.
Identifies the system and transport address of the link driver starting up.
User Action: None.
Local system system_name is not listed for this group g under this transport

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

Explanation: Fatal.
Maximum DECnet system name is 6 characters.
User Action: Modify the group initialization file and restart the group.
Logical DMQ$SET_GBLSEC_PROT value "s" is invalid

Explanation: Fatal.
The format of the DMQ$SET_GBLSEC_PROT logical name is invalid.
User Action: Correct as necessary.
** LOW BUFFER WARNING --- LARGE FREE LIST --- TOTAL:n CURR:n WARN:n **

Explanation: Warning.
The number of large free buffers available has reached the warning level.
User Action: You might need to adjust send rate, total number of large buffers available, or receive byte quota on the message queues.
** LOW BUFFER WARNING --- MEDIUM FREE LIST --- TOTAL:n CURR:n WARN:n **

Explanation: Warning.
The number of medium free buffers available has reached the warning level.
User Action: You might need to adjust send rate, total number of medium buffers available, or receive byte quota on the message queues.
** LOW BUFFER WARNING --- SMALL FREE LIST --- TOTAL:n CURR:n WARN:n **

Explanation: Warning.
The number of small free buffers available has reached the warning level.
User Action: You might need to adjust send rate, total number of small buffers available, or receive byte quota on the message queues.
MCS already exists --- two DMQ COM Servers running.

Explanation: Fatal.
While attempting to create the message control section (MCS), MessageQ found it to already exist. This error means that one or more processes have not unmapped the global sections so that the systems can delete them. This error could be caused by a process in the debugger or because the user mode ASTs are disabled.
User Action: Search for processes that are still attached to MessageQ and cause them to exit.
Medium buffer size is too small, adjusting medium buffer size to n

Explanation: Warning.
The medium buffer size provided in the group initialization file is too small. It must be larger than the small buffer size.
User Action: Increase the size of the medium buffers in the group initialization file.
Medium LLS Pool already exists --- two DMQ COM Servers running.

Explanation: Fatal.
While attempting to create the medium linked list section (LLS), MessageQ found that it already exists. This error means that one or more processes have not unmapped the global sections so that the system can delete them. This error could be caused by a process in the debugger, or because the user mode ASTs are disabled.
User Action: Search for processes that are still attached to MessageQ and cause them to exit.
Message lost (undeliverable)
+ discarded msg --- Src=g.q Target=g.q class=n type=n

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

Explanation: Error.
An attempt to receive a message from the MessageQ message bus returned an unexpected error.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.
Msg from system system_name is larger than negotiated maximum for group g (group_name)

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

Explanation: Warning.
A user attempted to shut down the COM Server by using the "Kill COM Server" MONITOR command. This command has been explicitly disabled by setting the ACCEPT_KILL_CMD to No in the Profile section of the group initialization file.
User Action: Correct as necessary.
Msg lost (bad target address)
+ discarded msg --- Src=g.q Target=g.q class=n type=n

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

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

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

Explanation: Error.
The network has become inaccessible and all existing connections to groups are being dropped. The link driver will retry connections if the network becomes accessible again.
User Action: Restart the network.
Network protocol error occurred for message queue group g (group_name)

Explanation: Error.
A DECnet protocol error occurred on the specified link to the remote group.
User Action: Examine the failure status posted on the next line to determine if it is due to a process quota problem or a system resource problem.
No available temporary queues - Unable to allocate temp SQ - Source=g.q

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

Explanation: Warning.
While attempting to allocate a temporary queue to a process, MessageQ found the pool of available queues to be empty.
User Action: Increase the number of temporary queues by lowering the FIRST_TEMP_QUEUE value in the groups initialization file.
No memory for buffer for message queue group g (group_name)

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

Explanation: Error.
A communications handshaking or protocol error has occurred on the connection to the indicated group. The group connection will be dropped.
User Action: If the problem persists, contact MessageQ support with a description of the error.
Rejected connect attempt to/for group g - Ownership transfer denied by g.q

Explanation: Warning.
The connection attempt was rejected because a request for group ownership transfer was denied by the server at the indicated address.
User Action: None.
Rejected connect request for group g - system could not be determined

Explanation: Error.
The connection request cannot be accepted because the remote system could not be determined. This may indicate an error in the MessageQ initialization file, or that the system is not listed in the appropriate network database.
User Action: Examine and correct the MessageQ initialization file(s) or network database.
Rejected connect request for group g from system system_name (system_address) - address disagrees with network database

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

Explanation: Error.
An outbound connection attempt to the indicated system and group failed due to an unknown error condition.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.
Rejected connect request for group g from system system_name (system_address) - system not found in network database

Explanation: Warning.
A connection attempt was received from a system that does not exist in the applicable network database.
User Action: The MessageQ initialization file(s) may be in error, or the system may need to be added in the network database.
Rejected connect request from system system_name due to security match failure (group unknown)

Explanation: Error.
XGROUP_VERIFY has been enabled and the connect request does not match the information found in the Cross-Group Connection Table.
User Action: Correct as necessary.
Rejected connect request from system system_name due to wrong bus

Explanation: Error.
The connection attempt was rejected because it came from a different MessageQ bus.
User Action: Correct the environment so that the group connections are for the same bus.
Rejected connect request from system system_name group g due to security match failure

Explanation: Error.
XGROUP_VERIFY has been enabled and the connect request does not match the information found in the Cross-Group Connection Table.
User Action: Correct as necessary.
Rejected connect request from system system_name for group g (group_name) - Connection already in progress by b.g

Explanation: Warning.
The connection request received from the indicated system was rejected because the connection is already in progress.
User Action: None.
Rejected connect request from system system_name for group g (group_name) - connection currently in progress

Explanation: Warning.
The connection request received from the indicated system was rejected because the connection is currently in progress.
User Action: None.
Rejected connect request from system system_name for group g (group_name) - connection still in progress

Explanation: Warning.
The connection request received from the indicated system was rejected because the connection is still in progress.
User Action: None.
Rejected connect request from system system_name group g - Group disabled

Explanation: Warning.
An incoming connect request was denied because connections are currently disabled. This can be due to the group being disabled on startup or by way of a Link Management message disconnecting the link.
User Action: When ready to allow links to this group, send a Link Management message to enable connections.
Rejected connect request from system system_name for group g (group_name) - group is already connected

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

Explanation: Warning.
An incoming connect request was denied because connections are currently disabled. This can be due to the group being disabled on startup or by way of a Link Management message disconnecting the link.
User Action: When ready to allow links to this group, send a Link Management message to enable connections.
Rejected connect request from system system_name (system_address) - Improper Protocol response received

Explanation: Error.
A connection attempt from the indicated system was rejected because of a communications protocol failure. This may indicate a non-linkdriver program (perhaps a non-MessageQ program), or an incompatible MessageQ system is attempting the connection.
User Action: Investigate the system and program attempting the connection.
Rejected connect request from system system_name for group g group_name -Link Driver or network is shutting down

Explanation: Error.
The connect request is ignored because either the link driver, the network, or the system is shutting down.
User Action: Correct as necessary.
Rejected connect request from system system_name for group g (group_name) - Link is currently in transition

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

Explanation: Warning.
The connection request received from the indicated system was rejected due to a different transport currently owning the group.
User Action: None.
Rejected connect request from system system_name for group g (group_name) - read link is currently in transition

Explanation: Warning.
The connection request received from the indicated system was rejected because the read link is currently in transition.
User Action: None.
Rejected connect request from system system_name for group g (group_name) - write link is currently in transition

Explanation: Warning.
The connection request received from the indicated system was rejected because we own this group, and there's already an outbound, and that outbound is currently shutting down.
User Action: None.
Rejected connect request from system system_name (system_address) - protocol not supported

Explanation: Error.
A connection attempt was received from a system running a MessageQ release that is incompatible with the link driver.
User Action: None.
Remote system not listed for this group/transport

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

Explanation: Warning.
The indicated link driver or server process has terminated.
User Action: Determine the reason for the termination by examining the link driver or server log files in DMQ$LOG:.
Skipping connect to group g (group_name) - Failed to send external ownership request to b.g

Explanation: Error.
A connection to the indicated group could not be attempted because of a failure to send an external ownership request to the specified group.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.
Skipping connect to group g (group_name) - No outbounds possible or allowed

Explanation: Informational.
A connect attempt to the indicated group was not possible or not supported.
User Action: None.
Skipping connect to group g (group_name) - System address cannot be determined

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

Explanation: Error.
A connection to the indicated group could not be attempted due to an unexpected error condition.
User Action: Examine the failure status posted on the next line to determine the error condition encountered, and the corrective action required.
Small LLS Pool already exists --- two DMQ COM Servers running.

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

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

Explanation: Informational.
The link driver or server specified has successfully started running.
User Action: None.
SYS$CRELNM failed to create logical_name in lnm tbl table_name

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

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

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

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

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

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

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

Explanation: Error.
The connection request is rejected because the specified transport is not supported by this group and XGROUP_VERIFY is YES.
User Action: Correct as necessary.
TP PROTOCOL ERROR: invalid substate n on INBOUND link to group g (group_name)

Explanation: Error.
A communications handshaking or protocol error has occurred on the connection to the indicated group. The group connection will be dropped.
User Action: If the problem persists, contact MessageQ support with a description of the error.
TP PROTOCOL ERROR: invalid substate n on OUTBOUND link to group g (group_name)

Explanation: Error.
A communications handshaking or protocol error has occurred on the connection to the indicated group. The group connection will be dropped.
User Action: If the problem persists, contact MessageQ support with a description of the error.
Unable to deassign DECnet data I/O channel for group g in XDECNET

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

Explanation: Warning.
MessageQ detected an error when attempting to deassign a DECnet OOB channel for a remote group.
User Action: Verify whether an earlier link error is causing this problem.
Unable to declare temporary SQ --- Source=g.q

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

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

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

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

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

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

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

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

Explanation: Error.
An attempt to respond to a request for transfer of group ownership failed.
User Action: Examine the status posted on the next line to determine the error condition encountered and the corrective action required.
Unable to send message to target - exceeded x-group buffer maximum
+ discarded msg - Src=g.q Target=g.q class=n type=n

Explanation: Error.
An attempt was made to send a message that is larger than the receiving groups GROUP_MAX_MESSAGE_SIZE.
User Action: Increase the receiving groups GROUP_MAX_MESSAGE_SIZE in the groups initialization file.
Unblock msg lost (buffer allocation failed)

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

Explanation: Fatal.
The ENABLE_XGROUP parameter in the group initialization file is set to NO.
User Action: Set the ENABLE_XGROUP parameter in the group initialization file to YES. Restart the group.
X-Group write failed to group g (group_name)
+ Discarded msg --- Src=g.q Target=g.q class=n type=n

Explanation: Warning.
A cross-group connection request between the listed groups failed.
User Action: None.
X-Group write failed to group g (group_name)
+ Message lost - protocol translation or UMA failure

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

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

Previous | Next | Contents