.HL 1 QUEUE SYSTEM SERVICE ERROR MESSAGES .fill .list 1,'' .le;QUE_SUCCESS-Successful completion .X QUE_SUCCESS>Defined .le;QUE_NOMESS-No message for the specified message ID The message id has no messages in it and is empty. The caller should either exit or wait on the event flag specified in the CONNECT_READ call. .x QUE_NOMESS>Defined .le;QUE_INVIDX-Invalid MID index for the specified MID The index passed in the call points to a message id that does not match the message id that has been passed, or the index is not within range. .x QUE_INVIDX>Defined .le;QUE_ALRATT-Queue has already been attached A call to the system service ATTACH_Q has detected that the calling process is already attached. The service determines that the calling process is already attached by looking for a LOCK BLOCK for the calling process. The caller must detach from the Queue, exit, or go through process deletion before calling the service again. The service will zero the Q_BLOCK that is passed in the calling argument and may require that the process go through process rundown if the calling process has not saved the previous contents of the Q_BLOCK. .x QUE_ALRATT>Defined .le;MIDNOTUNIQUE-Message ID is not unique The caller/user has attempted to add a message id that is already in the queue. The user should use Q_UTL to determine which message ids are already in use and MENU to determine which are currently installed (those maintained by Q_UTL and what is currently in the installed queue may not be the same). .x QUE_MIDNOTUNIQUE>Defined .le;QUE_MIDLISTFULL-Message ID list is full No more message ids can be added without creating a new queue. The system manager must modify the maximum number of message ids to be allowed even if they are not all used. .x QUE_MIDLISTFULL>Defined .le;QUE_MIDNOTFOUND-Message ID not found in list The message id passed is not defined in the queue. The menu program may be used to define a message id to the installed queue and the Q_UTL utility may be used to have the message id added permeantly. If the message id is defined in the queue, then the caller has not passed the message id as a character string. .LE;QUE_INSFARG-Insufficient arguments The caller has passed insufficient arguments for the call. Review the call and provide the minimum number of arguments. .x QUE_INSFARG>Defined .le;INVARG-Invalid arguments The caller has passed an argument either incorrectly (ie: by reference instead of by value), with an invalid size (ie: 10 character message id instead of 16), simply invalid, or the item is not readable/writeable in user mode. .x QUE_INVARG>Defined .le;NOTINITIALIZED-Queueing functions have not been initialized The caller has made a call to one of the queue system services with out first attaching to the queue or else the Q_BLOCK parameter is not valid. .x QUE_NOTINITIALIZED>Defined .le;QUE_MIDATTACHED-Message ID is already attached The caller has attempted to connect to a message id for read but either itself or another process has already connected to the message id for read (There may be only a single reader for a message id). .x QUE_MIDATTACHED>Defined .le;QUE_BUFTOOSMALL-User buffer is too small for message The caller has passed a buffer that is too small to receive the message from the queue or else the buffer is being passed by the wrong method. The menu program may be used to do a non-destructive read of the message to find out how large the message really is. Note: The buffer must be large enought to hold the message header too. .x QUE_BUFTOOSMALL>Defined .le;QUE_RNAMESS-There is an outstanding read-not-acknowleged message The caller has attempted to read a second message before acknowledging the first message. The user should acknowledge the first before reading another message .X QUE_RNAMESS>Defined .le;QUE_NORNAMESS-There is no outstanding read-not-acknowleged message The caller has attempted to acknowledge a message that does not have an outstanding read but not acknowledged message. If this is from a queue where the oldest message may be deleted (ie: type 0 messages), this should be considered as a postive acknowledge as the message that was being acknowledged may have been deleted and replaced by a new message. .X QUE_NORNAMESS .le;QUE_INVRNA- Invalid read-not-acknowleged pointer The caller has attempted to acknowledge a message just read but the RNA pointer does not match that which has been saved in the queue. Either the caller is passing the RNA pointer incorrectly or the RNA is simply not valid. .x QUE_INVRNA>Defined .le;QUE_INSFREE- Insufficient number of free blocks The Queue is full and no more messages can be added until some of the messages have been removed. The system manager should be contacted to allocate more message blocks for the queue. If the menu program shows that there are message blocks on the free list, then the queue is possibly corrupt and the system should be taken down and the queue restored. .x QUE_INSFREE>Defined .le;QUE_INVFREE-Invalid free control blocks The queue is corrupt. .x QUE_INVFREE>Defined .le;QUE_MIDNOTATT- Message ID is not attached The caller has attempted to read a message id without first connecting to it with the CONECT_READ system service. .x QUE_MIDNOTATT>Defined .le;QUE_MIDMAX-Message ID is at maximum allowed messages The user has attempted to write a message to the queue but the Queue already has the maximum number of messages for this message id in the queue already. The user should contact the system manager to find out why the queue is not being emptied or else have the system manager modify the maximum number allowed to be queued. This error will not occurr if the message type is of type zero as the oldest message id will be deleted if the queue is full. .x QUE_MIDMAX>Defined .le;QUE_MAXMID-Caller is connected to maximum number of Message IDs The calling process has attempted to connect for read for more message ids than was specified when the caller did a ATTACH_Q (or the default). The caller should modify his application to pass a parameter instead of using the default or else increment the current passed number. .x QUE_MAXMID>Defined .le;QUE_HEADNOTREM-Message header unable to be removed from Message ID list While attempting to remove the message id from the list, the REMQUEI failed. The attempt should be tried a second time and if it still fails, the system manager should be notified. .x QUE_HEADNOTREM>Defined .le;QUE_GTRMAX- Number specified is greater than allowed maximum number of Message IDs The number of message ids to allow for connection by a single process is invalid. This is a probable error in the Maximum message ids to connect for. The value being exceeded is for sanity test and has been set rather large. The caller should verify that the parameter is valid and is being passed correctly. .x QUE_GTRMAX>Defined .le;QUE_NOCHK-Checkpoint process is not available The message id has been added but the message is not guaranteed to be saved as the process that is responsible for checkpointing the queue to the disk file is nolonger available. The system manager should be notified if this occurrs (unless the queue is being taken down intentionally). .x QUE_NOCHK>Defined .le;QUE_IDXOOR- MID index is out of range The passed message id index is out or range, ie: less than one and greater than the number of message ids currently defined in the queue. The caller should verify the parameter and the calling method. .X QUE_IDXOOR>Defined .le;QUE_BADLOCK- LKB points to an invalid resource block (RSB) The lock block that is pointed to by the queue header does not appear to be intact. The queue is probably corrupt and the system manager should be notified. .X QUE_BADLOCK>Defined .le;QUE_TOOMANYPCBS- Insufficient room to return all of the PCBs of attached processes The system service FIND_Q_PROCESSES was unable to return all of the processes that are currently attached to the queue. The passed buffer must be enlarged. .X QUE_TOOMANYPCBS>Defined .le;QUE_HASHCORUPT- Hash table in queue is corrupt, rebuild queue The queue is corrupt, contact the system manager. .X QUE_HASCORUPT>Defined .le;QUE_NOPRIV- User does not have privilege for attempted operation Certain system services require SYSPRIV. The caller does not have the privelege to peform this call. .x QUE_NOPRIV>Defined .le;QUE_MIDDELETED- The requested message id has been deleted The message id that the caller has desired to read, write, or connect to has been deleted. The message id is still threaded but has not been overwritten yet. This should be considered the same as the invalid message id. .x QUE_MIDDELETED>Defined .le;QUE_KSSACCVIO- Kernel SS dispatcher, access violation The Kernel system service dispatcher has determined that one of the required parameters to one of the system service calls is not accessible in the mode of the caller. The caller should fix the calling sequence and method of parameter passing. .x QUE_KSSACCVIO>Defined .le;QUE_ESSACCVIO- Executive SS dispatcher, access violation The Executive system service dispatcher has determined that one of the required parameters to one of the system service calls is not accessible in the mode of the caller. The caller should fix the calling sequence and method of parameter passing. .x QUE_ESSACCVIO>Defined .le;QUE_KSSINSFARG- Kernel SS dispatcher, insufficient number of arguments The Kernel system service dispatcher has determined that the minimum number of arguments has not been specified. The caller should verify the required parameters for the called service. .x QUE_KSSINSFARG>Defined .le;QUE_ESSINSFARG- Executive SS dispatcher, insufficient number of arguments The Executive system service dispatcher has determined that the minimum number of arguments has not been specified. The caller should verify the required parameters for the called service. .X QUE_ESSINSFARG>Defined .LE;QUE_SHUTDOWN- Queue has been shut down, nolonger available Some user with SYSPRIV priveleged has decided to shut down the queue. The calling process should disconnect from the queue and/or exit. The queue is no longer available for use and the disconnect will allow the system to remove the queue (the system will not allow the queue to be removed until all processes have unmapped the section). .x QUE_SHUTDOWN>Defined .le;QUE_RSBBAD- Queue Resource lock (RSB) is corrupt, missing, etc. The queue header points to a bad RSB. The system manager should be contacted and use of the queue should be suspended. .x QUE_RSBBAD>Defined .le;QUE_NONEMPTYQ- Attempt to delete a message id that is not empty The caller has attempted to delete a message id that contains messages. The caller must first dequeue all the message ids before it may be deleted. .x QUE_NONEMPTYQ>Defined .le;QUE_IDATTACHED- Attempt to delete a message id that is currently attached The caller has attempted to delete a message that has a process connected for a read on it. The process that is connected must exit or disconnect from the message id before it may be deleted. .x QUE_IDATTACHED>Defined .els .PAGE .CENTER;ROUTER PROCESS ERRORS AND STATUS .HL 1MA_ROUTER PROCESS ERRORS AND STATUS All of the MA_ROUTER's error and status messages are sent via "SYS$SNDOPR" system service. The standard format of the message is: .literal TIME STAMP PROCESS USER error text .end literal .sk The following messages are informational only are logged to help diagnose the routing functions. None of the debug messages will be displayed if the debug has not been compiled into the router. .sk .list 1,' ' .le;RTR_LNKEST- Link established with remote node: The router successfully connected to node listed. .LE;RTR_CONEST- Receiving process connection made for Message ID: Debug .LE;RTR_START- MA_ROUTER process starting The router is starting up, however, no further success can be determined from this status. .LE;RTR_RUTABL- New routing table being processed The router has been told that a new routing database is to be used. The router will disconnect from all nodes and exit. .LE;RTR_OPN- Successfull message routing section file built, length: Debug .LE;RTR_OBJDEF- Router: Defined to DECNET as a known object The router has successfully defined itselft to DECNET as a known object such that it may accept incomming connections from remote nodes. .LE;RTR_LNKCON- Requested logical link successful Access control string: The router has successfully created a logical link with the listed node by using the listed access control string. .LE;RTR_CONAST-Connection Ast called, access control string: status: Debug .LE;RTR_NETAST- Network message ast called, information: MESSAGE TYPE(ID): Debug .LE;RTR_CONTMO- Connect timeout for node (access control string): The node specified (access control string) has timed out while trying to establish a logical link. .LE;RTR_CONTIMAST- Connect timer timeout ast executing, acc: Debug .LE;RTR_CONTRY-Connect attempt for (access control string): Debug .LE;RTR_NTRDAST -Network read AST called, BYTE COUNT: Debug .LE;RTR_NTRDPST- Read posted on node: Debug .LE;RTR_RSPAST-Read response ast qio complete, status: Debug .LE;RTR_NTRDMSG-Msgid: NODES(S,D): , Lnksq: /Typ: Idx: lth: On Q: Debug .LE;RTR_NTOUTMSG- Message id: output to node: RNA= , BUFADDR: Debug .LE;RTR_WRITECOMP- Write complete node: Message ID: I/O status: Debug .LE;RTR_QWRITEAT- Write to Queue: Message id: Length: , Type: Debug .LE;RTR_ACKMSG-Node: Acknowledging message id: , will acknowledge read from queue Debug .LE;RTR_RSPMSG-Msgid: NODES(S,D): , Lnksq: Typ: Idx: lth: On Q: Debug .ELS .PAGE .CENTER;ROUTER PROCESS ERRORS AND STATUS (Continued) The following messages are warning messages and will not cause the router to stop performing its functions. Only the effected element will suffer. .sk .list 1,' ' .LE;RTR_STOP- MA_ROUTER has been requested to stop, message routing discontinued A message has been recieved in the router's mailbox requesting that the router stop. Currently this entry is not used. .LE;RTR_NMLEXT- MA_ROUTER is exiting normally, routing functions will not be available The exit handler for the MA_ROUTER is running. This is normally caused by someone stopping and restarting the router because of a new routing database. .LE;RTR_UNKCON- Connect request error, status: Unable to accecpt a connection, status is printed. .LE;RTR_DISNODE-Disconnecting node: Routing for this node will be disabled The router is disconnecting from the listed node. Previous messages should be studied to find the cause. .LE;RTR_NORNA- Acknowledge received for non outstanding message Node: Message id: The router on this node has detected a router protocol error between itself and the router on the node that is listed. It should be brought to the attention of the developer. .LE;RTR_ACKRDE- Error while calling ACK_READ, queue error: Node: Message id: The router was unable to acknowledge a read for a message that was just successfully transmitted to the remote node listed. This may or may not cause the discontinued routing of this message id depending on the error code. .LE;RTR_BADIDX- Acknowledge received with invalid routing index: Node: Message id: The router on this node has detected a router protocol eerror between itself and the router on the node that is listed. .LE;RTR_BADIDX2- Invalid NRBID index in buffer: Id: Node: The router on this node has detected a router protocol eerror between itself and the router on the node that is listed. .LE;RTR_NOSUCHID- Acknowledge received for noexistant id from: Node: Message id: The router on this node has detected a router protocol eerror between itself and the router on the node that is listed. .LE;RTR_NEWDBS- New routing database requested, ROUTER services disabled, process exiting A request has been received in the router's mailbox to discontinue routing because a new routing database is being installed. This is not currently used but is supported. .els .PAGE .CENTER;ROUTER PROCESS ERRORS AND STATUS (Continued) .sk The following errors are used to denote action that might be required by maintenance people such as a link being down. .list 1,' ' .LE;RTR_LNKFAL- Link failure, for node: , DECNET status: Logical link attempt has failed for the listed node and the DECNET status reason is listed. .LE;RTR_EVQFUL- Event Queue Full, unable to store event: routing failure may occur Internal error, contact developer. .LE;RTR_QIORDERR- Route MBX read failure, status: Request is being ignored The router was unable to read it's mailbox. These letters are supported but not implemented. .LE;RTR_CONFAL- Connect qio failure, status: Access Control: no routing to node Logical connect attempt failed with the access control string. No routing will be attempted and a connect timer will be started. .LE;RTR_REQFAL-Request logical link failure access control string: Logical connect attempt failed with the access control string. No routing will be attempted and a connect timer will be started. .LE;RTR_NETREJ- Unable to do qio to reject incoming connect, status: Internal error contact developer .LE;RTR_NETACC-Unable to do qio to accept incoming connect, status: Internal error contact developer .LE;RTR_RDNETMBX- Read error on read of network mailbox, status: ACCESS CONTROL: Internal error contact developer .LE;RTR_NETRDERR-Network read error, status: routing continuing Internal error contact developer .LE;RTR_LNKSEQERR- Logical link sequence error, got: expected from node: The router on this node has detected a router protocol eerror between itself and the router on the node that is listed. Contact the developer. .LE;RTR_NORSPBUF-No response buffer available, node: slowdown required, recovering The router needs more response buffers than are currently available in the routing database. The system manager should consider increasing the number of response buffers. .LE;RTR_NTWTQIO- Network write error, node: status:, disconnecting node The router is unable to write the remote node. Expect other errors to also be logged. The most probable error is node disconnect, etc. .LE;RTR_PEXERR- Q_BLOCK pointing to region is invalid, from routine MARK_FULL Internal error contact developer .LE;RTR_QWRITE-Q_WRITE bad status: Msgid: Node: Msgid no longer being queued The message id recieved from the remote node is unable to be queued. The remote node will be told not to route this message id anymore. The reason for the status is listed. More than one of these messages may be logged if this message is received from more than a single node. .LE;RTR_NETWTQIO-Message output to DECNET NODE: Status: Debug .LE;RTR_QREAD- Bad Q_Read status: Msgid: Node: , ignoring message The message was unable to be read from the queue. The message id will no longer be routed. The message id will be flagged with status showing a bad queue read status. .LE;RTR_NTWRTERR- Bad network write status: Node: for message id: Bad write status to the listed node. Will cause a disconnect and link termination. .LE;RTR_NRBIDIDX- Invalid index for BACKUP_RNA call index:, Message id: Internal error, contact developer .LE;RTR_BACKUPRNA-Bad error status for backup RNA call: Message id: If the error is simply no RNA message, then this will not be fatal. Otherwise, the developer should be notified. .els .PAGE .CENTER;ROUTER PROCESS ERRORS AND STATUS (Continued) .sk The following errors are considered fatal to router operations and will cause the router to exit and terminate all routing functions. .LIST 1,' ' .LE;RTR_MAPFAL-Unable to build routing table, mapping failure: routing discontinued The router was unable to build is routing map and therefore no routing will be available. .LE;RTR_MBXCRE-Unable to create MA_ROUTER mailbox, status: routing discontinued The router could not create is mailbox and will not continue. The priveleges given to the router should be checked along with the error status listed. .LE;RTR_NOEFN-Unable to get event flag, status: routing discontinued Internal error, contact developer. .LE;RTR_EXTHAN- Unable to setup exit handler, status: routing discontinued Internal error, contact developer. .LE;RTR_ABNEXT-MA_ROUTER is exiting ABNORMALLY, status: routing discontinued Internal error, contact developer. .LE;RTR_DSCERR- Unable to delete Routing Database section, status: routing discontinued The router is attempting to create a new routing database and delete the old one but failed. Most probable cause is that someone else is mapped to the group global section (see NRBDMP). .LE;RTR_DELADR- Unable to delete Routing Database V.A., status: routing discontinued Internal error, contact developer .LE;RTR_DASNF- Deassign channel failure Routing section, status: routing discontinued Internal error, contact developer .LE;RTR_NOLUN- Unable to get event LUN, status: routing discontinued Internal error, contact developer .LE;RTR_BOPN- Bad section open/creation for routing DBS, status: routing discontinued Since can't create a routing database, no routing will be supported. The status will point to the fault. If not obvious, contact developer. .LE;RTR_QIOMBX-Unable to issue QIO to our ROUTING mailbox, status: routing discontinued Internal error, contact developer .LE;RTR_NETASN-Unable to assign channel to network, status: routing discontinued Since can't connect to the network, will be unable to create logical links. Therefore, no need to route. Check to make sure network is available. .LE;RTR_NETOBJ-Unable set self as a known network object, status: routing discontinued To allow incomming connections, must be able to identify self as a network object. If failure, check privelege (requires sysprv). .LE;RTR_DEAFAL-Unable to deassign network channel, status: routing discontinued Internal error, contact developer. .LE;RTR_NETMBX- Unable to issue QIO to NETWORK mailbox, status: routing discontinued Since can't write to network mailbox, can't accept or attempt logical link connection. May have insufficient buffer quota. If error status not obvious, contact developer. .LE;RTR_RTYTIM- Unable to set retry timer, status: routing discontinued Internal error, contact developer .LE;RTR_WAKEFN- Unable to set wakeup event flag, status: routing discontinued Internal error, contact developer .LE;RTR_BINTIM- Unable to convert retry timer, status: NODE: routing discontinued Internal error, contact developer .LE;RTR_NETRDQIO- Unable to post network read node: STATUS: Unable to do a read will fail that logical link. .LE;RTR_QUEFAL-Unable to attach to queue, status: routing discontinued If the Queue is not available, then routing will exit as all messages are read and written to the queue. Make sure that the queue checkr process is available and the queue is not shutting down. .LE;RTR_TIMFAL- Unable to start no response buffer timer, routing discontinued Internal error, contact developer .LE;RTR_TMRERR- Unable to canceal mark time for node: status: continueing Internal error, contact developer. However, error is not critical and process will not exit. .LE;RTR_NETDOWN- NETWORK SHUTTING DOWN, no need for routing services, process exiting Someone has used NCP to shutdown the network. The router has received the network shuting downt error in it network mail box. The router will shutdown. .els